martin, et al, sorry so long in getting back to this. Finally was in a position to work on this a bit. so long sweet uptime. On Thu, Apr 05, 2007 at 12:07:21PM -0700, Andrew Sackville-West wrote: > On Sat, Mar 31, 2007 at 11:45:38AM +0200, martin f krafft wrote: > > also sprach Andrew Sackville-West <andrew@farwestbilliards.com> [2007.03.30.1920 +0200]: > > > Failure: failed to load Module 0 no such module > > > Failure: failed to load Module 1 no such module > > > Failure: failed to load Module 5 no such module > > > > I don't even know what creates those messages. > > I know, its wierd, but it definitely looks like its happening in that > script. > > > > > > looks like it should just interate through the list and load the > > > modules. I have confirmed that it works the way I expect in bash, > > > but it doesn't work properly when booting. for some reason the > > > module names seem to get replaced with just hte numbers "0" "1" > > > and "5". > > > > No, I don't think this is what's happening, but I also don't know > > what is going on. > > > > > I have hacked the script and rebuilt my initrds by commenting out > > > the above section and just putting in a bunch of modprobes and it > > > works. But clearly something wacky is going on here. > > > > Can you edit the script, add set -x at the top and post the output? > > will do. will post that up shortly. sorry for the delay, btw, had to > run out of town. So I returned the script to its original state, and the same problem is still there, running up-to-date etch. I put in set -x as you requested, and it looks like MD_MODULES gets set twice. Initially, its set appropriately as "linear ..." but later it just get set to "0 1 5" which of course causes the modprobe to fail. Unfortunately, it won't boot in this scenario (maybe... I'll try init=/bin/bash) so I've got to rig up a serial console to capture the messages. I'll report back with more. A
Attachment:
signature.asc
Description: Digital signature