Hi All,
I have 2x SSD drives and some other drives on an Ubuntu server. This morning the power had gone out at 2 AM and after getting the server up and running, the 2x SSD drives are not mounting. My root, var etc partition are ok (because they are not on the SSD).
I am hoping someone can help me to recover the data from the 1st or 2nd SSD drive. The 1st SSD drive holds a virtual machine and my approach for the backup was to freeze the machine and copy it to the 2nd SDD and then unfreeze the VM. What I didn't do (and should have done) was to copy the VM from the 2nd SSD to an external drive. I have a UPS on the server which didn't shutdown the server gracefully. I thought I would be able to use the 2nd SSD if an error occured on the first but the power outage has taken both SSD's (even though it would be idle at the time). Anyway lessons learnt...
I have gone through the following forum links which mimic the same scenario that I have but I am still at a dead end.
http://ubuntuforums.org/showthread.php?t=1804435
http://askubuntu.com/questions/10605...o-length-error
http://ubuntuforums.org/showthread.php?t=1854308&page=2
I believe I am using the ext4 partition with no lvm setup.
The details for my server are as follows:
So I tried to recover the super block which didnt work:Code:dileepa@server:~$ cat /etc/issue Ubuntu 10.04.4 LTS \n \l dileepa@server:~$ uname -a Linux transcohq 2.6.32-26-generic-pae #48-Ubuntu SMP Wed Nov 24 10:31:20 UTC 2010 i686 GNU/Linux dileepa@server:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/md4 during installation UUID=73f56bf0-80b7-4dfa-b454-28a194ebc400 / ext3 errors=remount-ro 0 1 # /boot was on /dev/md0 during installation UUID=a8abf5f0-3858-40bd-bec4-5988d5f56e62 /boot reiserfs notail 0 2 # /tmp was on /dev/md3 during installation UUID=f4ebe1b2-fb21-4a12-a701-cc07ed627c6b /tmp reiserfs defaults 0 2 # /var was on /dev/md2 during installation UUID=b90a41f8-0a59-4421-be3d-b1fdc5db4350 /var ext3 defaults 0 2 # swap was on /dev/md1 during installation UUID=84ec317e-2147-4acd-83cb-aa960541c2b4 none swap sw 0 0 /dev/sde1 /backup ext4 defaults 0 2 /dev/sda1 /vm01 ext4 defaults 0 2 /dev/sdb1 /vm02 ext4 defaults 0 2 dileepa@server:~$ ls /dev/sd* /dev/sda /dev/sdb /dev/sdc /dev/sdc2 /dev/sdc4 /dev/sdc6 /dev/sdd1 /dev/sdd3 /dev/sdd5 /dev/sde /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdc3 /dev/sdc5 /dev/sdd /dev/sdd2 /dev/sdd4 /dev/sdd6 /dev/sde1
I tried testdisk which didnt find any partitions after doing a deep search. I ran the following command but I am not sure where the logs etc are from testdisk to upload it.Code:dileepa@server:~$ sudo e2fsck -f /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo mke2fs -n /dev/sda1 mke2fs 1.41.11 (14-Mar-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 7815168 inodes, 31258465 blocks 1562923 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 954 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 dileepa@server:~$ sudo e2fsck -f -b 32768 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 32768 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 98304 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 163840 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 229376 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 294912 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 819200 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 884736 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 1605632 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? dileepa@server:~$ sudo e2fsck -f -b 2654208 /dev/sda1 e2fsck 1.41.11 (14-Mar-2010) e2fsck: Invalid argument while trying to open /dev/sda1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> dileepa@server:~$
dd is also unable to read the /dev/sda1 partitionCode:dileepa@server:~$ sudo testdisk /log /debug /dev/sda TestDisk 6.11, Data Recovery Utility, April 2009 Christophe GRENIER <grenier@cgsecurity.org> http://www.cgsecurity.org TestDisk exited normally.
I tried fixparts and this also was not able to read the MBRCode:dileepa@server:~$ sudo dd if=/dev/sda1 of=/dev/null count=8 dd: reading `/dev/sda1': Input/output error 0+0 records in 0+0 records out
I also ran the smart tool which is not supported i believeCode:dileepa@server:~$ sudo fixparts /dev/sda FixParts 0.8.4 Loading MBR data from /dev/sda Unable to read MBR data from '/dev/sda'! Exiting!
My 2nd SSD is basically a copy of the 1st SSD with the same partition format of /dev/sdb1 and I have tried the above commands on sdb1 and it also outputs the same results and I am not able to recover the partition information.Code:dileepa@server:~$ sudo smartctl -l selftest /dev/sda1 smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dileepa@server:~$ sudo smartctl -l selftest /dev/sda1 -T permissive smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Short INQUIRY response, skip product id Device does not support Self Test logging
Given my scenario, am I able to recover the partition by using any partition recovery program or is there something else I should try?
Thank you in advance.
Adv Reply
Bookmarks