Tiny Core Extensions > TCE Q&A Forum

Help getting tce's to persist on usb flash drive

(1/3) > >>

padr:
Hi all - this is my first post - hope I am doing things properly. I have been reading about Linux for some time and recently taken the plunge and have downloaded and successfully booted/explored live cd's for Puppy Linux, DSL and now Tiny Core. I am still very much at the learning stage !

My setup
Booting Tiny Core from CD with no problems. Can install tce's but cannot get them to persist ( saving to USB Flash Drive) across sessions/reboot.

USB drive is 2Gig. Have partitioned it, using Gparted under Puppy Linux, into sda1 and sda2 - file systems both  type ext2 - sda1 partition set as boot . Also set up tce directory on sda1 using Puppy Linux. In fact can boot Puppy from the USB so it seems the basics are in order. This post is being made from Puppy ( booted from the USB drive - I am still too much of a learner to be able to set the USB for multiboots so am only booting TinyCore from CD).

Booted from CD several time using boot code tce=sda1 and waitusb=10 but unable to get persistence of installed tce's. Booted aging using these codes but also pause bootcode to see any error messages.

Error messages obtained .
Buffer I/O error on SDA1 ( several times)
mount: you must specify the filesystem type
chown: /mnt/sda1/tce: no such file or directory

I can see sda1 in Puppy and also see the tce directory so it appears to exist and the USB appears to be operational but for some reason Tiny Core cannot mount ?

As I have said I am very much a newbie/learner and may be missing something obvious - hope the above is sufficient ( and not too long or rambling !) for somebody to advise me or point me in the right direction

Help!

^thehatsrule^:
After a while in TC, can you mount sda1?  Anything in `dmesg`?

padr:
Thanks for your reply

No - still cannot mount sda1 ( using Mount Tool on Control Panel ) even after a little while say 5 or 10 mins.

When I run 'dmesg' there are mutilple messages along the lines of :
"attempt to access beyond end of device
sda:rw=0,want=2040263, limit=1"

Also a number of mesages along the lines of :
"Buffer I/O error on device sda1, logical block"

In fact the Control Panel mount tool will only allow hda1 to be mounted. If I run "fdisk -l" from a root shell Hda is definitely the hard drive and sda1 the flash drive.

In case it was a hardware issue with the particular USB drive - seems unlikely given that another distro can access - I also tried booting from CD with a different usb flash drive , which is formatted as FAT32 , plugged in and could not mount it either using the control panel mount tool.

^thehatsrule^:
What's your output of fdisk -l for the sda section?

I guess you get similar errors with your other drive?

This might help: http://ubuntuforums.org/showthread.php?t=359

padr:
Thanks for your suggestion. I looked through the link you provided.

I tried deleting the partition and creating just one FAT32 partition using gparted. I then also ( belt and braces !) reformatted the usb stick again in Windows as FAT32. Still no luck however getting TinyCore to mount the USB drive.

I came across another question in LinuxQuestions -   www.linuxquestions.org/questions/printthread.php?t=318392 which seemed relevant to my problem. This suggested making sure a volume label was attached - so I did this and it resolved a quirk in the way the drive was behaving in Windows but still no luck with TinyCore.

The mount command gives a "can't read superblock" message. The Fdisk -l output is to the effect the "Partition 1 has different physical / logical beginnings (non-Linux?)"

Finally ( it is a question of persistence after all !! ) tried a different brand ( two in fact ) and success !! TinyCore TCE's now persist on the non-Transcend sticks across sessions   ;D

So it looks like there is some issue with detection with Transcend USB sticks/TinyCore ? The Transcend sticks which I cannot mount in TinyCore work OK in Puppy linux, DSL and under Windows .

However I now have tce's carrying thorugh from one session to another so all is well for now at least - maybe the above will help to track down where the issue lies.

By the way - I did need to use the waitusb=5 bootcode

Navigation

[0] Message Index

[#] Next page