LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Desktop (http://www.linuxquestions.org/questions/linux-desktop-74/)
-   -   Boot failed after disk image restore using DD (http://www.linuxquestions.org/questions/linux-desktop-74/boot-failed-after-disk-image-restore-using-dd-4175463997/)

manuel19 05-29-2013 04:16 PM

Boot failed after disk image restore using DD
 
Hi. I have a Desktop computer with 10GB of Hard disk.
I have been using my desktop PC since 2 years ago.

1 Month ago I Made a full backup using DD.

I did this:

dd if=/dev/sdb of=/media/ExternalHDD/sdb.img

Yesterday I accidentatly I drop a glass of water and now my computer mainboard is Burned.

Today I bought a new desktop PC and I tried to restore the backup image from my old desktop.

I did this:

dd if=/media/ExternalHDD/sdb.img of=/dev/sda

When the restored is done, I boot the desktop but when the kernel is uncompressing....booting...blah,blah,bla..h.. at the end it says something like:
...etc
.."can't mount new root"
..etc
"Booting failed"

I don't know why I get this error :S

Maybe is because my previous system was using /dev/sdb and now the new one is using /dev/sda ?

I really don't know.
Please, I need you help.

TobiSGD 05-29-2013 04:40 PM

Quote:

Originally Posted by manuel19 (Post 4961618)
Maybe is because my previous system was using /dev/sdb and now the new one is using /dev/sda ?

Most likely this is the case. Start your system from a live-CD/USB, mount that partition and edit the file /etc/fstab on that partition. Just change any occurrence of sdb to sda and try it again.

Shadow_7 05-30-2013 10:57 AM

It probably is an fstab issue. If it contains /dev/sd?# entries instead of the UUID of the partition, then it probably gets assigned a different /dev/sd?# location by the motherboard at boot. My desktop is like that because I have IDE (PATA) and SATA drives attached. It is always flip flopping the /dev/ names of the drives on boot. UUIDs are the way to go.


# blkid /dev/sda1

or something like that to get the UUID value.


and use:
UUID=00000008-0004-0004-0004-000000000012 / ext3 rw,errors=remount-ro 0 1
instead of:
/dev/sda1 / ext3 rw,errors=remount-ro 0 1
for the fstab entry (/etc/fstab).


Or whatever applies in your case. Replace with the actually UUID and double check for typos. You will likely need to change the bootloader to use the UUID as well. With a root=UUID=ffffffff-ffff-ffff-ffff-ffffffffffff instead of root=/dev/sda1 for the bootloader in terms of options passed to the kernel. And hopefully that does you good. If you're using a distros kernel and it's not ancient you should be mostly okay.

jefro 05-30-2013 03:51 PM

I agree with the others. DD is best for exact hardware copies and fails on some system changes.

When you make an exact bit by bit copy some very specific data is also copied. Grub and other loaders along with any other mount information may now be wrong. Some drastic changes with the size of the drive or other features of this new machine could also affect.


If you did manage to get a good clone, you should easily be able to get data off it. I mount a dd'd image with qemu.

unSpawn 06-12-2013 01:06 PM

Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.


All times are GMT -5. The time now is 03:57 PM.