Mailinglist Archive: opensuse (1196 mails)
| < Previous | Next > |
Re: [opensuse] Why is root device hardcoded in initrd and how couldit be prevented?
- From: Istvan Gabor <suseuser04@xxxxxxx>
- Date: Mon, 18 Jan 2010 16:49:02 +0100
- Message-id: <8134822.59fd90ec.4b5482ee.e12b9@xxxxx>
2010. január 18. 13:54 napon Felix Miata <mrmazda@xxxxxxxxxxxxx> írta:
Actually it was not the partition what I cloned but the directory system. I
created another ext3 filesystem on another partition and used rsync -a command
to copy openSUSE 11.2 to the new partition. So I don't have the same UUIDs. I
don't use partition labels either.
Yes, I also reinstalled grub after adjusting menu.lst but this did not
solve/prevent the issue.
The boot process starts normally but it stops since it can not find a device
which is not needed at all. The root parameter in menu.lst clearly defines
which one is the root disk.
Istvan
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
On 2010/01/18 13:38 (GMT+0100) Istvan Gabor composed:
Recently I had more times boot problems with openSUSE 11.1 and 11.2 after
cloning/copying
the operating system from one partition to another. Even if I adjusted
fstab and boot manager (grub) according to the new location the boot
stopped with errors like this one:
"Waiting for device /dev/disk/by-id/ata-MaxtorXXXXXX-part3 to appear.
Could not find /dev/disk/by-id/ata-MaxtorXXXXXX-part3
Want me to fallback to /dev/disk/by-id/ata-MaxtorXXXXXX-part3 (y/n)"
The device the message cites hosted the root partition of the system before
cloning.
It seems that this information is hardcoded in initrd.
Why is the root device hardcoded in initrd? How could this hardcoding be
prevented?
I successfully cloned one just a few days ago, but I remembered also to
regenerate the uuid of the cloned partition. Having more than one root
partition with identical UUIDs is not good. On first boot of the clone I did
Actually it was not the partition what I cloned but the directory system. I
created another ext3 filesystem on another partition and used rsync -a command
to copy openSUSE 11.2 to the new partition. So I don't have the same UUIDs. I
don't use partition labels either.
generate new initrds, but for unreleated reasons
, not because I knew if I
had to. Grub also needed reinstallation on the clone in order to actually use
the menu.lst from the clone. ATM, I don't remember if I had to do anything
else.
Yes, I also reinstalled grub after adjusting menu.lst but this did not
solve/prevent the issue.
The boot process starts normally but it stops since it can not find a device
which is not needed at all. The root parameter in menu.lst clearly defines
which one is the root disk.
Istvan
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |