Issues with Automatic Extension loading

[busy_intern]

I have TC on a bootable flash drive and I'm trying to automate setup as eventually I'm going to use TC to simulate servers. I have all the needed extensions downloaded and in /tce/optional on my flash drive and in /tce I have the copy2fs.flg and onboot.lst which lists all the extensions. I know that it doesn't seem right but that's the only way I've got this to work.

In /opt/bootlocal.sh I've added mount /dev/sdc1 since that seems to be necessary for this to work. I also use the boot code tinycore tce=sdc1/tce as I think that might be necessary.

The issue arises is that some times but not all the time when I restart TC to test something, the bootup isn't entirly successful as the extension don't get loaded. If I shutdown and move my flash drive to a different usb port sometimes it works perfectly and I didn't nothing different. The screen tends to move fairly fast but after it tries to mount the extensions there is some output that mentions write-through and cache.

I know that's not much to go on but I'll see if I can't get ahold of the output and post it tomorrow.

[gerald_clark]

You do not need the tce= option, as the directory already exists.
You do need the 'waitusb=5' option.
http://tinycorelinux.com/faq.html#bootcodes

[thane]

Second what gerald_clark said. I load extensions off a USB stick and unless I use the waitusb=5 bootcode the box won't recognize it. I boot off CD so I edited the isolinux.cfg file to include that and the other bootcodes I want. There should be a similar file in your USB install you can update (if you don't want to enter bootcodes from the keyboard).

[busy_intern]

I seem to be unable to replicate the issues I was having but as long as it keeps working it's no big deal and if it's just a USB issue then in the end it really won't matter.

The idea of modifing the isolix.cfg file for auto bootcodes sounds interesting. How do you actually add the boot codes to the file?

[busy_intern]

Ok actually got the issue to occur again. I booted like normal but this time I used the pause boot code. I know you guys did say to use waitusb=5 but I've gotten it to work without it so I assumed that it wasn't the cause.

This is basically the screen output I'm getting:

sd 6:0:0:0: [sdb] Attached SCSI removable disk
sd 6:0:0:0: Attached scsi geeric sg2 type 0
Invalid device specified. Ignoring persistent HOME request!
Invalid device specified. Skipping persistent OPT request!
Possible swap partition(s) enabled.
Loading Tiny Core Applications Extensions. . . scsi 7:0:0:0: Direct-Access     Ut163     USB2FlashStorage 0.00 PQ: 0 ANSI: 2
sd 7:0:0:0: [sdc] 1999872 512-byte hardware sectors: (1.02 GB/976MiB)
sd 7:0:0:0: [sdc] Write Protect is off
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] 1999872 512-byte hardware sectors: (1.02 GB/976MiB)
sd 7:0:0:0: [sdc] Write Protect is off
sd 7:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 7:0:0:0: [sdc] Attached SCSI removable disk
sd 7:0:0:0: Attached scsi generic sg3 type 0
Done.
Restoring backup files form /mnt/sdc1/ mounted over /dev/sdc1 Done.
Setting keymap to us Done.
Boot time configuration completed. Press <Enter> to continue.r8169: eth0: link down
mv can't rename 'can't rename '*.php": No such file or directory
sudo: /usr/local/sbin/lighttpd: command not found
sudo: php-cgi: command not found

Those last 3 lines are error messages from failure to execute commands I've placed in bootlocal.sh due to the extensions failing to load. I don't know for sure if this even is the problem I just now that when the extensions aren't loaded this is what I end up seeing.

[jur]

Come back after you have used the boot code, waitusb=5 (or more). usb sticks certainly do take some seconds to get mounted and recognised by the OS even if you are booting from it.

[busy_intern]

I did 5 boots using the waitusb=5 boot code. Two were perfectly fine, the other 3 times I got an Invalid device UUID. So should I just increase the wait time?

[bmarkus]

I have an USB stick which require 10 sec. You can start with a higher valu, like 15 just to see the result and decrease till you find a safe setting.

[^thehatsrule^]

... or use polling, see related thread http://forum.tinycorelinux.net/index.php?topic=5995.0