Mailinglist Archive: opensuse (1196 mails)
| < Previous | Next > |
Re: [opensuse] Why is root device hardcoded in initrd and how could it be prevented?
- From: Per Jessen <per@xxxxxxxxxxxx>
- Date: Mon, 18 Jan 2010 13:41:22 +0100
- Message-id: <hj1kti$ko7$1@xxxxxxxxxxxxxxxx>
Istvan Gabor wrote:
Hello Istvan
AFAIK, it's not actually "hardcoded", but generated during the
installation. It's annoying, but the work-around is to rebuild the
initrd when you clone a system.
/Per
--
Per Jessen, Zürich (5.6°C)
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
Hello:
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?
Hello Istvan
AFAIK, it's not actually "hardcoded", but generated during the
installation. It's annoying, but the work-around is to rebuild the
initrd when you clone a system.
/Per
--
Per Jessen, Zürich (5.6°C)
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |