Re: new disk results in boot problem

On Fri, Jun 29, 2007 at 12:01:00PM +0200, nicals wahlgren wrote:
Normally I am using one sata disk, no problem to boot from it. (using
amd64 and sid, kernel 2.6.21.2-amd64)
But when I add another sata or ide disk from old Debian systems the
system ends up in initramfs.
BIOS still says it boots from original disk.

How do I keep the system to boot from original sata disk when adding
more disks?

You may find that it _is_ booting from the origional sata disk but that,
once the kernel is booting, it can't find the root partition because the
kernel has decided that the boot disk is sdb instead of sda.

I think you've run into to the oft-reported device renaming issue. The
consesnus answer seems to be to use volume names on kernel boot lines
and in fstab instead of device names. See the mount man page under -L
label, and the similar section near the top of the fstab man page.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Broken loader on 7.1-STABLE?
    ... I think the boot loader is ok, because I can load old amd64 kernel structures, but no newer one on this hardware. ... the appropriate disk controllers were found/probed and that the disk devices were found on the disk controllers? ...
    (freebsd-stable)
  • Re: maximum hard drive size in Latitude cpi
    ... > actually written a boot loader they won't be so adamant about how "Windows ... > of the disk, and while it is being read off of the disk the machine is ... > limitatoins of that BIOS. ... After that the kernel takes over. ...
    (comp.sys.laptops)
  • Re: Broken loader on 7.1-STABLE?
    ... make kernel, etc... ... I attempted to boot into single user to run mergemaster, installworld, etc.. ... the appropriate disk controllers were found/probed and that the ... I was wondering if anyone else was seeing loader break after updating ...
    (freebsd-stable)
  • Re: SCSI controller PCI slot change
    ... But with V5.1* it should be even easier and you don't have to hack the kernel configuration, because the device mapping is dynamic there. ... When you boot the kernel it walks through the hardware and maps all found hardware to appropriate device files. ... Therefore, if you have had a disk in your Tru64 V5.* machine at least once, it keeps that recorded until you delete it and whenever you bring that disk back into the machine and place it somewhere (on any SCSI bus) the OS will bring it up with the original device file mapping. ...
    (comp.unix.tru64)
  • Re: Linux Router & Fwall - old bios - wont mount root
    ... Both boot and swap are well within the first ... Once GRUB has loaded the kernel, ... With 9.3, you should be able to do about a 500MB install, ... which seems to indicate that you have a problem with the disk. ...
    (alt.os.linux.suse)