New Boot Drive 16 GB -> 4 GB

[Rich]

Hi MTCAT
Assuming you 4 Gig USB is sdc, run this command:

Code: [Select]

blkid /dev/sdc1And see if the UUID listed matches what's in extlinux.cfg.

[MTCAT]

Hi Rich,

Thanks for the help, fired up the little VortexDX3 with a 16 GB pen drive, inserted the 4GB Cactus drive which got attached as sdc1. Seems like the UUID in extlinux.conf and that reported by "blkid" are consistent.

The output of

Code: [Select]

blkid /dev/sdc1

was;

Code: [Select]

/dev/sdc1: UUID="c3981945-a8ad-48d3-9867-41b071e3a046" TYPE="ext4"

The extlinux.conf file on sdc1 contains;

Code: [Select]

UI vesamenu.c32
MENU TITLE TinyCore Bootloader
TIMEOUT 100

DEFAULT realtime

LABEL tinycore
KERNEL /boot/bzImage
APPEND initrd=/boot/tinycore.gz norestore noswap nodhcp quiet waitusb=10:UUID="c3981945-a8ad-48d3-9867-41b071e3a046" tce=UUID="c3981945-a8ad-48d3-9867-41b071e3a046" home=UUID="c3981945-a8ad-48d3-9867-41b071e3a046" opt=UUID="c3981945-a8ad-48d3-9867-41b071e3a046"

LABEL realtime
KERNEL /boot/bzImagert
APPEND initrd=/boot/tinycorert.gz norestore noswap nodhcp quiet libata.force=80c waitusb=10:UUID="c3981945-a8ad-48d3-9867-41b071e3a046" tce=UUID="c3981945-a8ad-48d3-9867-41b071e3a046" home=UUID="c3981945-a8ad-48d3-9867-41b071e3a046" opt=UUID="c3981945-a8ad-48d3-9867-41b071e3a046"

Thanks,

David

[MTCAT]

Hi Rich,

Not sure how the 4GB pen drive would have ext4 with 64 bit compression when the source drive apparently does not (since it does boot), but maybe this could be something to try?, see image attached, especially if I could do so w/o having to re-do the dd step?

Thanks,

David

[Rich]

Hi MTCAT

Not sure how the 4GB pen drive would have ext4 with 64 bit compression when the source drive apparently does not ...

It doesn't. The  dd  command duplicates what and where it finds on device A on device B.