On 14Nov20:1843+0100, Juergen Daubert wrote:
On Thu, Nov 20, 2014 at 07:55:51AM -0500, David L. Craig wrote:
On 14Nov20:0634-0500, David L. Craig wrote:
So it appears that in lines 60 and 61, the USB-stick's block device is getting edited out of the candidates. I'll look into what the shell that gets spawned in line 93 sees and report back. Thanks for pointing me at the code involved.
Well, sdh, sdh1, and sdh2 are clearly in /proc/partitions but /init isn't seeing them during the for loop at line 62. I tested with devicetimeout=30 and it still didn't see them. I also tested with root=/dev/sdh1 just to shake it up a little: the first time, the for loop found the CRUX media on /dev/sde (?!), but the second time it failed as before. I am able to successfully run "mount -vv -r /dev/sdh1 /.tmpfs/.media" in the recovery shell and get to the root prompt.
Sorry, but what's the final problem?
On this Gigabyte desktop, it often fails to find the CRUX 3.1 USB-stick. I have no issues on my Acer Aspire 1 netbook. I suspect the race condition noted in the ISO-NOTES is part of this. The intermediate problem, getting a root prompt, is circumvented. The final problem is providing you with any additional diagnostic data you might be interested in; otherwise, I'll get back to installing CRUX on the Gigabyte box and deciding if I want to replace my Debian Sid primary platform with it. I was offering to run /init with some tracing logic added if I could figure out how to update the script before the kernel hands off the boot to PID 1. -- <not cent from sell> May the LORD God bless you exceedingly abundantly! Dave_Craig______________________________________________ "So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe." __--from_Nightfall_by_Asimov/Silverberg_________________