Grub Error Collection [Part 8] [POST GRUB QUESTIONS HERE!]

[lyallp]

Yep, SATA and SCSI where both built as modules - which was fine while booting from IDE.

What gave it away was lsmod showed 'sg' and 'ata_piix' modules.

Sigh...

Thanks for the prompters.

This message has been posted, courtesy of a Gentoo system running off my new SATA drive.

[maartenlambrecht]

When rebooting I have to wait a minute and then there appears a screen that a file couldn't be found.
After this I have to push a button and afterwards the dual boot menu of GRUB appears but without collor. When I select XP it shows me the screen to enter safe mode or to start normal... When I choose Gentoo it doesn't start. File not found.

I use GRUB-static (64bit) and my partition table looks like this:

Code: Select all

sda1      xp 
sda2      boot 
sda3      swap 
sda4      extended 
sda5      root 

my grub.conf file looks like this:

Code: Select all

default 0 
timeout 30 
splashimage=(hd0,1)/boot/grub/splash.xpm.gz 

title=Gentoo Linux 2.6.21-r4 
root (hd0,4) 
kernel /boot/kernel-genkernel-x86_64-2.6.21-gentoo-r4 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda5 udev 
initrd /boot/initramfs-genkernel-x86_64-2.6.21-gentoo-r4 

# Only in case you want to dual-boot 
title=Windows XP 
rootnoverify (hd0,0) 
makeactive 
chainloader +1  

[NeddySeagoon]

maartenlambrecht,

The missing colour suggests that this line

Code: Select all

splashimage=(hd0,1)/boot/grub/splash.xpm.gz

is not correct and the image cannot be found. You therefore get a menu

Code: Select all

Gentoo Linux 2.6.21-r4
Windows XP

of white text on a black background.
There are no obvious errors in your splashimage line.

What filesystem is /boot ?
Do you have a symbolic link of boot pointing to itself like this ?

Code: Select all

boot -> .

look in ls /boot when you are inside the chroot.
If its missing, create it with

Code: Select all

cd /boot
ln -s . boot

[maartenlambrecht]

Thanks NeddySeagoon for the reply!

What filesystem is /boot ?

Boot is formatted as a ext2 partition of 32 mb.

Do you have a symbolic link of boot pointing to itself like this ?
Code:
boot -> .

I don't know what a symbolic link is

How can I change the config file? Chroot like in the handbook like this?

Code: Select all

# chroot /mnt/gentoo /bin/bash
# env-update
>> Regenerating /etc/ld.so.cache...
# source /etc/profile
# export PS1="(chroot) $PS1"

[NeddySeagoon]

maartenlambrecht,

You need to mount all your partitions, then chroot as you suggest. There is a review here

A symbolic link is an alternative name for a a file or directory. e.g. my /boot contains

Code: Select all

$ ls -l /boot
total 21346
-rw-r--r-- 1 root root 1618552 May 27 17:33 2.6.21-gentoo-r2
-rw-r--r-- 1 root root 1618904 Jun 16 10:27 2.6.21-gentoo-r3
-rw-r--r-- 1 root root 1644664 Jul 19 19:53 2.6.22-gentoo-r1
lrwxrwxrwx 1 root root       1 Dec 14  2004 boot -> .
drwxr-xr-x 2 root root    1024 Oct  6  2006 grub
drwx------ 2 root root   12288 Dec 14  2004 lost+found

The first character of the permissions tells you something of the type of file
- is a normal file
l is a symbolic link (boot -> .)
d is a directory

[maartenlambrecht]

Thanks for the useful reply, NeddySeagoon!
I'll give it a try tomorrow. Today it's to late(23:11h).

I'm not used to the table you gave me:
I do not know what the number 1 and 2 means in front of the word 'root'.
And I don't know what the numbers after the word 'root' mean.
Do you know what my /boot should contain?

But I'll look for it tomorrow and if I couldn't find the solution for my problem, I'll post something on this forum.
Thanks for helping me!

[lyallp]

I just thought I would post some info on my experiences when I installed a new drive and cloned my existing system on to it.

My old drive (an IDE disk) was starting to report errors so I bought a new disk (SATA).

The old drive was /dev/hda , the new drive was /dev/sda

