Re: booting with persistent image
On Jul 20, 2006, at 3:00 AM, Klaus Knopper wrote:
On Wed, Jul 19, 2006 at 01:40:55PM -0400, Keith Hodges wrote:
In 5.0.1 I created a persistent home image and booted with
home=/dev/hdb2 as instructed and the image was ignored.
You should not have to give home=... as boot option. Knoppix will scan
all partitions read-only for a knoppix.img.
Are you booting from CD or from the hard drive (e.g. Poor Man's
Install)?
I saw in the known bugs list that this was rumoured not to be
working if /dev/hdb2 is an ext2fs.
Really? Where?
For 4.0.2:
http://lists.debian.org/debian-knoppix/2005/12/msg00028.html
The code is unchanged in 5.0.1.
So I made /dev/hdb2 to be a FAT32 in order to work around this. I
still find it ignored. I tried ext3fs too and that did not work
either.
I'm using this right now with 5.0.1, /dev/sda1 being vfat (FAT16,
but FAT32 works as well).
Yup, vfat should work just fine. ext3 should also, except if you are
booting from the same partitions. That is, an interesting issue
arises when a PMI and a PDI are on the same ext2 or ext3 filesystem
-- the PDI will not mount. I don't remember the details. But if
anyone's interested I'll look into it further.
If you want to do more troubleshooting, boot with "knoppix -b" and
run this code ...
rebuildfstab -r
ls -d /mnt/hd* | xargs -n 1 mount
( set -x
cat /etc/knoppix-version
cat /etc/fstab
fdisk -l
cat /proc/cmdline
mount
) &> output.txt
... and please post the contents of output.txt.
Have you tried booting with "knoppix 2", then mount /media/hdb2,
and knoppix-image /media/hda2/knoppix.img ?
Alternatively, you can boot with "knoppix -b" and when you enter
"emergency mode", edit the /etc/init.d/knoppix-autoconfig file
manually, changing one of the ext3's to ext2. For example:
sed 's/ext3/ext2/' /etc/init.d/knoppix-autoconfig > /tmp/ka
mv /tmp/ka /etc/init.d/knoppix-autoconfig
Let us know what you do and how it works for you.
Regards,
- Robert
http://www.cwelug.org/downloads
Help others get OpenSource software. Distribute FLOSS
for Windows, Linux, *BSD, and MacOS X with BitTorrent
Reply to: