WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

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

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: USB install, /tce does not recognize sda1 or sda2.
« Reply #15 on: June 13, 2011, 06:30:25 PM »
Quote
The goal is to have TCL on an independent USB pen-drive,
utilizing the USB pen-drive as the host for the "frugal" install !!! 

Using the Tiny Core provided install scripts USB-HDD or USB-ZIP for pendrive makes it easy.
To select not too, well, see all the continuing drama above!  ;D
10+ Years Contributing to Linux Open Source Projects.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11221
Re: USB install, /tce does not recognize sda1 or sda2.
« Reply #16 on: June 13, 2011, 06:59:59 PM »
Hi glene77is
At this point I need to ask you a serious question as you seem to be making this harder than it
needs to be. Why are you trying to install Tinycore and it's applications on separate partitions on
your USB drive.

Also:

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

If that's the case I'd highly recommend you take roberts advice. He knows more about Tinycore than
anyone else. If you want to listen to someone sharp, listen to him, I'm just a novice here.

Offline glene77is

  • Newbie
  • *
  • Posts: 31
  • Electrical Science, weightlifting, cycling.
    • personal website
Re: USB install, /tce does not recognize sda1 or sda2.
« Reply #17 on: June 15, 2011, 07:32:29 PM »
Rich,
You have been very encouraging.   
I have mostly completed my work on this little project.
and need to take a break,
let the "dust settle".

The boot-code included works OK. 
Am using it on two USB pendrives now. 
Both run USB OS code isolated from the HD, as I wanted.
Both can call/execute OS already installed on one of my HardDrive systems, as I wanted.

Hi glene77is

*** At this point I need to ask you a serious question
as you seem to be making this harder than it needs to be.   
>>> I am having a great, interesting time, exploring scripting methods,
avoiding dependence on gui objects (which I spent years writing). 

On the other hand, sometimes I must use the new gui tools and various Live-device OS available
to cover my lack of expertise with the differing syntax of grub, grub4dos, grub2, BASH scripting.


Quote
***  Why are you trying to install Tinycore and it's applications on separate partitions on
your USB drive.
>>> Data Security, only.   
I fell into a long-term habit of isolating "created data". 
Single partition should be simpler, as you suggest.

Quote
The goal is to have TCL on an independent USB pen-drive,
utilizing the USB pen-drive as the host for the "frugal" install !!!
If that's the case I'd highly recommend you take roberts advice.
He knows more about Tinycore than anyone else.
If you want to listen to someone sharp, listen to him,
I'm just a novice here.
[/quote]

Quote
>>> RobertS has given advice, and I have seen the work the 'sharp' engineer,
which is why I am spending some time to investigate how to work with it at the scripting level.
I am not prepared to spend many years following in those same foot-steps. 
RobertS is way ahead of me in his field. 


Sorry if I embarrased you.
Think I am tying up my own loose ends on a thread. 

Here is a post of todays 'piddling' and 'mucking' as I push my little project forward.

Everything works OK.  May be some test code as noted.

