Issues with mount External HD

[saulo.faria]

Hi All,

Suddenly I got a problem with my external HD who is not being read anymore, neither by my RaspPi nor by my Win7 machine.

I wonder if the HD is dead or something happened to the file system of the HD.

When executing lsusb i see the device listed there:

Bus 001 Device 013: ID 059b:0475 Iomega Corp.

When executing dmesg I get the following for sda:

6444.779234] sd 2:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 6444.780186] sd 2:0:0:0: [sda] Write Protect is off
[ 6444.780219] sd 2:0:0:0: [sda] Mode Sense: 34 00 00 00
[ 6444.781214] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 6444.789111] sda: sda1
[ 6444.793237] sd 2:0:0:0: [sda] Attached SCSI disk
[ 6611.560575] EXT4-fs (sda1): recovery complete
[ 6611.561602] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 8826.869590] FAT-fs (sda1): Unrecognized mount option "fmask137" or missing value
[ 9103.506663] FAT-fs (sda1): Unrecognized mount option "fmask137" or missing value
[ 9566.349543] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro

But with all that, I am not understanding why the HD is not mounting properly.

Any help from the team is appreciated.

[saulo.faria]

Further to that, when trying to mount sda1 i get:
sudo mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

here is my fstab

proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults 0 2
/dev/mmcblk0p2 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, so no using swapon|off from here on, use dphys-$
/dev/sda1 /media/extHD ext3 nobootwait

[saulo.faria]

More info:

Here we can see that there is an used space of ~ 40 GB on the HD, which is correct.

Filesystem Size Used Avail Use% Mounted on
rootfs 3.7G 2.7G 800M 78% /
/dev/root 3.7G 2.7G 800M 78% /
devtmpfs 212M 0 212M 0% /dev
tmpfs 44M 576K 44M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 88M 0 88M 0% /run/shm
/dev/mmcblk0p1 56M 19M 38M 33% /boot
/dev/sda1 917G 921M 870G 1% /media/extHD

But when doing a ls on the media. that's what I am getting:

bin
boot
dev
etc
home
lib
lost+found
media
mnt
opt
proc
root
run
sbin
scripts
selinux
splash
srv
sys
tmp
usr
var

HELP

[RaTTuS]

sudo umount /dev/sda1
sudo fdisk -l #list filesystem
sudo e2fsck -f /dev/sda1 #force check of sda1

...
umm actually
/dev/sda1 /media/extHD ext3 nobootwait
that fstab looks wrong
make it

/dev/sda1 /media/extHD ext3 default 0 1

[saulo.faria]

Here is the output of sudo e2fsck -f /dev/sda1
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 25952259 was part of the orphaned inode list. FIXED.
Inode 25952260 was part of the orphaned inode list. FIXED.
Inode 25952261 was part of the orphaned inode list. FIXED.
Inode 25952262 was part of the orphaned inode list. FIXED.
Inode 25952263 was part of the orphaned inode list. FIXED.
Inode 25952264 was part of the orphaned inode list. FIXED.
Inode 25952265 was part of the orphaned inode list. FIXED.
Inode 25952266 was part of the orphaned inode list. FIXED.
Inode 25952267 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 30510/61054976 files (0.1% non-contiguous), 4067592/244190645 blocks

[saulo.faria]

Well, I was connected via ssh to my Rpi.

I have followed your recommenadation to umount the extHD and changed the fstab. Aftar that I reboot the Rpi.

Probably the ip got changed and my router didn't pick it up. I will need to give you feedback on that later today.

Thanks for the reply

[saulo.faria]

Just checked and is not mounted yet. But when executing dmesg I see something important

[ 27.825091] EXT4-fs (sda1): Unrecognized mount option "default" or missing value

What does that mean? should I go ahead and mount it again to the /media/extHD

[saulo.faria]

After executing sudo mount -t auto /dev/sda1 /media/extHD/
I got into the same structure with linux files.
thoughts?

[saulo.faria]

I am unable to restore access to my HDD.

I wonder if what I have done destroyed my files.

I have 2 SD cards.
1 - Running Raspbian (Which I use as a File repository)
2 - Running RaspBMC

As I have removed my Raspbian so then I can troubleshoot the HDD issue on my Win7 Machine I decided to give it a second try booting my Raspberry Pi with the 2 SD.

As the system didn't boot up I re-imaged the SD with RaspBMC, and the installation procedure hang on the screen where it says: "raspbmc cannot be installed to a usb drive"

What I found on RaspBMC website is that

Q: What happens if I plug in a USB device?

A: Raspbmc should mount your device for you at /media/usb* and it will be available for use in XBMC.

Q: Can I install Raspbmc to a USB drive?

A: Yes — but the SD card will still be needed to boot. This may seem futile then, however, the performance gains are admirable. This can be done easily through the Windows installer. For users installing via Python or manually, all that is needed is to create a file called ‘usb’ on the fat32 partition. The installer will then install to the first detected USB drive.

Taking that it may probably got installed on my HDD, would I be able still to recover my files?

Thanks