On Sun, 21 Mar 2010 07:50:57 -0400 (EDT), Arthur Marsh wrote: > On Sun, 21 Mar 2010 07:28:24 -0400 (EDT), Stephen Powell wrote: >> On Sun, 21 Mar 2010 04:25:45 -0400 (EDT), Arthur Marsh wrote: >>> Hi, I have a DPT 2044W SCSI adaptor in this pc for a non-boot disk ... >> So what's the problem? > > The problem was that the eata SCSI module was not loaded from the initrd > and therefore fsck and mount of the SCSI disk failed. > > I had a look at: > > http://wiki.debian.org/InitramfsDebug > > and temporarily removed eata from /etc/initramfs-tools/modules, ran: > > update-initramfs -u -k 2.6.32-4-686 > > then rebooted into that kernel, specifying break=bottom on the linux > command line in GRUB2. > > cat /proc/modules > > didn't show eata, but did show all the other modules that one would > expect to find at boot-up. Running "modprobe eata" worked, it just > should have been loaded automatically.
OK, there are a couple of things to check. First of all, make sure you have MODULES=most listed in /etc/initramfs-tools/initramfs.conf. Also check /etc/initramfs-tools/conf.d/driver-policy, if it exists. Generally, this file only exists if, during installation, you said you wanted an initial RAM file system with only what is required to boot the system. If this is the case, /etc/initramfs-tools/conf.d/driver-policy will likely exist and specify MODULES=dep. And that overrides what is specified in /etc/initramfs-tools/initramfs.conf. Change /etc/initramfs-tools/conf.d/driver-policy to specify MODULES=most too. For now, do *not* list eata in /etc/initramfs-tools/modules. Then re-run update-initramfs, re-run lilo (if lilo is your boot loader), shutdown and reboot. Let me know the results. -- .''`. Stephen Powell <zlinux...@wowway.com> : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1486357930.20796661269267623424.javamail.r...@md01.wow.synacor.com
