LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Laptop died (graphic card failure/no boot) and main SSD drive became unreadable. (http://www.linuxquestions.org/questions/linux-hardware-18/laptop-died-graphic-card-failure-no-boot-and-main-ssd-drive-became-unreadable-4175444643/)

yamagami 01-08-2013 08:30 AM

Laptop died (graphic card failure/no boot) and main SSD drive became unreadable.
 
I have just lost my laptop (Thinkpad T61p - graphic card failure/no boot) and to add another blow I cannot read my main SSD drive now which means Iím losing about 4-5 month worth of my lifeís data. Iím trying to recover that drive.

When the laptop died, I took out the SSD drive, put it in a USB sata encolsure, and connected it to another (olde) laptop running Ubuntu (10.04). It worked just fine and I could see my files. Later that evening I tried to use that drive to boot another similar T61p but the laptop wouldnít boot, falling into Grub rescue mode saying there is no file system.
I immediately reconnected it to the USB enclosure and now instead of seeing my files I get nothing. Iím pretty sure the drive was ext4 (default file system for Ubuntu 12.04).

The usual investigation produces the following:

dmesg after connecting the drive:

Code:

[ 1218.296064] usb 2-2: new high-speed USB device number 2 using ehci_hcd
[ 1218.460823] Initializing USB Mass Storage driver...
[ 1218.461481] usbcore: registered new interface driver usb-storage
[ 1218.461483] USB Mass Storage support registered.
[ 1218.473020] scsi5 : usb-storage 2-2:1.0
[ 1218.473104] usbcore: registered new interface driver ums-cypress
[ 1219.472848] scsi 5:0:0:0: Direct-Access        Mass  Storage Device        PQ: 0 ANSI: 0
[ 1219.473941] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 1219.475126] sd 5:0:0:0: [sdb] 195371566 512-byte logical blocks: (100 GB/93.1 GiB)
[ 1219.475561] sd 5:0:0:0: [sdb] Write Protect is off
[ 1219.475564] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 1219.476149] sd 5:0:0:0: [sdb] No Caching mode page present
[ 1219.476152] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 1219.477810] sd 5:0:0:0: [sdb] No Caching mode page present
[ 1219.477812] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 1219.480332]  sdb: sdb1 sdb2 < sdb5 >
[ 1219.483706] sd 5:0:0:0: [sdb] No Caching mode page present
[ 1219.483711] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 1219.483716] sd 5:0:0:0: [sdb] Attached SCSI disk
[ 1237.936096] usb 2-2: reset high-speed USB device number 2 using ehci_hcd

fdisk shows:

Code:

Disk /dev/sdb: 100.0 GB, 100030241792 bytes
255 heads, 63 sectors/track, 12161 cylinders, total 195371566 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c8f75

  Device Boot      Start        End      Blocks  Id  System
/dev/sdb1  *        2048  187117567    93557760  83  Linux
/dev/sdb2      187119614  195371007    4125697    5  Extended
/dev/sdb5      187119616  195371007    4125696  82  Linux swap / Solaris


sudo file -s /dev/sdb1
Code:

harel@yamagami:~$ sudo file -s /dev/sdb1
/dev/sdb1: data

Trying to mount it:
Code:

harel@yamagami:~$ sudo mount -t ext4 /dev/sdb1 /mnt/damo
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
      missing codepage or helper program, or other error
      In some cases useful info is found in syslog - try
      dmesg | tail  or so

After mount attempt, dmesg adds this:

Code:

[ 1417.597997] EXT3-fs (sdb1): error: can't find ext3 filesystem on dev sdb1.
[ 1417.611379] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 1477.287884] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem


How can I recover the drive? Should I use dd to mirror it on an image file locally and experiment with that? Is there a way to extract the data out of it? I have lost lot there since my last backup and it would mean a lot if I could get it back.

TobiSGD 01-08-2013 08:33 AM

Use dd to make an image, then try to mount the partition with Testdisk. If that doesn't work you can try to recover your files with Photorec.
After that you might think about implementing a backup plan.

yamagami 01-08-2013 04:37 PM

Quote:

Originally Posted by TobiSGD (Post 4865345)
Use dd to make an image, then try to mount the partition with Testdisk. If that doesn't work you can try to recover your files with Photorec.
After that you might think about implementing a backup plan.

I'm trying this on the image obtained from dd with testdisk and photorec (and e2fsck etc.). Thanks. As for backup - yes I've always lacked on that department. Serves me right.....

yamagami 01-15-2013 06:29 PM

I didn't learn...
 
As I got a new laptop, I took out the drive off the old one (mechanical) and connected it as usb. Unfortunately the same kind of problem happened to it as well, though this time when the computer boots I get Grub error 17, and fdisk/testdisk/gparted/etc all see the partition as 'unknown'. The partition order is fine. The drive is now now mountable.
As opposed to the dead SSD above, this drive was the main backup, including the recovered files of the SSD above. I'm having a stroke of bad luck.
This link is the output of boot-repair from ubuntu live cd: http://paste.ubuntu.com/1535948/

Any ideas welcome as I'm facing the loss of my digital life of many years.

Thanks
Harel

syg00 01-15-2013 07:35 PM

There is absolutely no reason to boot suspect drives. None.
Looking at that pastebin, I'd be inclined to delete the extended, and let testdisk loose on it. I'd be betting there was at least one primary before that extended - including maybe what shows up there as sda5. We see a lot of threads with errant extended partition allocations after errors.

No need to mention my sigline I guess ...


All times are GMT -5. The time now is 11:15 PM.