Re: [gentoo-user] Can't boot upgraded kerne;

2012-03-13 Thread Mick
On Tuesday 13 Mar 2012 05:36:38 ro...@cs.wisc.edu wrote:
 I recently decided to update my AMD64 box from 2.38 to the new 3.2 kernel.
 I used genkernel all to compile the upgraded kernel but when I go to boot
 I get the following error.
 
 Loading modules
 Determining root device
 
 !!Block device /dev/sdb2 is not a valid root device
 !!Could not find the root block device in .
 Pleas specify another value or press enter for the same, type shell for
 a shell, or qto skip..
 root block device()::
 
 However at this point the computer is hung and I am no longer able to
 input anything. I just switched over to gentoo from bsd a year or so ago
 and am still a newbie at some of the installation procedures but I believe
 I have followed the manual correctly with the only change being that /boot
 is located on the root partition and not a seperate partition. I'm still
 able to use my older kernel without a problem and the only difference that
 I can note between the two is that older kernel seems to load in a bunch
 of modules and starts mdev, I believe, before trying to locate root. I am
 also using Lilo since my motherboard doesn't seem to like grub. Any help I
 could get would be appreciated.
 
 roger
 
 Here is a print out of lilo.conf
 boot=/dev/sdb
 map=/boot/map
 
 prompt
 timeout=50
 default=Windows
 
 image=/boot/kernel-genkernel-x86_64-2.6.38-gentoo-r6
   label=2.6.38
   read-only
   append=real_root=/dev/sdb2
   vga=773
   initrd=/boot/initramfs-genkernel-x86_64-2.6.38-gentoo-r6
 
 image=/boot/kernel-genkernel-x86_64-3.2.1-gentoo-r2
   label=3.2.1
   read-only
   append=real_root=/dev/sdb2
   initrd=/boot/initramfs-genkernel-x86_64-3.2.1-gentoo-r2
 
 
 other=/dev/sda1
   label=Windows
 
 
 Here is a print out of fdisk
 Disk /dev/sdb: 80.0 GB, 80026361856 bytes
 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x37cd3650
 
Device Boot  Start End  Blocks   Id  System
 /dev/sdb1204812584959 6291456   82  Linux swap /
 Solaris /dev/sdb2   *1258496014682111 1048576   83  Linux
 /dev/sdb314682112   156301487708096885  Extended
 /dev/sdb51468416018878463 2097152   83  Linux
 /dev/sdb61888051223074815 2097152   83  Linux
 /dev/sdb7230768646501990320971520   83  Linux
 /dev/sdb865021952   15630148745639768   83  Linux
 
 Here is a print out of fstab
 # /etc/fstab: static file system information.
 #
 # noatime turns off atimes for increased performance (atimes normally
 aren't # needed); notail increases performance of ReiserFS (at the expense
 of storage
 # efficiency).  It's safe to drop the noatime options if you want and to
 # switch between notail / tail freely.
 #
 # The root filesystem should have a pass number of either 0 or 1.
 # All other filesystems should have a pass number of 0 or greater than 1.
 #
 # See the manpage fstab(5) for more information.
 #
 
 # fsmountpointtype
 optsdump/pass
 
 # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
 /dev/sdb2/ext3noatime
   0 1
 /dev/sdb1noneswapsw
 0 0
 
 /dev/sdb5/varext3defaults
1 2
 /dev/sdb6/tmpext3defaults
   1 2
 /dev/sdb7/usrext3defaults
   1 2
 /dev/sdb8/homeext3defaults
1 2
 
 /dev/cdrom/mnt/cdromautonoauto,ro
   0 0
 
 /dev/sda2/mnt/Windowsntfsdefaults
   1 2
 
 proc /procproc
 defaults0 0
 shm/dev/shmtmpfs
 nodev,nouisd,noexec0 0
 
 #tmpfs /var/tmp/portagetmpfs
 size=500M,mode=07770 0


In all likelihood you have not included in your kernel (built in, not as 
modules) the corresponding SATA controller driver.  Run a diff between old and 
new kernel .config to find out what's missing, or cp your old .config into your 
new kernel tree and run 'make oldconfig'.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Can't boot upgraded kerne;

