What do you mean by "exactly what I did", there was a lot of points made in my email.
Do you mean you manually created an initrd? What about the /dev/ directory in your initrd? Did you populate it with the necessary device nodes? There is a minimum set of device nodes you need in your initrd. Typically I just copy all devices that match this list command cd /dev/ ls fd? tty tty? null zero mem ram* kmem initrd console core cloop* lp* random std* hd* sd* md* You may not need all of them but they don't take up any size so it is better to have them. So are you using modules for your SATA? What modules are you loading for that? The new Linux kernel version numbering system is causing a lot of problems, namely that the kernel is under going radical incompatibility changes between build numbers. My rule is that radical incompatibility changes should only happen between major version number changes but the kernel developers don't think that way. It is very possible that a module you needed in kernel 2.6.19 to load SATA driver support is no longer there or requires other modules to be loaded in kernel 2.6.20. My point with this is that the module may have been renamed, moved or changed. Did you take your .config from an older kernel build or did you actually go into the section for SATA support and make sure that the modules are turned on? I do recall that last week I built a 2.6.20 and I had to manually turn SATA support back on because something in the format of the .config changed. Maybe you could add the lsmod program to your initrd and use it to list your modules before you try to mount your root partition. This will let you know what modules loaded correctly. You could also do a cat of your /proc/devices file inside the initrd before you mount to see if the device controller shows up, and then cat /proc/partitions to see if the drive and partition are available. Are you using RAID or LVM or any thing like that? On Mon, 2007-03-12 at 19:55 -0600, Juan Alberto Cirez wrote: > Roy Souther wrote: > > If you include these numbers that you replaced with X's then the > > answer becomes clearer. > > The numbers tell what module for the device is missing. > > > > Aren't all new Dell's coming with SATA drives now? If so then your > > numbers would be some thing like > > unknown-block(8,1) or unknown-block(8,5) > > > > You can boot a kernel with Reiserfs and (S)ATA modules but you need to > > use an initrd to start the system, it will need to contain a copy of > > the modules, insmod and a script to load them. There are programs that > > build initrd's automatically but I find they do a crappy job of it and > > I like to build my initrd files manually. > > > > On Sun, 2007-03-11 at 22:49 -0600, Juan Alberto Cirez wrote: > >> VFS: Cannot open root device "xxx" or unknown-block(x,x) > > > Royce,This is exactly what I did; but then I get the following > error:unable to mount /dev/sda1 on /mnt. no such file or directory... > Royce Souther www.SiliconTao.com Let Open Source help your business move beyond. For security this message is digitally authenticated by GnuPG.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
