Page 3 of 3 FirstFirst 123
Results 21 to 29 of 29

Thread: HOWTO: recover lost partition after unexpected shutdown (Lucid)

  1. #21
    Join Date
    Oct 2006
    Beans
    Hidden!

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    dentaku65 .....

    THANK YOU THANK YOU THANK YOU THANK YOU!

    Your solution worked perfectly. I thought I'd lost the contents of the drive for good.

    Again, thank you.

  2. #22
    Join Date
    Mar 2012
    Beans
    1

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    Thank you!!!
    You save a lot of my time!!!

  3. #23
    Join Date
    Apr 2012
    Beans
    17

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    zillions of thanks!! you are a life saver dentaku65 !!!

  4. #24
    Join Date
    May 2010
    Beans
    6

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    So this thread is the gift that keeps giving. Thank you dentaku!

  5. #25
    Join Date
    Jul 2012
    Beans
    1

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    Seriously, thank you! I had the exact same problem and your solution was perfect. Your original post keeps giving.

  6. #26
    Join Date
    Jun 2008
    Location
    Opp, AL. USA
    Beans
    114
    Distro
    Ubuntu 10.04 Lucid Lynx

    Talking Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    Wow...quick and easy!

    Thanks so much for sharing

    Allen
    Ubuntu...set your computer free!
    Linux User: 216754
    Alabama

  7. #27
    Join Date
    Sep 2012
    Beans
    1

    Smile Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    Quote Originally Posted by dentaku65 View Post
    Two days ago "someone" took out brutally (but without intention) the power supply of my box; when I reboot the machine I've got this message just after the Grub was loaded:
    Code:
    No init found. Try passing init= boot arg
    BusyBox v1.10.2 (Ubuntu 1:1.10.2.2ubuntu7) built-in shell (ash)
    Mmm, I've never seen this, but I quickly understood that my box was seriously damaged, the access to my data was impossible; user in panic

    After two days of trying to fix the issue I've been able to get back my disk intact; I know, I'm a pretty lucky folk.

    First to all this "guide" worked for me and for my case; for what I've understood the problem was regarding something about EXT4 filesystem that was locking the access to the disk due to the unexpected shutdown (of course); Grub was ok, hardware disk was ok; I'm not so deep involved in the knowledge of the filesystem stuff, but I had the high suspect that the inode structure was denying the system to be mounted/accessed for some pending operations.

    At this moment I've created a USB key with the live of Ubuntu Rescue Remix http://ubuntu-rescue-remix.org/ and I booted the machine with this distro.

    As a first step I've just list my partitions (sda in my case it's the only drive):
    Code:
    sudo fdisk -l /dev/sda
    
    Disk /dev/sda: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000619b6
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1       29844   239721898+  83  Linux
    /dev/sda2           29845       30401     4474102+   5  Extended
    /dev/sda5           29845       30401     4474071   82  Linux swap / Solaris
    The damaged partition, in my case, was /dev/sda1.
    Now I've tried to do an fsck:
    Code:
    sudo fsck -yv /dev/sda1
    but
    Code:
    fsck: Device or resource busy while trying to open /dev/sda1
    Filesystem mounted or opened exclusively by another program?
    What? The disk was obviously not mounted (although I did an umount); no way, I was not able to do an fsck on that partition.

    I've tried everything:
    • Create an image with dd and mount the image after an fsck (the image was unusable due to an arror in the filesystem)
    • Back-up the partition with PhotoRec (the files saved were really trivial)
    • Mount the disk as slave (the Ubuntu Rescue freezed trying to mount it)

    I've was almost to give up and prepare myself to format the disk, when I came across this technical document (for EXT3)
    http://planet.admon.org/using-altern...to-check-ext3/
    So I decided to try it as last resource (remove the first inode), based on consideration that all my data was already lost.
    Code:
    sudo debugfs -w /dev/sda1
    debugfs 1.41.11 (14-Mar-2010)
    debugfs:  clri <8>
    debugfs:  quit
    Then I've launch fsck:
    Code:
    sudo fsck -yv /dev/sda1
    but
    Code:
    fsck: Device or resource busy while trying to open /dev/sda1
    Filesystem mounted or opened exclusively by another program?
    Damn! No way; but I was thinking that maybe a reboot (*) was needed.
    (*) to reboot with Ubuntu Rescue I've used ALT+PrnScreen+r+e+i+s+u+b instead of normal reboot because the normal reboot was not working

    Then I've launch fsck again:
    Code:
    sudo fsck -yv /dev/sda1
    and now this time worked!
    Fsck fix the filesystem errors; I've had not need to do a tune2fs as stated in the document reported above for the re-creation of the journalized filesystem.

    Rebooted the machine with my disk and everything is all there.
    Happy user.
    Hidentaku65,

    Thanks a lot .. the following command worked for me..\

    sudo fdisk -l /dev/sda

    Regards

    Pankaj C

  8. #28
    Join Date
    Jan 2010
    Beans
    93
    Distro
    Ubuntu

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    Thanks for great tutorial

  9. #29
    Join Date
    Oct 2012
    Beans
    1

    Re: HOWTO: recover lost partition after unexpected shutdown (Lucid)

    Thank you!

Page 3 of 3 FirstFirst 123

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •