First Boot after Install Fails [Solved]

Installer Issues via Installer -- Not for global upgrades or upgrading individual packages -- ONLY ISSUES WITH INSTALLATION OF THE OS -- Can't get Sabayon installed, than post here, otherwise use correct forums

Moderator: Moderators

First Boot after Install Fails [Solved]

Postby FrancisG » Mon May 24, 2010 11:19

I have Sabayon 5.2 64bit running on my machine, so I have installed 5.2 X86 on my wife's machine - risky!? Her machine has a Promise TX2000 raid card for her XP system, so I had to do hack the anaconda dmraid.py file as per this http://forum.sabayon.org/viewtopic.php?f=50&t=13963&p=80403&hilit=Scanning+for+dmraid+on+drives#p80403 to get it to install. I wanted to use Raid1 and LVM for the root and home directories.
sda1 /boot ext3 sdb1 not used yet
sda2 /swap sdb2 /swap
sda3 and sdb3 are Raid partitions with LVM for / and /home as /dev/sabayon/root and /dev/sabayon/home

After the install, on the first boot I get 'Block device /dev/sabayon/root is not a valid root device...'
At the shell I cannot see any raid or lvm in /dev at all.

Surely Sabayon should boot into LVM on Raid. On my own machine I am not using raid yet, hope to later this week, but it is perfectly happy booting into a system with root in LVM.

Fromthe LiveCD I can modprobe raid1 then activate the LVM with vgchange -a y sabayon and then mount the system. I have to use mount /dev/mapper/sabayon-root rather than mount /dev/sabayon/root to mount, so I tried that in grub.cfg as the real_root, and changed the /etc/fstab as well to match but same message on booting.

Here is uname -a
Code: Select all
Linux sabayon 2.6.33-sabayon #1 SMP Tue Mar 2 20:35:55 UTC 2010 i686 AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux

Here is lspci
Code: Select all
00:00.0 Host bridge: nVidia Corporation nForce2 IGP2 (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 0 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:06.0 USB Controller: NEC Corporation USB (rev 43)
01:06.1 USB Controller: NEC Corporation USB (rev 43)
01:06.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
01:07.0 RAID bus controller: Promise Technology, Inc. PDC20271 (FastTrak TX2000) (rev 03)
01:08.0 SCSI storage controller: Adaptec AIC-7850 (rev 03)
01:09.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46)
01:0a.0 Ethernet controller: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) (rev 11)
02:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)

Here is /boot/grub/grub.cfg
Code: Select all
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_fonts ###
### END /etc/grub.d/00_fonts ###