I also had to re-build my kernel to enable SATA and LVM as compiled in options (NOT modules) - this caused me hours of pain as the old system would boot from IDE and load the SATA modules, but when I booted the new system, SATA was not available and booting failed. I kept thinking my GRUB setup was wrong.

I then setup LVM and duplicated the Filesystem structure of the old disk, on the new disk. The only non-LVM partitions where the /boot and root partitions - it is all too much hard work having root under LVM control.

I then copied all my data over to the new disk - the only file I changed was the /etc/fstab - to reflect the new drive, rather than the old drive.

I setup so that the old system had /etc/fstab mount all the new partitions under /mnt/new and the new system would mount all the old system partitions under /mnt/old - this way I would know which system I had booted

I updated my old disk GRUB.conf (once I found out what the device id was) to have a new option to boot this cloned system.

I figured out the device id by simply booting my old config, entering GRUB command line mode and using command line completion after typing root (... to find the disk which had the partition layout of the new disk. I then updated /boot/grub/device.map to reflect this.

I copied these changes across to the new disk /boot/grub directory. Basically, the old and new /boot/grub directory where identical.

I installed grub on the new disk using

Code: Select all

grub-install /dev/sda

I guess I could have used

Code: Select all

grub-install --root-directory=/mnt/new/boot /dev/sda 

but as both directories where identical, it seemed pointless.
Anyway, once I changed the boot sequence, the devices changed, so GRUB did not work, it simply repeated GRUB endlessly.
I guessed (luckily) that what would happen was that hd0 (which was the old IDE) and hd1 (which was the new SATA) prior to the BIOS change would swap, so I edited the new disks grub.conf and devices.map to reflect this, rebooted and off it went.
Success. If I boot my new disk, it works, if I boot my old disk, it works. Each disk is capable of booting both.
Cool.

So, here are excerpts of the files, just for reference.
Old /etc/fstab

Code: Select all

# <fs>                  <mountpoint>            <type>  <opts>                  <dump/pass>
LABEL=boot              /boot                   xfs     defaults,noatime        1 1
LABEL=root              /                       xfs     defaults,noatime        1 2
/dev/hda6               none                    swap    sw                      0 0
LABEL=usr               /usr                    xfs     defaults,noatime        1 3
LABEL=var               /var                    xfs     defaults,noatime        1 4
LABEL=home              /home                   xfs     defaults,noatime        1 5
LABEL=tmp               /tmp                    xfs     defaults,noatime        1 6
LABEL=usr/local         /usr/local              xfs     defaults,noatime        1 7
LABEL=opt               /opt                    xfs     defaults,noatime        1 8
LABEL=portage           /portage                xfs     defaults,noatime        1 9
/dev/cdrom              /mnt/cdrom              auto    noauto,ro,user,gid=cdrom 0 0
#/dev/fd0               /mnt/floppy             auto    noauto                  0 0


/dev/sda2               /mnt/new                xfs     auto,defaults,noatime        1 10
/dev/sda1               /mnt/new/boot           xfs     auto,defaults,noatime        1 11
/dev/vg/swap            none                    swap    sw
/dev/vg/home            /mnt/new/home           xfs     auto,defaults,noatime        1 12
/dev/vg/opt             /mnt/new/opt            xfs     auto,defaults,noatime        1 13
/dev/vg/portage         /mnt/new/portage        xfs     auto,defaults,noatime        1 14
/dev/vg/tmp             /mnt/new/tmp            xfs     auto,defaults,noatime        1 15
/dev/vg/usr             /mnt/new/usr            xfs     auto,defaults,noatime        1 16
/dev/vg/usr_local       /mnt/new/usr/local      xfs     auto,defaults,noatime        1 17
/dev/vg/var             /mnt/new/var            xfs     auto,defaults,noatime        1 18

New /etc/fstab

Code: Select all

/dev/vg/swap            none                    swap    sw
/dev/sda2               /                       xfs     defaults,noatime        1 10
/dev/sda1               /boot                   xfs     defaults,noatime        1 11
/dev/vg/home            /home                   xfs     defaults,noatime        1 12
/dev/vg/opt             /opt                    xfs     defaults,noatime        1 13
/dev/vg/portage         /portage                xfs     defaults,noatime        1 14
/dev/vg/tmp             /tmp                    xfs     defaults,noatime        1 15
/dev/vg/usr             /usr                    xfs     defaults,noatime        1 16
/dev/vg/usr_local       /usr/local              xfs     defaults,noatime        1 17
/dev/vg/var             /var                    xfs     defaults,noatime        1 18

/dev/hda5               /mnt/old/               xfs     defaults,noatime        1 20
/dev/hda1               /mnt/old/boot           xfs     defaults,noatime        1 21
/dev/hda7               /mnt/old/usr            xfs     defaults,noatime        1 22
/dev/hda8               /mnt/old/var            xfs     defaults,noatime        1 23
/dev/hda9               /mnt/old/home           xfs     defaults,noatime        1 24
/dev/hda10              /mnt/old/tmp            xfs     defaults,noatime        1 25
/dev/hda11              /mnt/old/usr/local      xfs     defaults,noatime        1 26
/dev/hda12              /mnt/old/opt            xfs     defaults,noatime        1 27
/dev/hda14              /mnt/old/portage        xfs     defaults,noatime        1 28

Old /boot/grub/grub.conf (needs to have the BIOS set to boot the old disk first)

Code: Select all

# Boot automatically after 10 secs.
timeout 10

# By default, boot the first entry.
default 0

# Fallback to the second entry
fallback 1

# Display initial image
#splashimage=(hd0,0)/grub/splash.xpm.gz

# For booting Windows NT or Windows95
title Windows XP - with SATA plugged in
map (hd0) (hd2)
map (hd2) (hd0)
rootnoverify (hd2,0)
makeactive
chainloader  +1


title  Gentoo Linux - IDE Disk
root (hd0,0)
kernel /vmlinuz root=/dev/hda5 vga=306

title  Gentoo Linux - SATA Disk
root (hd1,0)
kernel (hd1,0)/vmlinuz  root=/dev/sda2 vga=306

title  Gentoo Linux - previous IDE
root (hd0,0)
kernel /vmlinuz.old root=/dev/hda5 vga=306

title  Gentoo Linux - previous SATA
root (hd1,0)
kernel /vmlinuz.old  root=/dev/sda2 vga=306

title Windows XP - Without SATA
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
makeactive
chainloader  +1

New /boot/grub/grub.conf (needs to have the BIOS set to boot the NEW disk first)

Code: Select all

# Boot automatically after 10 secs.
timeout 10

# By default, boot the first entry.
default 0

# Fallback to the second entry
fallback 1

# Display initial image
#splashimage=(hd0,0)/grub/splash.xpm.gz

# For booting Windows NT or Windows95
title Windows XP - with SATA plugged in
map (hd0) (hd2)
map (hd2) (hd0)
rootnoverify (hd2,0)
makeactive
chainloader  +1

title  Gentoo Linux - SATA Disk
root (hd0,0)
kernel (hd0,0)/vmlinuz  root=/dev/sda2 vga=306

title  Gentoo Linux - IDE Disk
root (hd1,0)
kernel (hd1,0)/vmlinuz root=/dev/hda5 vga=306

title  Gentoo Linux - previous IDE
root (hd0,0)
kernel /vmlinuz.old root=/dev/hda5 vga=306

title  Gentoo Linux - previous SATA
root (hd1,0)
kernel /vmlinuz.old  root=/dev/sda2 vga=306

title Windows XP - Without SATA
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
makeactive
chainloader  +1

Old /boot/grub/device.map

Code: Select all

(fd0)	/dev/fd0
(hd0)	/dev/hda
(hd1)	/dev/sda
(hd2)	/dev/hdb
(hd3)	/dev/hdd

New /boot/grub/device.map

Code: Select all

(fd0)	/dev/fd0
(hd0)	/dev/sda
(hd1)	/dev/hda
(hd2)	/dev/hdb
(hd3)	/dev/hdd

[maartenlambrecht]

I will give you my error message:

Code: Select all

Booting 'gentoo 2.6.21...'

root (hd0,4)
filesystem type is ext2fs, partition type 0X83
kernel /boot/kernel[]genkernel[]x86_64[]r4 root=/dev/ram0
init= /linuxrc ramdisk=8192 real root=/dev/sda5 udev
error15:file not found

Boot partition is ext2 and root is ext3.

I'm going to try to delete the /boot prefix.

[lyallp]

You look like you are using a ram disk.

Since your root and boot partitions are not under LVM control, a ramdisk is not needed, using a ramdisk just makes things more complicated.

Just ensure that ext2 and ext3 are compiled into your kernel, then have a squiz at my files in my previous post on this list.

Oh, by the way, my /boot partion looks like this...

Code: Select all

  /boot:
  used 5932 available 20888
  drwxr-xr-x  3 root root    4096 Aug  4 00:21 .
  drwxr-xr-x 22 root root    4096 Aug  3 23:56 ..
  -rw-r--r--  1 root root       0 Aug 25  2005 .keep
  lrwxrwxrwx  1 root root      27 Aug  4 00:21 System.map -> System.map-2.6.21-gentoo-r4
  -rw-r--r--  1 root root  981354 Aug  4 00:21 System.map-2.6.21-gentoo-r4
  -rw-r--r--  1 root root  978246 Aug  4 00:10 System.map-2.6.21-gentoo-r4.old
  lrwxrwxrwx  1 root root      31 Aug  4 00:21 System.map.old -> System.map-2.6.21-gentoo-r4.old
  lrwxrwxrwx  1 root root       1 Aug  4 00:21 boot -> .
  lrwxrwxrwx  1 root root      23 Aug  4 00:21 config -> config-2.6.21-gentoo-r4
  -rw-r--r--  1 root root   43194 Aug  4 00:21 config-2.6.21-gentoo-r4
  -rw-r--r--  1 root root   43194 Aug  4 00:10 config-2.6.21-gentoo-r4.old
  lrwxrwxrwx  1 root root      27 Aug  4 00:21 config.old -> config-2.6.21-gentoo-r4.old
  drwxr-xr-x  2 root root    4096 Aug  5 19:44 grub
  lrwxrwxrwx  1 root root      24 Aug  4 00:21 vmlinuz -> vmlinuz-2.6.21-gentoo-r4
  -rw-r--r--  1 root root 2007704 Aug  4 00:21 vmlinuz-2.6.21-gentoo-r4
  -rw-r--r--  1 root root 1995288 Aug  4 00:10 vmlinuz-2.6.21-gentoo-r4.old
  lrwxrwxrwx  1 root root      28 Aug  4 00:21 vmlinuz.old -> vmlinuz-2.6.21-gentoo-r4.old

Note the use of symbolic links - whenever I update my kernel, I don't have to update my grub.conf because my grub.conf uses the non-version specific symbolic link names, which, in turn, point to the version specific files.

[maartenlambrecht]

Thanks lyallp
I deleted ramdisk and changed the bootslplashscreen like your code.
The menu works fine!!!!! Thanks a lot! It's in color.
But I still can't boot gentoo.
Can you tell me plz the exact location of the kernel and initramfs file?
Is that located for me on hd(0,1) or on hd(0,4)
I'm looking forward to enter my gentoo install!

[NeddySeagoon]

maartenlambrecht,

Grub counts drives from 0 and partitions from 0.
If you only have one hard drive, its (hd0 so thats easy. When you have more, how they are identified depends on the BIOS.

You can ask grub during the boot process. At the splash screen, press e.
Navigate to the the root (hd... line and delete characters until it reads

Code: Select all

root (hd

press the tab key and grub will list your drives. Choose one and add it to the root line like this

Code: Select all

root (hd0, 

press tab again. Grub will list all the partitions on hd0. By doing this for all your drives, you can tell which is which, since its unlikely they have the same partition structure.

The kernel is on /boot if you have a /boot partition and a properly installed kernel. For you thats partition (hdX,1).
You need to fill in the number for X.

You can use the grub built in editor to change the in memory copy of grub.conf and find out what works.
That way you can fix grub.conf for real when the system boots.

[lyallp]

Assuming you have 1 disk plugged in, your disk will be hd0

Assuming you created your /boot partition as the first partition on the disk, then /boot will be partition 0.

This puts vmlinuz on (hd0,0)/vmlinuz

Assuming your disk is a SATA disk, then your disk will be /dev/sda (as opposed to an IDE disk, which would be /dev/hda)

Assuming you created your root partition (/) as the second partition, then your root partition will be /dev/sda2 (/dev/sda1 is assumed to be your boot partition for the purposes of this post)

/boot and root (/) are completely separate - do not confuse them. /boot is used only during boot to configure grub and to load the kernel. root (/) is where everything else starts, including all the important programs like ls, ps, etc.

Once a kernel loads from the /boot partition, it needs to be told where to find the root (/) partition, hence the root= option in grub.conf

So, your grub.conf should have this entry...

Code: Select all

title  Gentoo Linux
root (hd0,0)
kernel (hd0,0)/vmlinuz  root=/dev/sda2 vga=306 

All very confusing when you have to completely different ways of specifying partitions on the disk, (hd0,0) and /dev/sda1 would both be the same partition, in this example.

If your boot partition is the second partition on the disk, then change (hd0,0) into (hd0,1)

If you have used an extended partition on your disk, then add 4 to the partition number. ie, instead of (hd0,0) use (hd0,4).

If you have not created a vmlinuz symbolic link, then you will have to put your full kernel filename, as seen in /boot, rather than vmlinuz.

As noted by NeddySeagoon, make the most of your 'command line' in the editor.

type 'root(hd' then use tab
Assuming 'root(hd0,0)/' fills out, you should be able to see your kernel file (amongst other files) by simply pressing tab. It's almost like typing 'ls'.
Once you have identified your kernel filename, put it in and then boot.

[NeddySeagoon]

lyallp,

Nice post.

I would like to add that the root (hd0,0) and the root=/dev/sda3 statements use the term root in two different contexts.
root (hd0,0) is telling grub where to find its files and is in grubspeak
root=/dev/sda3 is thelling the kernel where to find its root filesystem and is in kernelspeak.
The two different uses of the word root are not related and will not be confused by grub or the kernel.

[maartenlambrecht]

thanks for the posts!!!

First of all I'll give you my configuration.

Code: Select all

sata hd:
sda1   xp
sda2   boot
sda3   swap
sda4  -extended-
sda5   linux
sda6   data
sda7   movies
sda8   photos

This is the only hd.

When I try changing the root to root (hd0,1), it still doesn't boot. It shows a black screen without any error message!

The symlink seems to be usefull, but I don't know how to create it with vmlinuz.

My grub.conf file looks like this:

Code: Select all

default 0
timeout 10
splashimage=(hd0,1)/boot/grub/splash.xpm.gz

title=Gentoo Linux 2.6.21-gentoo-r4
root (hd0,1)
kernel (hd0,1)/kernel-genkernel-x86_64-2.6.21-gentoo-r4 root=/dev/sda5 udev
initrd (hd0,1)/initramfs-genkernel-x86_64-2.6.21-gentoo-r4

# Only in case you want to dual-boot
title=Windows XP
rootnoverify (hd0,0)
makeactive
chainloader +1

I hope you can find a solution with this information.

[NeddySeagoon]

maartenlambrecht,

That looks self consistant, which is good.
As you get a blank screen I suspect your own /boot is missing the symbolic link to grub.conf, so the config file is never found.

Can you boot with a liveCD, mount your root and boot partitions

Code: Select all

mount /dev/sda5 /mnt/gentoo
mount /dev/sda2 /mnt/gentoo/boot

Then post

Code: Select all

 ls -l /mnt/gentoo/boot
ls -l /mnt/gentoo/boot/grub

You may ping me on IRC too if you prefer irc.freenode.net #gentoo-uk is usually quiet

[maartenlambrecht]

NeddySeagoon found the solution for my problems. Thanks a lot!!!

The black screen after selecting Gentoo in the GRUB menu:
To solve the first part of my problem, delete the "vga=306" after the kernel name.

In my case this worked but during the booting of Gentoo the 2nd error occured.

Block device /dev/sda5 is not a valid root device:
This error was caused by the genkernel who did not include my sata driver!
To solve this, you can make your own kernel or you can still use genkernel with one option more enabled.
In my case I had to enable VIA sata support.

When rebooting everything worked fine.

[wangzilla]

got everything installed and my stupid xp boots right in after i perform the reboot mentioned under 10.d under the handbook.

i reboot, and BAM xp boots right away, no grub, nothing. just right into xp.

my conf looks like the following:

Code: Select all

default 0
timeout 30
splashimage=(hd1,1)/boot/grub/splash.xpm.gz

title=Gentoo Linux 2.6.21-r4
root (hd1,1)
kernel /boot/kernel-genkernel-x86-2.6.21-gentoo-r4 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sdb4 udev
initrd /boot/initramfs-genkernel-x86-2.6.21-gentoo-r4

# Only in case you want to dual-boot
title=Windows XP
rootnoverify (hd0,0)
makeactive
chainloader +1

i have 2 hd's... primary drive is where i have xp, and my slave drive has a junk partition for music and whatnot (partition 1), partition 2 is linux boot, partition 3 is swap, and partition 4 is root.

i then perform, as the handbook says,

Code: Select all

grep -v rootfs /proc/mounts > /etc/mtab

Code: Select all

grub-install --no-floppy /dev/sdb

i exit from chroot and umount as i am told, reboot, remove the cd, and XP takes over.

what am i missing?

thanks!

[lyallp]

Sounds like your BIOS is booting sda first!

[wangzilla]

Sounds like your BIOS is booting sda first!

awesome, that worked... to a point... i saw the message GRUB then it switched over to an all black screen with a blinky white _ at the top left and nothing else.

since i switched the order of my boot... need i edit my grub to take into account the boot as hd0,1 instead of how it was with hd1,1 ?

[Chris McGee]

Hello there, I re-installed Gentoo yesterday and came across a problem. I'm new(ish) to linux so followed the installation handbook to the letter and it all went flawlessly except for this line in grub.conf:

kernel /boot/kernel-2.6.19-gentoo-r5 root=/dev/hda3 init=/bin/bb

The system booted to a weird prompt with all my drives as read only. I removed the part in bold and it fixed it, it now boots as it is supposed to and everything is working perfectly (for now!) but I don't know what that bit does or whether it is important.

I guess i'm just wondering if I should have that part (or something like it) in my grub.conf and whether it will cause problems not having it?

[lyallp]

Sounds like your BIOS is booting sda first!

awesome, that worked... to a point... i saw the message GRUB then it switched over to an all black screen with a blinky white _ at the top left and nothing else.

since i switched the order of my boot... need i edit my grub to take into account the boot as hd0,1 instead of how it was with hd1,1 ?

Changing boot order may change your GRUB drive specifications (according to the GRUB manual) - it depends on your BIOS.

Sounds like you need to swap your drive numbers around now.

[wangzilla]

Sounds like your BIOS is booting sda first!

awesome, that worked... to a point... i saw the message GRUB then it switched over to an all black screen with a blinky white _ at the top left and nothing else.

since i switched the order of my boot... need i edit my grub to take into account the boot as hd0,1 instead of how it was with hd1,1 ?

Changing boot order may change your GRUB drive specifications (according to the GRUB manual) - it depends on your BIOS.

Sounds like you need to swap your drive numbers around now.

that was what i was thinking but i'm stuck in hell (work) and will have to give it a whirl when i get home.

thanks for your help!

as for bios, i have awdflash something or another.

[wangzilla]

kernel /boot/kernel-2.6.19-gentoo-r5 root=/dev/hda3 init=/bin/bb

from the handbook it lists init=/linuxrc where you have init=/bin/bb so not sure why it'd point to /bin/bb in the first place.

then again, i'm new to it all and just posting an observation lol.

[Chris McGee]

kernel /boot/kernel-2.6.19-gentoo-r5 root=/dev/hda3 init=/bin/bb

from the handbook it lists init=/linuxrc where you have init=/bin/bb so not sure why it'd point to /bin/bb in the first place.

then again, i'm new to it all and just posting an observation lol.

I hadn't noticed that. In the handbook it lists 'init=/linuxrc' for genkernel users but 'init=/bin/bb' for non-genkernel users. As I wasn't using genkernel I put in 'init=/bin/bb'.

Handbook page

Thanks, i'll try putting init=/linuxrc and see if that works.

[wangzilla]

kernel /boot/kernel-2.6.19-gentoo-r5 root=/dev/hda3 init=/bin/bb

from the handbook it lists init=/linuxrc where you have init=/bin/bb so not sure why it'd point to /bin/bb in the first place.

then again, i'm new to it all and just posting an observation lol.

I hadn't noticed that. In the handbook it lists 'init=/linuxrc' for genkernel users but 'init=/bin/bb' for non-genkernel users. As I wasn't using genkernel I put in 'init=/bin/bb'.

Handbook page

Thanks, i'll try putting init=/linuxrc and see if that works.

ahh, ya, i was thinking genkernel, my bad

maybe just cd into that /bin/bb directory and see if there are any config files or anything in there and maybe that will shed light on what is not loading when you remove the /bin/bb command from init.