2012-03-13 Thread Bruce Hill, Jr.



On March 13, 2012 at 3:10 AM Mick michaelkintz...@gmail.com wrote:

 On Tuesday 13 Mar 2012 05:36:38 ro...@cs.wisc.edu wrote:
  I recently decided to update my AMD64 box from 2.38 to the new 3.2
kernel.
  I used genkernel all to compile the upgraded kernel but when I go to
boot
  I get the following error.
 
  Loading modules
  Determining root device
 
  !!Block device /dev/sdb2 is not a valid root device
  !!Could not find the root block device in .
  Pleas specify another value or press enter for the same, type shell
for
  a shell, or qto skip..
  root block device()::
 
  However at this point the computer is hung and I am no longer able to
  input anything. I just switched over to gentoo from bsd a year or so
ago
  and am still a newbie at some of the installation procedures but I
believe
  I have followed the manual correctly with the only change being that
/boot
  is located on the root partition and not a seperate partition. I'm
still
  able to use my older kernel without a problem and the only difference
that
  I can note between the two is that older kernel seems to load in a
bunch
  of modules and starts mdev, I believe, before trying to locate root. I
am
  also using Lilo since my motherboard doesn't seem to like grub. Any
help I
  could get would be appreciated.
 
  roger
 
  Here is a print out of lilo.conf
  boot=/dev/sdb
  map=/boot/map
 
  prompt
  timeout=50
  default=Windows
 
  image=/boot/kernel-genkernel-x86_64-2.6.38-gentoo-r6
label=2.6.38
read-only
append=real_root=/dev/sdb2
vga=773
initrd=/boot/initramfs-genkernel-x86_64-2.6.38-gentoo-r6
 
  image=/boot/kernel-genkernel-x86_64-3.2.1-gentoo-r2
label=3.2.1
read-only
append=real_root=/dev/sdb2
initrd=/boot/initramfs-genkernel-x86_64-3.2.1-gentoo-r2
 
 
  other=/dev/sda1
label=Windows
 
 
  Here is a print out of fdisk
  Disk /dev/sdb: 80.0 GB, 80026361856 bytes
  255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x37cd3650
 
 Device Boot  Start End  Blocks   Id  System
  /dev/sdb1204812584959 6291456   82  Linux swap /
  Solaris /dev/sdb2   *1258496014682111 1048576   83  Linux
  /dev/sdb314682112   156301487708096885  Extended
  /dev/sdb51468416018878463 2097152   83  Linux
  /dev/sdb61888051223074815 2097152   83  Linux
  /dev/sdb7230768646501990320971520   83  Linux
  /dev/sdb865021952   15630148745639768   83  Linux
 
  Here is a print out of fstab
  # /etc/fstab: static file system information.
  #
  # noatime turns off atimes for increased performance (atimes normally
  aren't # needed); notail increases performance of ReiserFS (at the
expense
  of storage
  # efficiency).  It's safe to drop the noatime options if you want and
to
  # switch between notail / tail freely.
  #
  # The root filesystem should have a pass number of either 0 or 1.
  # All other filesystems should have a pass number of 0 or greater than
1.
  #
  # See the manpage fstab(5) for more information.
  #
 
  # fsmountpointtype
  optsdump/pass
 
  # NOTE: If your BOOT partition is ReiserFS, add the notail option to
opts.
  /dev/sdb2/ext3noatime
0 1
  /dev/sdb1noneswapsw
  0 0
 
  /dev/sdb5/varext3
defaults
 1 2
  /dev/sdb6/tmpext3
defaults
1 2
  /dev/sdb7/usrext3
defaults
1 2
  /dev/sdb8/homeext3
defaults
 1 2
 
  /dev/cdrom/mnt/cdromauto
noauto,ro
0 0
 
  /dev/sda2/mnt/Windowsntfs