### BEGIN /etc/grub.d/00_header ###
set default=saved
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set e55e694b-a0b8-4497-aebd-1e96ca692d19
if loadfont /grub/unifont.pf2 ; then
  set gfxmode=1024x768
  # vga= is deprecated, grub2 handles this just fine
  # making grub2 res == linux fb res
  set gfxpayload=keep
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
if sleep --interruptible 0 ; then
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_distro_theme ###
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(sabayon-root)
search --no-floppy --fs-uuid --set aa00aabd-23fb-47d7-a432-87639833492f
insmod png
if background_image /usr/share/grub/default-splash.png ; then
  set color_normal=white/black
  set color_highlight=magenta/black
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_distro_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Sabayon GNU/Linux, with Linux x86-2.6.33-sabayon" {
   insmod ext2
   set root=(hd0,1)
   search --no-floppy --fs-uuid --set e55e694b-a0b8-4497-aebd-1e96ca692d19
   linux   /kernel-genkernel-x86-2.6.33-sabayon ro root=/dev/ram0 ramdisk=8192 real_root=/dev/sabayon/root dolvm init=/linuxrc splash=silent,theme:sabayon console=tty1 quiet resume=swap:/dev/sdb2 real_resume=/dev/sdb2
   initrd   /initramfs-genkernel-x86-2.6.33-sabayon
}
menuentry "Sabayon GNU/Linux, with Linux x86-2.6.33-sabayon (recovery mode)" {
   insmod ext2
   set root=(hd0,1)
   search --no-floppy --fs-uuid --set e55e694b-a0b8-4497-aebd-1e96ca692d19
   linux   /kernel-genkernel-x86-2.6.33-sabayon ro single root=/dev/ram0 ramdisk=8192 real_root=/dev/sabayon/root dolvm init=/linuxrc splash=silent,theme:sabayon console=tty1 quiet resume=swap:/dev/sdb2 real_resume=/dev/sdb2
   initrd   /initramfs-genkernel-x86-2.6.33-sabayon
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

and /etc/fstab
Code: Select all
/dev/sabayon/root       /                       ext4    user_xattr,noatime 1 1
/dev/sda1               /boot                   ext3    user_xattr,noatime,noauto 1 2
/dev/shm                /dev/shm                tmpfs   defaults        0 0
/dev/sabayon/home       /home                   ext4    user_xattr,noatime 1 2
/dev/sdb2               swap                    swap    defaults        0 0
/dev/sda2               swap                    swap    defaults        0 0


Any ideas on how to get the kernel to recognise my LVM on the raid1

Thanks
An Old Gentoo User, Perfect in every way, Modest and Misunderstood!
Intel Core Duo, 4Gb Memory, Nvidia GeForce 9800, DMX6Fire PCI Sound Card
Running Sabayon 5.2 with Linux 2.6.31.12-rt21 kernel - some mods. No Dual Boot.
User avatar
FrancisG
Baby Hen
 
Posts: 8
Joined: Sat Apr 24, 2010 8:23
Location: Eire

Re: First Boot after Install Fails [Solved]

Postby FrancisG » Sun Jun 27, 2010 10:57

I solved this myself, eventually this way:
Alter
GRUB_CMDLINE_LINUX="lvmraid=/dev/md2, /dev/sda3, /dev/sdb3"
or whatever your raid setup is into /etc/default/grub
then update grub
and 'bob's your uncle'!
It is a shame that the anaconda installer does not do this.
An Old Gentoo User, Perfect in every way, Modest and Misunderstood!
Intel Core Duo, 4Gb Memory, Nvidia GeForce 9800, DMX6Fire PCI Sound Card
Running Sabayon 5.2 with Linux 2.6.31.12-rt21 kernel - some mods. No Dual Boot.
User avatar
FrancisG
Baby Hen
 
Posts: 8
Joined: Sat Apr 24, 2010 8:23
Location: Eire

Re: First Boot after Install Fails [Solved]

Postby wolfden » Tue Jun 29, 2010 4:41

FrancisG wrote:I solved this myself, eventually this way:
Alter
GRUB_CMDLINE_LINUX="lvmraid=/dev/md2, /dev/sda3, /dev/sdb3"
or whatever your raid setup is into /etc/default/grub
then update grub
and 'bob's your uncle'!
It is a shame that the anaconda installer does not do this.


Did you file a bug to our bugzilla? Maybe it's something that can be done if submitted :wink:
User avatar
wolfden
Sharecropper
 
Posts: 8822
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Re: First Boot after Install Fails [Solved]

Postby jortax » Tue Dec 07, 2010 23:55

FrancisG wrote:I solved this myself, eventually this way:
Alter
GRUB_CMDLINE_LINUX="lvmraid=/dev/md2, /dev/sda3, /dev/sdb3"
or whatever your raid setup is into /etc/default/grub
then update grub
and 'bob's your uncle'!
It is a shame that the anaconda installer does not do this.


Thanks a lot!
I had the exact same problem tonight and thanks to you I can go to bed before midnight :D
jortax
Young Hen
 
Posts: 20
Joined: Fri Sep 24, 2010 18:54

Re: First Boot after Install Fails [Solved]

Postby karen66 » Thu Sep 01, 2011 13:34

Join to your thanks
It made my life a little easier as well :wink:
karen66
Baby Hen
 
Posts: 1
Joined: Thu Sep 01, 2011 13:32


Return to Installer Issues - Anaconda **Not for Package Manager Stuff**

Who is online

Users browsing this forum: No registered users and 2 guests