Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 17/11/2010, at 6:56am, Dale wrote: ... So now system boots but I can not seem to the network card going. On the lspci -k I think you mean lspci -nn (there is no switch -k) ... The man page shows a -k switch here so maybe what you are booting has a older version or something. I advise Joseph (OP) to use a recent SystemRescueCd. He doesn't say he is, and I assume not - I would assume that SystemRescueCd would have a version of `lspci` supporting the -k flag, as it is based on Gentoo and it works on my Gentoo stable system. http://www.sysresccd.org/ Stroller.
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 11/17/10 13:57, Stroller wrote: On 17/11/2010, at 6:56am, Dale wrote: ... So now system boots but I can not seem to the network card going. On the lspci -k I think you mean lspci -nn (there is no switch -k) ... The man page shows a -k switch here so maybe what you are booting has a older version or something. I advise Joseph (OP) to use a recent SystemRescueCd. He doesn't say he is, and I assume not - I would assume that SystemRescueCd would have a version of `lspci` supporting the -k flag, as it is based on Gentoo and it works on my Gentoo stable system. http://www.sysresccd.org/ Stroller. I think this is the case, I was using an old Gentoo CD so lspci version did not have the -k switch, need to get a newer one. -- Joseph
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 11/17/10 13:57, Stroller wrote: On 17/11/2010, at 6:56am, Dale wrote: ... So now system boots but I can not seem to the network card going. On the lspci -k I think you mean lspci -nn (there is no switch -k) ... The man page shows a -k switch here so maybe what you are booting has a older version or something. I advise Joseph (OP) to use a recent SystemRescueCd. He doesn't say he is, and I assume not - I would assume that SystemRescueCd would have a version of `lspci` supporting the -k flag, as it is based on Gentoo and it works on my Gentoo stable system. http://www.sysresccd.org/ Stroller. I've tried Gentoo ISO first. I've downloaded the latest minimal AMD64 ISO and they will not boot my AMD Athlon 64 processor 3800 (the below ISO boot my other box OK). I've tried: install-amd64-minimal-2010.iso install-amd64-minimal-20101007.iso The system start booting and stops at: Looking for the cdrom ... Attempting to mount media: - /dev/hda This system boots OK older ISO AMD64 - 2008 but not the latest ISO. It seems to me I am not the only one having this problem. I don't know what kind of rubbish they put together lately as ISO :-( OK I've tried as you suggested, http://www.sysresccd.org/ and it works OK. When I boot I have network eth0 and it loads driver forcedeth I've compiled the same driver into my current kernel but there is no eth0, so I'm puzzled, the kernel I'm using is: linux-2.6.31-gentoo-r6 so it is not that old. -- Joseph
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 11/17/10 00:56, Dale wrote: It appears udev is renaming the network card so I would check the udev rules. They are usually in /etc/udev/rules.d and I think it starts from the higher numbers and works its way down. I'm not much of a expert on udev. Dale :-) :-) You are correct previous card setting was blocking eth0 name. Small modification fix it. -- Joseph
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
Joseph wrote: My ASUS A8V motherboard went down so I change it with another ASUS MB M2NPV along with CPU. Both CPU's were AMD so no need to change flags. Have two hard drives both SATA 200G and 500G However, after trying to boot I get: VFS: Cannot open root device sda3 or unknown-block (0,0) In grub.conf I have: root (hd0,0) kernel /boot/kernel-current root=/dev/sda3 pci=noapi noapci When I boot strap and run, df -h it shows all the partition correctly but all showing as: Size: 46G used: 30G avail: 15G So it would seem to me the kernel does not recognized correctly large disk drives; but it this kernel worked correctly with previous motherboard (the one that failed). BIOS is showing both hard drives size: 200G and 500G What to look for? I would start by checking the kernel config. Make sure you have your drive chipset BUILT INTO the kernel and whatever drivers you use for the file system root is on also BUILT IN. Keep in mind, you can't build those as modules. They have to be in the kernel itself. As to the different sizes, not sure. Maybe someone who has seen that will have additional ideas. May be driver related, may be something else. Dale :-) :-)
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 11/16/10 21:04, Dale wrote: Joseph wrote: My ASUS A8V motherboard went down so I change it with another ASUS MB M2NPV along with CPU. Both CPU's were AMD so no need to change flags. Have two hard drives both SATA 200G and 500G However, after trying to boot I get: VFS: Cannot open root device sda3 or unknown-block (0,0) In grub.conf I have: root (hd0,0) kernel /boot/kernel-current root=/dev/sda3 pci=noapi noapci When I boot strap and run, df -h it shows all the partition correctly but all showing as: Size: 46G used: 30G avail: 15G So it would seem to me the kernel does not recognized correctly large disk drives; but it this kernel worked correctly with previous motherboard (the one that failed). BIOS is showing both hard drives size: 200G and 500G What to look for? I would start by checking the kernel config. Make sure you have your drive chipset BUILT INTO the kernel and whatever drivers you use for the file system root is on also BUILT IN. Keep in mind, you can't build those as modules. They have to be in the kernel itself. As to the different sizes, not sure. Maybe someone who has seen that will have additional ideas. May be driver related, may be something else. Dale :-) :-) The BIOS sees both HD but, boot sector is working OK as grub comes up but then I get a message: VFS: Cannot open root device sda3 or unknown-block (0,0) please append a correct root= boot option; here are the available partitions: 0300 4191302 hda driver: ide-cdrom So it seems kernel does not see the sata drives, but how it is possible? Boot partition is on sda Someone suggested that BIOS is seeing different logical layout of cylinders/ heads. In BIOS setup there a choice of IDE mode, AHCI mode, etc -- Joseph
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
Joseph wrote: On 11/16/10 21:04, Dale wrote: Joseph wrote: My ASUS A8V motherboard went down so I change it with another ASUS MB M2NPV along with CPU. Both CPU's were AMD so no need to change flags. Have two hard drives both SATA 200G and 500G However, after trying to boot I get: VFS: Cannot open root device sda3 or unknown-block (0,0) In grub.conf I have: root (hd0,0) kernel /boot/kernel-current root=/dev/sda3 pci=noapi noapci When I boot strap and run, df -h it shows all the partition correctly but all showing as: Size: 46G used: 30G avail: 15G So it would seem to me the kernel does not recognized correctly large disk drives; but it this kernel worked correctly with previous motherboard (the one that failed). BIOS is showing both hard drives size: 200G and 500G What to look for? I would start by checking the kernel config. Make sure you have your drive chipset BUILT INTO the kernel and whatever drivers you use for the file system root is on also BUILT IN. Keep in mind, you can't build those as modules. They have to be in the kernel itself. As to the different sizes, not sure. Maybe someone who has seen that will have additional ideas. May be driver related, may be something else. Dale :-) :-) The BIOS sees both HD but, boot sector is working OK as grub comes up but then I get a message: VFS: Cannot open root device sda3 or unknown-block (0,0) please append a correct root= boot option; here are the available partitions: 0300 4191302 hda driver: ide-cdrom So it seems kernel does not see the sata drives, but how it is possible? Boot partition is on sda Someone suggested that BIOS is seeing different logical layout of cylinders/ heads. In BIOS setup there a choice of IDE mode, AHCI mode, etc It sounds to me like you don't have the drivers for the chipset. If you leave those out or they are modules, it can't see the drives. Keep in mind, just because grub sees the drives does not mean the kernel does. They are two separate things. Grub only passes info on to the kernel. Once you select what you want to boot, grub is out of the picture. Dale :-) :-)
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 11/16/10 21:45, Dale wrote: [snip] The BIOS sees both HD but, boot sector is working OK as grub comes up but then I get a message: VFS: Cannot open root device sda3 or unknown-block (0,0) please append a correct root= boot option; here are the available partitions: 0300 4191302 hda driver: ide-cdrom So it seems kernel does not see the sata drives, but how it is possible? Boot partition is on sda Someone suggested that BIOS is seeing different logical layout of cylinders/ heads. In BIOS setup there a choice of IDE mode, AHCI mode, etc It sounds to me like you don't have the drivers for the chipset. If you leave those out or they are modules, it can't see the drives. Keep in mind, just because grub sees the drives does not mean the kernel does. They are two separate things. Grub only passes info on to the kernel. Once you select what you want to boot, grub is out of the picture. Dale :-) :-) Thanks for the hint. What should I look for? I think lspci list some chipset, MCP51 but kernel is not listing anything on MCP51 -- Joseph
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
Joseph wrote: On 11/16/10 21:45, Dale wrote: [snip] The BIOS sees both HD but, boot sector is working OK as grub comes up but then I get a message: VFS: Cannot open root device sda3 or unknown-block (0,0) please append a correct root= boot option; here are the available partitions: 0300 4191302 hda driver: ide-cdrom So it seems kernel does not see the sata drives, but how it is possible? Boot partition is on sda Someone suggested that BIOS is seeing different logical layout of cylinders/ heads. In BIOS setup there a choice of IDE mode, AHCI mode, etc It sounds to me like you don't have the drivers for the chipset. If you leave those out or they are modules, it can't see the drives. Keep in mind, just because grub sees the drives does not mean the kernel does. They are two separate things. Grub only passes info on to the kernel. Once you select what you want to boot, grub is out of the picture. Dale :-) :-) Thanks for the hint. What should I look for? I think lspci list some chipset, MCP51 but kernel is not listing anything on MCP51 Try lspci -k from the CD. That should tell you what driver the CD is using. Then while in the kernel config, just look for that driver. If in menuconfig, try the question mark key. Then type in the name of the driver and it should show you where it is exactly. Most CDs use the old IDE drivers so you may have to try this site: http://kmuto.jp/debian/hcl/ That should list all the drivers you need for your hardware. Details on the site as to what to post there. Neat site too. Dale :-) :-)
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
On 11/16/10 22:40, Dale wrote: Thanks for the hint. What should I look for? I think lspci list some chipset, MCP51 but kernel is not listing anything on MCP51 Try lspci -k from the CD. That should tell you what driver the CD is using. Then while in the kernel config, just look for that driver. If in menuconfig, try the question mark key. Then type in the name of the driver and it should show you where it is exactly. Most CDs use the old IDE drivers so you may have to try this site: http://kmuto.jp/debian/hcl/ That should list all the drivers you need for your hardware. Details on the site as to what to post there. Neat site too. Dale :-) :-) Thank you, I run lspci -n retyping all the numbers manually :-/ on http://kmuto.jp/debian/hcl/ So now system boots but I can not seem to the network card going. On the lspci -k I think you mean lspci -nn (there is no switch -k) Anyhow, dmesg |grep eth shows: forcedeth :00:14.0 ifname eth0, PHY OUI addr. 00:17:31:83:a1:53 udev: renamed network interface eth0 to eth1 Any idea why is it renaming network interface? I have forcedeth loaded in the kernel but it is not bringing it up :-( -- Joseph
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
Joseph syscon...@gmail.com writes: So now system boots but I can not seem to the network card going. On the lspci -k I think you mean lspci -nn (there is no switch -k) No, he does mean 'lspci -k'. The -k switch lists the kernel driver which is handling each item. If you do this from the CD then you can tell which driver to configure in your kernel.
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
Joseph wrote: On 11/16/10 22:40, Dale wrote: Thanks for the hint. What should I look for? I think lspci list some chipset, MCP51 but kernel is not listing anything on MCP51 Try lspci -k from the CD. That should tell you what driver the CD is using. Then while in the kernel config, just look for that driver. If in menuconfig, try the question mark key. Then type in the name of the driver and it should show you where it is exactly. Most CDs use the old IDE drivers so you may have to try this site: http://kmuto.jp/debian/hcl/ That should list all the drivers you need for your hardware. Details on the site as to what to post there. Neat site too. Dale :-) :-) Thank you, I run lspci -n retyping all the numbers manually :-/ on http://kmuto.jp/debian/hcl/ So now system boots but I can not seem to the network card going. On the lspci -k I think you mean lspci -nn (there is no switch -k) Anyhow, dmesg |grep eth shows: forcedeth :00:14.0 ifname eth0, PHY OUI addr. 00:17:31:83:a1:53 udev: renamed network interface eth0 to eth1 Any idea why is it renaming network interface? I have forcedeth loaded in the kernel but it is not bringing it up :-( The man page shows a -k switch here so maybe what you are booting has a older version or something. -k Show kernel drivers handling each device and also kernel modules capable of handling it. Turned on by default when -v is given in the normal mode of output. (Currently works only on Linux with kernel 2.6 or newer.) It appears udev is renaming the network card so I would check the udev rules. They are usually in /etc/udev/rules.d and I think it starts from the higher numbers and works its way down. I'm not much of a expert on udev. Dale :-) :-)
Re: [gentoo-user] Cannot open root device sda3 or unknown-block (0,0)
=== On Tue, 11/16, Joseph wrote: === Anyhow, dmesg |grep eth shows: forcedeth :00:14.0 ifname eth0, PHY OUI addr. 00:17:31:83:a1:53 udev: renamed network interface eth0 to eth1 Any idea why is it renaming network interface? I have forcedeth loaded in the kernel but it is not bringing it up :-( === The system maps MAC addresses to device names, to try to keep the ordering consistent. The fix, when you change NICs, is: # rm /etc/udev/rules.d/70-persistent-net.rules Then reboot. -- Keith Dart -- -- ~ Keith Dart ke...@dartworks.biz public key: ID: 19017044 http://www.dartworks.biz/ =