defaults
1 2
 
  proc /procproc
  defaults0 0
  shm/dev/shmtmpfs
  nodev,nouisd,noexec0 0
 
  #tmpfs /var/tmp/portagetmpfs
  size=500M,mode=07770 0


 In all likelihood you have not included in your kernel (built in, not as
 modules) the corresponding SATA controller driver.  Run a diff between
old and
 new kernel .config to find out what's missing, or cp your old .config
into your
 new kernel tree and run 'make oldconfig'.
 --
 Regards,
 Mick


It would not matter that he has his / fs drive controller as a module and
not built in with an initrd. That's the purpose of an initrd image ... to
load modules needed before the kernel is loaded. Now, his initrd might not
be built correctly, but that's another story.

Roger, it looks like you didn't run lilo as 

Re: [gentoo-user] Can't boot upgraded kerne;

2012-03-13 Thread Bruce Hill, Jr.



On March 13, 2012 at 1:36 AM ro...@cs.wisc.edu wrote:

 I recently decided to update my AMD64 box from 2.38 to the new 3.2
kernel.
 I used genkernel all to compile the upgraded kernel but when I go to boot
 I get the following error.

 Loading modules
 Determining root device
 !!Block device /dev/sdb2 is not a valid root device
 !!Could not find the root block device in .
 Pleas specify another value or press enter for the same, type shell
for
 a shell, or qto skip..
 root block device()::

 However at this point the computer is hung and I am no longer able to
 input anything. I just switched over to gentoo from bsd a year or so ago
 and am still a newbie at some of the installation procedures but I
believe
 I have followed the manual correctly with the only change being that
/boot
 is located on the root partition and not a seperate partition. I'm still
 able to use my older kernel without a problem and the only difference
that
 I can note between the two is that older kernel seems to load in a bunch
 of modules and starts mdev, I believe, before trying to locate root. I am
 also using Lilo since my motherboard doesn't seem to like grub. Any help
I
 could get would be appreciated.

 roger

 Here is a print out of lilo.conf
 boot=/dev/sdb
 map=/boot/map

 prompt
 timeout=50
 default=Windows

 image=/boot/kernel-genkernel-x86_64-2.6.38-gentoo-r6
   label=2.6.38
   read-only
   append=real_root=/dev/sdb2
   vga=773
   initrd=/boot/initramfs-genkernel-x86_64-2.6.38-gentoo-r6

 image=/boot/kernel-genkernel-x86_64-3.2.1-gentoo-r2
   label=3.2.1
   read-only
   append=real_root=/dev/sdb2
   initrd=/boot/initramfs-genkernel-x86_64-3.2.1-gentoo-r2


 other=/dev/sda1
   label=Windows


 Here is a print out of fdisk
 Disk /dev/sdb: 80.0 GB, 80026361856 bytes
 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x37cd3650

Device Boot  Start End  Blocks   Id  System
 /dev/sdb1204812584959 6291456   82  Linux swap /
Solaris
 /dev/sdb2   *1258496014682111 1048576   83  Linux
 /dev/sdb314682112   156301487708096885  Extended
 /dev/sdb51468416018878463 2097152   83  Linux
 /dev/sdb61888051223074815 2097152   83  Linux
 /dev/sdb7230768646501990320971520   83  Linux
 /dev/sdb865021952   15630148745639768   83  Linux

 Here is a print out of fstab
 # /etc/fstab: static file system information.
 #
 # noatime turns off atimes for increased performance (atimes normally
aren't
 # needed); notail increases performance of ReiserFS (at the expense of
 storage
 # efficiency).  It's safe to drop the noatime options if you want and to
 # switch between notail / tail freely.
 #
 # The root filesystem should have a pass number of either 0 or 1.
 # All other filesystems should have a pass number of 0 or greater than 1.
 #
 # See the manpage fstab(5) for more information.
 #

 # fsmountpointtype
 optsdump/pass

 # NOTE: If your BOOT partition is ReiserFS, add the notail option to
opts.
 /dev/sdb2/ext3noatime

   0 1
 /dev/sdb1noneswapsw

 0 0

 /dev/sdb5/varext3defaults
1 2
 /dev/sdb6/tmpext3defaults
   1 2
 /dev/sdb7/usrext3defaults
   1 2
 /dev/sdb8/homeext3
