Author Topic: USB install, /tce does not recognize sda1 or sda2. (Read 8689 times)

glene77is · « **on:** June 12, 2011, 08:47:25 AM »

*(: tcl_forum_USB_bootcode.txt

Have USB, 8G, Cruizer pendrive,
(1) with grub4dos, Puppy Linux (main OS), Parted-Magic in /pmagic, TCL in /tinycore,
(2) with second partition for data (& hopefully /tce). Formatted ext2.
Have HD system with TCL (as tinycore & tce), Puppy frugal, Ubuntu, with grub2.
(3) TCL is the only problem.

------------------------------------------------------------------------------------------------------------------------
Object is to have USB TCL load a USB /tce (ignoring any attached HD system).

------------------------------------------------------------
Problem symtoms:
(1) USB TCL (after bootup) will not recognize the USB sda1 or sda2.
(2) TCL Mount app will show sda1 & sda2 clicked 'open', but Fluff will not open sda1 or sda2.
(3) TCL Control-Panel, Backup-Restore will not recognize USB sda1 or sda2.

Any tips or hints ?

Rich · « **Reply #1 on:** June 12, 2011, 12:08:14 PM »

Hi glene77is
Please post the Tinycore section of your grub2 config file and I'll try to help.

gerald_clark · « **Reply #2 on:** June 12, 2011, 12:10:14 PM »

TC does not automount USB drives.
Only the partition containing /tce will be mounted, and then only if you have the waitusb=5 ( or maybe 10 ) boot code.

glene77is · « **Reply #3 on:** June 12, 2011, 07:48:25 PM »

Quote from: Rich on June 12, 2011, 12:08:14 PM

Hi glene77is
Please post the Tinycore section of your grub2 config file and I'll try to help.

Rich,
Thanks.

No obligation implied, of course.

USB is Booting via grub4dos, into (hd0,0) for OS, having (hd0,1) for DATA,
with Puppy Linux (main OS), Parted-Magic in /pmagic, TCL in /tinycore,
All other OS boot OK, will detect both USB partitions and access r/w as usual.

TCL OS is in /tc-core, with required mods to isolinux.cfg.

USB pendrive Boot code related to TCL:

### TinyCore : several options for testing #############################
title ---------------------------------------------------------
   root (hd0,0)

### grub4dos syntax is '(hd0,0)' & 'kernal ...' & 'initrd ...'
title ---{ TinyCore root(hd0,0) pmedia=usbflash (Standard) (hda5/tce)
   root (hd0,0)
   kernel /tc-core/bzImage pmedia=usbflash quiet
   initrd /tc-core/tinycore.gz

###
title ---{ TEST TinyCore root (hd0,0) pmedia=usbflash tce=(hd0,1)
   root (hd0,0)
   kernel /tc-core/bzImage pmedia=usbflash tce=(hd0,1)/tce quiet
   initrd /tc-core/tinycore.gz

###
title ---{ TEST TinyCore root (hd0,0) pmedia=usbflash (Append UUID) (hd0,1)/tce
root (hd0,0)
kernel /tc-core/bzImage pmedia=usbflash quiet
#   initrd /tc-core/tinycore.gz
APPEND initrd=/tc-core/tinycore.gz quiet waitusb=5:UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6" tce=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"/tce

### info per boot_info.sh sdb1 = "60abc2ba-477e-43af-ae8a-7affc307fa31"
### info per boot_info.sh sdb2 = "8f2b131a-3293-49c5-83b0-d443ea923eb6"

### test this
#PPEND initrd=/tc-core/tinycore.gz quiet waitusb=5:UUID="98F6-837D" tce=UUID="98F6-837D"/tc-e
#PPEND initrd=/tc-core/tinycore.gz quiet waitusb=5:UUID="60abc2ba-477e-43af-ae8a-7affc307a31" tc-e=UUID="60abc2ba-477e-43af-ae8a-7affc307a31"/tc-e
#PPEND initrd=/tc-core/tinycore.gz quiet waitusb=5:UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6" tce=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"/tce

######################################################
Sincew you asked, although there are no problems on the HD,
From my desk-top system , this code is from grub2 which has slightly different syntax:

menuentry "---< T-C >--- Tiny Core at (sda5,Ubuntu)/tinycore --------"
{
   ### grub2 syntax calls to (hd0,5)/tc-core on HardDrive. ### No problems here.
   insmod ntfs
   set root='(hd0,5)'
   linux /tc-core/bzImage quiet
   initrd /tc-core/tinycore.gz

###############################################

Problem:
(1) Booted from USB pendrive 'sda1'. Other OS run OK.
(2) Selecting TCL,
(3) Tiny-Controller , backup/restore, will not accept 'any' absolute filename "/tce" ,
and sda1 & sda2 are not mountable.
Therefore, cannot do a "Backup" to build a "/tce" .

Perhaps I misspelled 'sda'

I have tried 'sda' , 'sdb' , 'hd0,0' , 'hd0,1'
since grub4dos and TCL and Parted-Magic call these differently.

Appreciate any tips !

glene77is

glene77is · « **Reply #4 on:** June 12, 2011, 07:56:48 PM »

Gerald Clark,
I agree.
Have had to add "wait 10" to the POST on my main computer in order to charge certain USB pendrives.
Now I see there is also boot-code that can add additional waits.
Since I am booting from a USB pendrive, it is already charged and running the grub4dos and btldr image.
But, per the suggestion, I will find a proper place to add such instruction and do it. Will not hurt.
Thanks.

glene77is

Rich · « **Reply #5 on:** June 13, 2011, 02:50:31 AM »

Hi glene77is
Sorry, I misread what you were trying to do so I didn't need the grub2 config.
Based on what I found in the grub4dos docs and assuming you want to boot from the first partition
with your apps on the second partition.

### TinyCore : several options for testing #############################
title ---------------------------------------------------------
root (hd0,0)
kernel /tc-core/bzImage quiet waitusb=10:UUID="60abc2ba-477e-43af-ae8a-7affc307fa31"
tce=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"
initrd /tc-core/tinycore.gz

Notes:
1.The "tce=UUID="8f2b.....eb6"" is part of the kernel statement and should be on the same line.
2. Your BIOS should be set to boot from USB before HD.
3. When using the mount tool you should click the button of the drive you wish to mount.
4. Unless I missed something there should be no isolinux.cfg

Hope I got it right, if not then someone familiar with grub4dos might chime in.

glene77is · « **Reply #6 on:** June 13, 2011, 07:41:04 AM »

Quote from: Rich on June 13, 2011, 02:50:31 AM

Rich,
Thanks. Will run the boot-code today.

Will place tce=UUID code as you suggest. Arrangement was on advice by someone else.

Bios always picks off any available USB bootable device, already, but ,
Will try re-arranging the sequence, as suggested.

IsoLinux.cfg is located in the TCL system subdir as:
/tc_core/isolinux/isolinux.cfg

"Mount-Tool" is used prior to running the "Control-Panel", and clicks show 'green' open,
but the "File-Manager" shows no access.

I have run "Boot_Info.sh" to look for any clues, but find nothing unusual.

Thanks for the tips

glene77is

Rich · « **Reply #7 on:** June 13, 2011, 11:32:23 AM »

Hi glene77is

Quote

Bios always picks off any available USB bootable device, already, but ,
Will try re-arranging the sequence, as suggested.

Also make sure you only plug in one USB storage device.

Quote

IsoLinux.cfg is located in the TCL system subdir as:
/tc_core/isolinux/isolinux.cfg

According to what I read here http://diddy.boot-land.net/grub4dos/files/intro.htm grub4dos looks for
a configuration file called menu.lst, that's where these commands belong.

Quote

"Mount-Tool" is used prior to running the "Control-Panel", and clicks show 'green' open,
but the "File-Manager" shows no access.

Just covering all the bases. Someone else once wrote that they could not access their drives even
though they all showed up (in red) when they called up the mount tool.

roberts · « **Reply #8 on:** June 13, 2011, 12:15:08 PM »

http://distro.ibiblio.org/tinycorelinux/faq.html#pendrives

Quote

Just covering all the bases. Someone else once wrote that they could not access their drives even
though they all showed up (in red) when they called up the mount tool.

Typically because of unsupported file system. Most likely NTFS. Starting with v3.7 Tiny Core, read access for NTFS is supported.

coreplayer2 · « **Reply #9 on:** June 13, 2011, 01:57:13 PM »

additionally there should not be any references to syslinux if you're using grub4dos.

Rich · « **Reply #10 on:** June 13, 2011, 03:59:12 PM »

Quote

Typically because of unsupported file system. Most likely NTFS. Starting with v3.7 Tiny Core, read access for NTFS is supported.

This particular individual did not realize they had to click the buttons to mount the drives.

glene77is · « **Reply #11 on:** June 13, 2011, 05:48:33 PM »

TCL,

##########################################################
>>> This is the current "close" solution, thanks to "RICH on TCL forum".
# sda1 is the USB OS partition for bootup,
# sda2 is the USB DATA partition.
# Current boot-code will allow Backup to sda2/tc-e
# Current boot-code does not allow file-manager access to sda1 or sda2, which are Ext2.
# Current boot-code will allow access to all Linux Ext2 partitions, and another USB w Ext2.

### TinyCore : several options for testing per RICH TCL forum #########################
title ---{ TEST : TinyCore RICH TCL forum (sda2/tce sda2/tc-e & drops ram & Apps into my_data.gz )

root (hd0,0)

kernel /tc-core/bzImage quiet waitusb=10:UUID="60abc2ba-477e-43af-ae8a-7affc307fa31" tce=tc-e=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"

initrd /tc-core/tinycore.gz

####################################################
### Close to success & it does not cause Kernal Panic !!!

####################################################

Right, RobertS, NTFS is not involved. Good URL.
Right, Rich, Mount is clicked sda1, sda2, everything is Ext2.
. . . . Still No File-manager access to sda1, sda2, but Backup goes to sda2.
. . . . Have access r/w to a different USB pendrive.
. . . . You are very thorough about 'covering bases'.
Right, Core, SysLinux.cfg is not involved, since the boot files are called directly by grub4dos..

# This boot-code will allow Backup to sda2/tc-e, when I insert the target.
# This boot-code ( & user-options) does not place Applications in /optional or onboot.lst.
# Current boot-code allows access sda2/tc-e & drops ram & Apps into my_data.gz
# First check shows both /tce and /tc-e being used, confusing. Cleanup/Restart.

# This boot-code does not allow file-manager access to sda1 or sda2.
# Was allow option of inserting "tc-e" during Backup/Restore setup.
# Perhaps I forgot to properly setup the Application-Downloader. Cleanup/Restart.
# Does not properly drop Apps into /tc-e/optional nor list in onboot.lst . Cleanup/Restart.
# Mixture of boot-code requirements and user-options during setup of Boot/Restore assignments.
# Will continue to Cleanup/Restart. to test boot-code and user-option combinations.

Notes are not accurate yet. Requires Cleanup/Restart to carefully track procedures/results.
Thanks for the tips.

The Final Result will be a Tiny-Core on USB which is hopefully:
(1) totally independent of the client's HD system which I want to repair
(2) and not alter the client's HD in any way !

Back to my work,
glene77is

Rich · « **Reply #12 on:** June 13, 2011, 06:13:49 PM »

Hi glene77is

In your kernel line you have

Quote

tce=tc-e=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"

I don't know if tce=tc-e=UUID= is legal or not. Maybe one of the smarter people could comment.

Lee · « **Reply #13 on:** June 13, 2011, 08:50:26 PM »

Quote

tce=tc-e=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"

Looks wrong to me. Try

Code: [Select]

tce=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"
Still waiting on the smarter ones, though.

glene77is · « **Reply #14 on:** June 13, 2011, 09:23:34 PM »

Quote from: Rich on June 13, 2011, 06:13:49 PM

Hi glene77is
In your kernel line you have
Quote
tce=tc-e=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"
I don't know if tce=tc-e=UUID= is legal or not. Maybe one of the smarter people could comment.

Rich,
Well, there is another problem, and I think it is a "design characteristic".
###
### TinyCore : several options for testing per RICH TCL forum
title ---{ TEST : TinyCore RICH TCL forum ( sda2/tce )

   root (hd0,0)

   kernel /tc-core/bzImage quiet waitusb=10:UUID="60abc2ba-477e-43af-ae8a-7affc307fa31" tce=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"

   initrd /tc-core/tinycore.gz

###
The code does have some effect in the "sda2" direction, and does not bomb, exactly.

When the simple "/tce" is used everywhere, there is still a problem.

On Booting, TCL will load something from sda2/tce, too fast to read.
Bootup no error sometimes retains the green wallpaper I set.
Mount shows "sda2" already set to green.
Backup/Restore shows "sda2/tce" preset, and will accept an edit.
FileManager, select <TCE> shows "shortcut not available".
FileManager, shows "sda2" empty. (but it is mounted).
FileManager, Edit (show all, use sudo) of fluff.conf comes up as "Read/Write".
. . . Can see that Loc2Path=/mnt/sda2/tce.
. . . Can Save As to /home/tc/fluff_tc.cfg OK.
Application loaded previous as Ace-of-Penguins is saved in /home/tc, not associated with 'optional'.
App-Browser can load the Ace-of-Penguins and it shows 'loading' and 'OK.
App-Browser can try a load again, and it shows 'Already loaded".
Ace-of-Penguins will run from the Application-List OK. This time OK, but not on reboot.
Exit, Reboot, Backup, "sda2/tce", OK, two seconds runtime, and it reboots.
Rebooting into Ubuntu or Puppy in order to use PCMan (root) filemanager,
and I see that the /mnt/sda2/tce/optional subdir is empty, and the onlist.lst is empty.
Rebooting into TCL, per above boot-code, will open TCL as a fresh run,
with no /optional/extensions, no configs, brand spanking new.

I think there is a "design issue" involved:
TCL was designed as a Live-CD utilizing a "frugal" install technique
for saving configs / applications to a hosting HD.
TCL can be installed to a Live-USB utilizing a "frugal" install technique
for saving configs / applications to a hosting HD.
TCL has code for scanning for its components, and may have 'tce' hard coded somewhere.
( I have done the same in applications to simplify the installation,
allowing a few config params to be entered. )

Did I mention that the FileManager Editor will "save-as" and write to any mounted Linux device ? Yes.
Did I mention that the FileManager Editor will "save-as" and read filename lists on Linus devices ? Yes.

I'll pursue this a little further, but I have the "active Option" already to use Parted-Magic Live-USB to do these service tasks, running Only from USB pendrive, completely in RAM. Puppy Linux is the same, R/W from an independent (frugal) install to USB pendrive. So, this investigaton/development is not real urgent, but is Very Interesting ! I have met some sharp tacks on this TCL forum, and you are one !

glene77is

Quote from: Lee on June 13, 2011, 08:50:26 PM

Quote
tce=tc-e=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"

Looks wrong to me. Try

Code: [Select]
tce=UUID="8f2b131a-3293-49c5-83b0-d443ea923eb6"
Still waiting on the smarter ones, though.

########################################################

Rich and Lee,
The last post contained code just as you suggested "tce=UUID . . . ."
(although xxx=ccc=vvv is legal) and the results were encouraging,
but still acts like it needs to have another "/tce/optional"
somewhere else besides my "sda2/tce/optional".

It seems that "/tce" is correct, and that "/tc-e" will not work,
as if there is a hard-coded "/tce" that is causing the code to abort, without error.
. . . maybe there is a "find" for a different "/tce" hard coded,
which would fit right in with the "Live-CD" development,
which requires a co-host Hard Drive for a "frugal" install.
That would fit the "design issue" as I described in the post.

It has been very interesting, and I'll tinker some more, good at that

but I need a new idea on this subject.

The goal is to have TCL on an independent USB pen-drive,
utilizing the USB pen-drive as the host for the "frugal" install !!!

glene77is

Tiny Core Linux

News: