On 2/20/08, Tero Mäntyvaara <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > 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.