defaults
1 2

 /dev/cdrom/mnt/cdromautonoauto,ro
   0 0

 /dev/sda2/mnt/Windowsntfsdefaults
   1 2

 proc /procproc
 defaults0 0
 shm/dev/shmtmpfs
 nodev,nouisd,noexec0 0

 #tmpfs /var/tmp/portagetmpfs
 size=500M,mode=07770 0






Something else ...

LiLO doesn't need/use this real_root=  convention. It knows that
/dev/sdb2 is /dev/sdb2. So, according to your fdisk and /etc/fstab output,
I think this /etc/lilo.conf should work for you:

[code]
# Faster, but won't work on all systems:
compact
# Should work for most systems, and does not have the sector limit:
lba32
# If lba32 does not work, use linear:
#linear
vga=773
# MBR to install LILO to:
boot = /dev/sda
map = /boot/.map
default = Windows
install = /boot/boot-menu.b   # Note that for lilo-22.5.5 or later you
  # do not need boot-{text,menu,bmp}.b in
  # /boot, as they are linked into the lilo
  # 

[gentoo-user] Can't boot upgraded kerne;

2012-03-12 Thread roger
I recently decided to update my AMD64 box from 2.38 to the new 3.2 kernel.
I used genkernel all to compile the upgraded kernel but when I go to boot
I get the following error.

Loading modules
Determining root device
!!Block device /dev/sdb2 is not a valid root device
!!Could not find the root block device in .
Pleas specify another value or press enter for the same, type shell for
a shell, or qto skip..
root block device()::

However at this point the computer is hung and I am no longer able to
input anything. I just switched over to gentoo from bsd a year or so ago
and am still a newbie at some of the installation procedures but I believe
I have followed the manual correctly with the only change being that /boot
is located on the root partition and not a seperate partition. I'm still
able to use my older kernel without a problem and the only difference that
I can note between the two is that older kernel seems to load in a bunch
of modules and starts mdev, I believe, before trying to locate root. I am
also using Lilo since my motherboard doesn't seem to like grub. Any help I
could get would be appreciated.

roger

Here is a print out of lilo.conf
boot=/dev/sdb
map=/boot/map

prompt
timeout=50
default=Windows

image=/boot/kernel-genkernel-x86_64-2.6.38-gentoo-r6
  label=2.6.38
  read-only
  append=real_root=/dev/sdb2
  vga=773
  initrd=/boot/initramfs-genkernel-x86_64-2.6.38-gentoo-r6

image=/boot/kernel-genkernel-x86_64-3.2.1-gentoo-r2
  label=3.2.1
  read-only
  append=real_root=/dev/sdb2
  initrd=/boot/initramfs-genkernel-x86_64-3.2.1-gentoo-r2


other=/dev/sda1
  label=Windows


Here is a print out of fdisk
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x37cd3650

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1204812584959 6291456   82  Linux swap / Solaris
/dev/sdb2   *1258496014682111 1048576   83  Linux
/dev/sdb314682112   156301487708096885  Extended
/dev/sdb51468416018878463 2097152   83  Linux
/dev/sdb61888051223074815 2097152   83  Linux
/dev/sdb7230768646501990320971520   83  Linux
/dev/sdb865021952   15630148745639768   83  Linux

Here is a print out of fstab
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of
storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# fsmountpointtype   
optsdump/pass

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sdb2/ext3noatime 
  0 1
/dev/sdb1noneswapsw   
0 0

/dev/sdb5/varext3defaults 
   1 2
/dev/sdb6/tmpext3defaults 
  1 2
/dev/sdb7/usrext3defaults 
  1 2
/dev/sdb8/homeext3defaults
   1 2

/dev/cdrom/mnt/cdromautonoauto,ro 
  0 0

/dev/sda2/mnt/Windowsntfsdefaults 
  1 2

proc /procproc   
defaults0 0
shm/dev/shmtmpfs   
nodev,nouisd,noexec0 0

#tmpfs /var/tmp/portagetmpfs   
size=500M,mode=07770 0