KNOPPIX 6.7.1 on USB with very large persistent data image.

....strange behavior.....using my new USB HDD 500GB instead of the broken internal 60GB SDD.
For Knoppix Live Usb I create:
- 1° partition FAT32 about 50GB with Syslinux Boot folder
- 2° partition NTFS about 300GB with my 7GB presisten image and 1GB extra personal data and future VirtualBox HDD image
- 3° partirion EXT2 about 150GB for temporary store to try to use recombine script (see the Werner P. Schulz recombine script at http://www.wp-schulz.de/knoppix/recombine.html)
Usually this 3° partition is un-allocated and all work fine.
But after activating the 3° Ext2 partition using GParted, exit and reboot....the system break in kernel panic with an error about the mount of mnt-system...
I think the problem is the Init script in minirt.gz
It seems that the EXT2 partition is the favorite to be mounted as mnt-system/knoppix instead the NTFS (where knoppix-data.img is real located).

Any suggestion ? There is a bug ?
Thanks
Bye

How big are your files for Fat32?

Quote:

---

Originally Posted by Blacksimon

....strange behavior.....using my new USB HDD 500GB instead of the broken internal 60GB SDD.
For Knoppix Live Usb I create:
- 1° partition FAT32 about 50GB with Syslinux Boot folder
- 2° partition NTFS about 300GB with my 7GB presisten image and 1GB extra personal data and future VirtualBox HDD image
- 3° partirion EXT2 about 150GB for temporary store to try to use recombine script (see the Werner P. Schulz recombine script at http://www.wp-schulz.de/knoppix/recombine.html)
Usually this 3° partition is un-allocated and all work fine.
But after activating the 3° Ext2 partition using GParted, exit and reboot....the system break in kernel panic with an error about the mount of mnt-system...
I think the problem is the Init script in minirt.gz
It seems that the EXT2 partition is the favorite to be mounted as mnt-system/knoppix instead the NTFS (where knoppix-data.img is real located).

Any suggestion ? There is a bug ?

---

Sure there is either a bug or some file or hardware error. But you give too little information to tell what it is. I like to keep things as simple as possible, which means that I keep KNOPPIX and the persistent image at the same place (the default setup), and I use legacy grub for booting. In your case, I would have created a smaller ext2 partition in addition to the other, installed grub to that, made it active, and then created different menu items for KNOPPIX. After copying the contents of the syslinux boot directory to a subdirectory knx671 on the boot partition, I would have forgotten about it.

Here are my grub entries for Knoppix 6.7.0, incidentally I have this version of KNOPPIX on the boot partiton - that's just because all the other partitions were in use for other versions, the norm is that the boot partition is not mounted during normal use.

Code:

---

title Knoppix 6.7.0 all arch (sda5)
      kernel (hd0,4)/boot/knx670/linux ramdisk_size=100000 lang=no keyboard=no  fromhd=/dev/sda5 nosound vt.default_utf8=0 apm=power-off initrd=minirt.gz nomce libata.force=noncq loglevel=1 tz=localtime
      initrd (hd0,4)/boot/knx670/minirt.gz

title Knoppix 6.7.0 64 bits kernel (sda5)
      kernel (hd0,4)/boot/knx670/linux64 ramdisk_size=100000 lang=no keyboard=no  fromhd=/dev/sda5 nosound vt.default_utf8=0 apm=power-off initrd=minirt.gz nomce libata.force=noncq loglevel=1 tz=localtime
      initrd (hd0,4)/boot/knx670/minirt.gz

---

Quote:

---

- 3° partirion EXT2 about 150GB for temporary store to try to use recombine script (see the Werner P. Schulz recombine script

---

Did you use my script or not? If so, tell us step by step what you've done. In case of error, what messages? Otherwise what else is on partition#3?

Greetings Werner * http://www.wp-schulz.de/knoppix/summary.html
Own Rescue-CD (Knoppix V6.7.1 remaster)

I use the recombine script and works well. Thanks Werner P. Schulz !!

The strange behavior happen before using the script, when I created tree partitions and normally boot the first time.
With 3° EXT2 partition active system halted in kernel panic with an error about the impossibility of mounting Knopppix in mnt-system
With 3° partition removed (un-allocated) all works fine


I'll try again

partially solved using at boot the cheat KNOPPIX FROMHD=/dev/sda2 instead the auto search

I'll try to change the 3° partition in NTFS or other and try again
I want understand

Why should NTFS vs ext2 make any difference here?
And when you make a partition active, you tell the system to boot from there, right?
I think that whenever we experiment with alternative setups from the default, leaving it to then Knoppix init to find and mount a Knoppix image may be relatively bad practice. Always specify fromhd= in such situations. (For me, init may find 5-7 Knoppixes, small probability it will auto-pick the correct one :))

probably nothing.....
sure best to use cheats fromhd=

experience leads to knowledge :-)))