[SOLVED] Rescue B2 Disk

[PerN]

Hiya,

I have a B2 and a B3.

The B2 will not boot, just blinks forever, not sure what caused it, I hadn't used it for a while.
There are stuff on the (1 TB) disk I'd really like to salvage.

I'm thinking in the lines of using a Linux PC (not that I have one yet, but I guess booting a Linux dist from USB would work) and connect the disk to the PC via USB and then FTP the files to the B3.

The question is : What do I need in order to be able to connect the disk to the PC?


Thanks

[Binkem]

There are several options here:

You can try booting your B2 from a rescue USB. You can find the howto somewhere on the forum.
If you open up the PC you may just connect it to the PC using a sata cable and power cable
You may use an external case and then connect it using esata or USB cables the cases are fairly inexpensive and installing a hdd is less difficult than installing a HDD in a B2/B3.
Or you can buy a HDD docking station, where you only need to place the hdd into the cradle.
It may be that a faulty HDD is the reason why the b2 don't boot.

[PerN]

Thanks,

yeah, I've tried the USB Recovery thingie without success (just keeps blinking).

HDD docking station sounds like the easiest way forward.

[sakaki]

Hi,

one other thing you could try is booting with the Gentoo live-USB for the B2. The image uses UUID-based disk naming, so should boot even if your internal HDD is no longer being recognized as /dev/sda on the B2. There is also a small 'blinktest' image (instructions here) that you can use to quickly check if your USB key will work correctly with your B2 (as not all brands do).

Best, sakaki

[PerN]

Hi thanks for the suggestions,

At first I got really really happy as using a HDD dock seemed to work fine. I could access the content and all looked fine.

But then I made the fatal (it seems) mistake of rebooting before retrieving the files in question (~90 GB) and now I can't access the HDD anymore.

When it tries to mount it i get
"Error mounting /dev/dm-0 at /media/ubuntu/Bubba home1: Command-line `mount -t "ext3" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-0" "/media/ubuntu/Bubba home1"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/mapper/bubba-storage,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so"

Code: Select all

ubuntu@ubuntu:~$ dmesg | tail
[  517.793788] blk_update_request: I/O error, dev sdc, sector 0
[  517.793875] JBD2: recovery failed
[  517.793881] EXT4-fs (dm-0): error loading journal
[  579.776685] scsi_io_completion: 63 callbacks suppressed
[  579.776695] sd 12:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  579.776699] sd 12:0:0:0: [sdc] Sense Key : Medium Error [current] 
[  579.776703] sd 12:0:0:0: [sdc] Add. Sense: Unrecovered read error
[  579.776707] sd 12:0:0:0: [sdc] CDB: Read(10) 28 00 01 2a 55 03 00 00 02 00
[  579.776710] blk_update_request: critical medium error, dev sdc, sector 19551491
[  579.776790] EXT4-fs (dm-0): unable to read superblock
ubuntu@ubuntu:~$ ^C
ubuntu@ubuntu:~$ 

Code: Select all

ubuntu@ubuntu:~$ sudo fsck.ext4 -v /dev/dm-0
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open /dev/dm-0
Could this be a zero-length partition?
ubuntu@ubuntu:~$ 

Any suggestions on how to prodceed? I can't believe I managed to destroy it by looking at it/rebooting.
I am sure the files/data are still there somewhere...

[PerN]

Data salvaged!

By using the TestDisk [1] app I managed to copy the files onto PC's disk without properly mounting the B2 drive.

[1] http://www.cgsecurity.org/wiki/TestDisk

[Comel]

Data salvaged!

By using the TestDisk [1] app I managed to copy the files onto PC's disk without properly mounting the B2 drive.

Sweet, is there a tutorial or something somewhere showing how to do this step by step so I don't mess things up?