Re: Multiple SATA disks, two OSs and booting problem

On 2/20/08, Tero Mäntyvaara <termant@gmail.com> wrote:

Owen Townend wrote:
>
>
> On 2/20/08, *Tero Mäntyvaara* <termant@gmail.com
> <mailto:termant@gmail.com>> wrote:
>
>     Hi,
>
>     I have got motherboard that has support for four (4) SATA devices. I
>     have installed Debian 4.0r2 AMD64 on filesystem witch has been build
>     on top of LVM system. LVM is on top of software-raid1 device md0 with
>     two SAMSUNG SP1614C (SATA) disks. Everything works well.
>
>     But if I connect two other disks (SATA2), there is volume group (named
>     VG1) on those disks and KnoppMyth OS installed on one partition of the
>     other disk, booting into Debian fails.
>
>     Further investigated: If I connect either of the two KnoppMyth VG1
>     disks
>     Debian boots well.
>
>     And while all disks connected booting into KnoppMyth goes well.
>
>     Here is the output:
>     kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8)
>     kinit: trying to resume from /dev/mapper/VG0-LV--swap
>     Attempting manual resume
>     kinit: No resume image, doing normal boot...
>     resume: libgcrypt version 1.2.3
>     resume: Could not read the image
>     Done.
>     kjournald starting. Commit internal 5 seconds
>     EXT3-fs: mounted filesystem with ordered data mode.
>     Begin: Running /scripts/local-bottom ...
>     Done.
>     Done.
>     Begin: Running /scripts/init-bottom ...
>     mount: Mounting /root/dev on /dev/.static/dev failed: No such file or
>     directory
>     Done.
>     mount: Mounting /sys on /root/sys failed: No such file or directory
>     mount: Mounting /proc on /root/proc failed: No such file or directory
>     Target filesystem doesn't have /sbin/init
>
>     BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash)
>     Enter 'help' for a list of built-in commands.
>
>     /bin/sh: can't access tty; job control turned of
>     (initramfs)
>
>
>     Here is the illustration of the disks:
>     Debian:
>     ------------------------------
>     FS:
>         /boot (LV-dir-boot)
>         /usr (LV-dir-usr)
>         /var (LV-dir-var)
>         /home (LV-dir-home)
>         /usr/local (LV-dir-usr-local)
>         / (LV-root)
>         /tmp (LV-dir-tmp)
>         swap (LV-swap)
>     ---------------------------------
>     LVM:
>         LVs:
>             LV-dir-boot
>             LV-dir-usr
>             LV-dir-var
>             LV-dir-home
>             LV-dir-usr-local
>             LV-root
>             LV-dir-tmp
>             LV-swap
>         VG:
>             VG0
>     ----------------------------------
>     RAID:
>         md0 (RAID1): hde1, hdg1
>     ----------------------------------
>     Partitions:
>         hde
>            hde1 (Auto RAID)
>         hdg
>            hdg1 (Auto RAID)
>     ----------------------------------
>     Disks:
>         SAMSUNG SP1614C (hde)
>         SAMSUNG SP1614C (hdg)
>     ----------------------------------
>
>     KnoppMyth:
>     ------------------------------
>     FS:
>         / (sdb1)
>         swap (sdb2)
>     ---------------------------------
>     LVM:
>         LVs:
>             myth
>         VG:
>             VG1 (sda2, sdb3)
>     ----------------------------------
>     Partitions:
>         sda
>             sda1 (linux swap)
>             sda2 (linux LVM)
>         sdb
>             sdb1 (linux)
>             sdb2 (linux swap)
>             sdb3 (linux LVM)
>     ----------------------------------
>     Disks:
>         SAMSUNG HD300LJ (sda)
>         SAMSUNG HD321KJ (sdb)
>     ----------------------------------
>
>
>     Tero Mäntyvaara
>
>
>
>     --
>     To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>     <mailto:debian-user-REQUEST@lists.debian.org>
>     with a subject of "unsubscribe". Trouble? Contact
>     listmaster@lists.debian.org <mailto:listmaster@lists.debian.org>
>
>
> Hey,
>   Looks like it can't find the right disks/partitions to boot from.
> The order may be being re-arranged when you attach them all at once.
>   Could be an issue with identification, are you using device paths or
> uuid's in grub?
>   On the subject of grub, what's your boot setup? Where is the boot
> manager installed and what's in your menu.1st (or equiv non-grub) ?
>   If in doubt post your /boot/grub/menu.1st
>
> Just a thought.
> cheers,
> Owen.
Hi,

LILO has installed in system by default. Installation target was
/dev/md0 and I remember that there was some problems with that in
installer. Here is also content of the lilo.conf:

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt' (if you have created it), or   |
# | install a new kernel.  The computer will most likely fail to  |
# | boot if a kernel-image post-install script or you don't       |
# | remember to run `lilo'.                                       |
# |                                                               |
# +---------------------------------------------------------------+

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/md0

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/mapper/VG0-LV--root

# This option may be needed for some software RAID installs.
#
raid-extra-boot=mbr-only

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#    prompt
#    delay=100
#    timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=

#
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
    label=Linux
    read-only
#    restricted
#    alias=1

    initrd=/initrd.img

image=/vmlinuz.old
    label=LinuxOLD
    read-only
    optional
#    restricted
#    alias=2

    initrd=/initrd.img.old

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#    label=HURD
#    restricted
#    alias=3

Tero Mäntyvaara