Boot-Code for my USB pendrive ( main )
with grub4dos controlling
(1) Puppy 5.25 USB ,
(2) Parted-Magic USB ,
(3) calling Puppy 5.25 on Live-CD (if in the CD drive)
with Puppy configs and Save and System.sfs on the Hard-Drive,
(4) Ubuntu on the HD
(5) M$ XP on the HD,
(6) Parted-Magic from the M$ XP partition on the HD:
(7) and other fancy stuff (just to see if it would work.

Everything works OK.  May be some test code as noted.

Quote
# menu.lst produced by grub4dosconfig-v1.7
# 110616, gae, highly altered.
#
#############################################
color blue/cyan yellow/blue white/black cyan/brown
timeout 10
default 1
###
title ==={  USB  Puppy GEEK   sda1  }======
   root (hd0,0)
title ------{^,^}  Lupu 525 find (sdb1/lupu_525)
     find --set-root --ignore-floppies --ignore-cd /lupu_525/initrd.gz
       kernel /lupu_525/vmlinuz   psubdir=lupu_525  pmedia=usbflash  pfix=fsck
       initrd /lupu_525/initrd.gz
title ---{ Lupu 525 find (sdb1/lupu_525) RAM mode \nBoot up Puppy without pupsave
       find --set-root --ignore-floppies --ignore-cd /lupu_525/initrd.gz
       kernel /lupu_525/vmlinuz   psubdir=lupu_525  pmedia=usbflash  pfix=ram,fsck
       initrd /lupu_525/initrd.gz
title ---{ Lupu 525 chainloader (sdb1:PBS)
       chainloader +1
##################33
title ------ EXTRA ------
   root (hd0,0)
title ==={ Parted Magic sda1/pmagic in RAM }===
        root  (hd0,0)
        kernel  /pmagic/bzImage  noapic  load_ramdisk=1  prompt_ramdisk=0  rw  vga=791  sleep=10  loglevel=0  keymap=us
        initrd  /pmagic/initramfs

title ---{^,^}--- Lupu 520 frugal (sda5/pup52005) ---{^,^}---
       find  --set-root  --ignore-floppies  /pup52005/initrd.gz
       kernel  /pup52005/vmlinuz  pmedia=atahd  psubdir=pup52005  pfix=fsck
       initrd  /pup52005/initrd.gz
title ==={ Tinycore Linux sda1/boot  in RAM }===
# needs more tweaking.
#   root  (hd0,0)
#   kernel  /boot/bzImage  quiet
#   initrd    /boot/tinycore.gz

title --- Grub4Dos commandline
       commandline
title --- Reboot computer
       reboot
title --- Halt computer
       halt
###

Everything works OK.  May be some test code as noted.

#####################################################
About TINY-CORE,    TCL method did not work completely on the new USB pendrive.
Needed to manually install MBR and grldr binary.
So,  trying to use some of the new Live-Device-OS gui tools
to cover my lack of expertise with the differing syntax of grub, grub4dos, grub2, BASH scripting.
(1) Used Parted-Magic (gParted) from my HardDrive
to format the new USB pendrive as ext2.
(2) Used TCL on my HD to run Control_Panel => Install_USB
from the kernal on the HardDrive over to the new USB pendrive.   
(3) Used Puppy 5.25 USB pendrive to run grub4dos_config
to send grub4dos to the new USB pendrive, and write a first-run menu.lst.
(4) upgraded the menu.lst to TCL compliant boot-code.
(5) copied Parted-Magic to /pmagic on USB pendrive, added to menu.lst.
(6) added calls to hda1, hda5 on the HardDrive for M$ and Ubuntu.
(7) probably left garbage at the end of the code.

Everything works OK.  May be some test code as noted.

Boot-Code for the new USB pendrive primary for TINY-CORE Linux:
Quote
# menu.lst produced by grub4dosconfig-v1.7
# 110615W, gae, upgraded greatly.
#
color blue/cyan yellow/blue white/black cyan/brown
timeout 10
default 1
#############################################
title ---{ USB pendrive - grub4dos - TinyCore Linux }------------------------
   root (hd0,0)
title ---{ TINY-CORE : Rich, TCL forum ( loads sda1/tce/optional/apps.tcz )---
# \n ( root, kernel+uuid, initrd )
        root (hd0,0)
        kernel  /tc-sys/bzImage  quiet  waitusb=10:UUID="3384ff11-91f0-497b-bcbe-7d88760e2757" tce=UUID="3384ff11-91f0-497b-bcbe-7d88760e2757"
        initrd  /tc-sys/tinycore.gz
title ---{ UBUNTU  - UUID - kernel + root - initrd - HD (sda5)--- \n Direct UUID
       uuid 99c2c0f3-8258-42b7-85dd-0c575f162831
       kernel /vmlinuz root=/dev/sda5 ro
       initrd /initrd.img
title ---{ M$ XP - map - find - chainloader }--- \nBoot up Windows if installed
       map (hd1) (hd0)
       map (hd0) (hd1)
       map --hook
       errorcheck off
       find --set-root --ignore-floppies --ignore-cd  /bootmgr
       chainloader /bootmgr
       find --set-root --ignore-floppies --ignore-cd  /ntldr
       chainloader /ntldr
       find --set-root --ignore-floppies --ignore-cd   /io.sys
       chainloader /io.sys
       errorcheck on
title ---{ M$ XP - map - uuid - chainloader  (sda1:PBS)
       map (hd1) (hd0)
       map (hd0) (hd1)
       map --hook
       uuid 3268A57F68A54289
       chainloader +1
#############################################
title ---{ ADDITIONAL testing required }--------
   root (hd0,0)
title Bootup from HDD\nBootup from the master boot record of the hard disk drive
       map (hd1) (hd0)
       map (hd0) (hd1)
       map --hook
       chainloader (hd0)+1
title Find Grub menu on HDD
       map (hd1) (hd0)
       map (hd0) (hd1)
       map --hook
       errorcheck off
       find --set-root --ignore-floppies --ignore-cd /menu.lst && configfile /menu.lst
       find --set-root --ignore-floppies --ignore-cd /boot/grub/menu.lst && configfile /boot/grub/menu.lst
       find --set-root --ignore-floppies --ignore-cd /grub/menu.lst && configfile /grub/menu.lst
       errorcheck on
       commandline
title Find Grub2\nBoot up grub2 if installed
       find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
       kernel /boot/grub/core.img
title Grub4Dos commandline\n(for experts only)
       commandline
title Reboot computer
       reboot
title Halt computer
       halt
###


Everything works OK.  May be some test code as noted.

So,  Thanks for your encouragement.
Today has been interesting
and will take a break from this, let the "dust settle down".

Have a call.    Later.

---{^,^}--- glene77is --- Electricity is Shocking