[NTLUG:Discuss] Lost SSD partition even after all the 'precautions'

[David Simmons]

Guys/Gals,

Around the end of February 2011 - I procured a Crucial RealSSD C300 solid
state drive and installed LinuxMint 10 on it.  Used the variety of
suggestions to run /tmpfs from ram and turn-off atime/dirtime/etc; didn't
use for /home (used magnetic rotational media for that).

Started machine today and got 'init not found' and dropped into
Busybox....uh-oh

after booting with LiveCD - tried:

mint at mint ~ $ sudo mount /dev/sda1 ./sda1
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


uh-oh...so tried:

mint at mint ~ $ sudo fsck.ext4 /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes

fsck.ext4: unable to set superblock flags on /dev/sda1


 then

mint at mint ~ $ sudo fsck.ext4 /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? no

Clear journal<y>? yes

/dev/sda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
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: 161796/7757824 files (0.2% non-contiguous), 1624571/30999808
blocks


still couldn't mount...here's:

mint at mint ~ $ dmesg | tail
[ 3355.968283] ata6.00: cmd ca/00:10:70:0d:81/00:00:00:00:00/eb tag 0 dma
8192 out
[ 3355.968286]          res 51/04:10:70:0d:81/00:00:0b:00:00/eb Emask 0x1
(device error)
 [ 3355.968292] ata6.00: status: { DRDY ERR }
[ 3355.968297] ata6.00: error: { ABRT }
[ 3355.968916] ata6.00: configured for UDMA/33
[ 3355.968927] sd 5:0:0:0: [sda]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 3355.968935] sd 5:0:0:0: [sda]  Sense Key : Aborted Command [current]
[descriptor]
[ 3355.968944] Descriptor sense data with sense descriptors (in hex):
[ 3355.968950]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3355.968967]         0b 81 0d 70
[ 3355.968976] sd 5:0:0:0: [sda]  Add. Sense: No additional sense
information
[ 3355.968984] sd 5:0:0:0: [sda] CDB: Write(10): 2a 00 0b 81 0d 70 00 00 10
00
[ 3355.969001] end_request: I/O error, dev sda, sector 193006960
[ 3355.969029] ata6: EH complete
[ 3355.969036] JBD: recovery failed
[ 3355.969046] EXT4-fs (sda1): error loading journal


then I thought I could use the alternate superblock with:

mint at mint ~ $ sudo e2fsck -b 32768 /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
e2fsck: unable to set superblock flags on /dev/sda1


While I have backups of personal data....I'd like to double-check and get
all of the config files off of this partition before
reformatting/re-installing.  Any ideas?

Thanks - dave

-- 
Those with sight believe what's believable. Those with vision know what's
unbelievable.



-- 
Those with sight believe what's believable. Those with vision know what's
unbelievable.