Error after Hdd install

[Durand Hicks]

The errors you're reporting is saying that the filesystem of your linux installation wasn't compiled into the kernel. What filesystem did you install linux to? If it isn't ext2, ext3 or reiserfs, then that would be your problem.

[markb]

The errors you're reporting is saying that the filesystem of your linux installation wasn't compiled into the kernel. What filesystem did you install linux to? If it isn't ext2, ext3 or reiserfs, then that would be your problem.

Durand, recall that the knoppix-installer installation script we are running here creates the file system itself (ext3 I am pretty sure) before it writes the installation. Then we get the devfs error and kernel panic on our first reboot after install. I think the installer script uses parted to do partitioning + formatting, hence my theory there is a bug in parted/libparted.

[Durand Hicks]

Not necessarily, you have to choose the filesystem before installing. For all we know, the op may have already partitioned his drive prior to running knoppix-installer. What I wanted to know is what filesystem is he installing to? Matter of fact, I partitioned my drive using qtparted prior to installing knoppix to my partitions, so I never really ran into that problem. The knoppix-installer will reformat the partitions it installs to anyway, so I asked the question because he may have done it differently.

[twistedalpha]

-at Konsole:
sudo qtparted
-i create an ext3 filesystem .. then a linux-swap
-then
sudo knoppix-installer
-then the installation follows
-after the installation end ofcourse i rebooted
-then when it booted it gives me the error .. again

[Durand Hicks]

When you ran qtparted, were the partitions unmounted before you made any modifications? Second, did you commit (write) the new partition table before exiting qtparted? If this step was omitted, then you'll need to rerun qtparted, make your modifications, and finally commit the changes. Then you can run sudo knoppix-installer.

HTH,

Durand

[twistedalpha]

1st question .. i can't seem to understand
2nd question .. yes, i commit before exiting

[francisgirard]

Hi All

This is my first post on this forum and I admit I am a newbie when it comes to Linux...

I am also experiencing a similar problem after installing to Hdd using the Knoppix-installer which comes with the KNOPPIX_V3.7-2004-12-08-EN.iso (MD5 checksum passed)

I used the exact same procedure that I used to install V3.4 that came with the Knoppix Hacks book. The 3.4 install worked fine, but since the HW detection for 3.4 could not detect my USB Scanner, I decided to try with 3.7.

When running the 3.7 LiveCD, it saw all my HW properly so I tried to HDD install again.
So I wiped the partition clean (by removing, reboot, recreating, reboot) using QTParted as root. (Swap of 1 gb as linux swap, and a 6 Gb ext2 part, which gets formated in ext3 by the installer script after)

I am doing the single boot install (no other OS installed) and using the MBR as the install option.

Now the symptoms are similar... I did notice also that during the install there was some errors reported as to the drive being read-only. I never had this type of error reported when I previously installed 3.4 but only had full confirm that it did not complete when I tried to boot to hdd.

Mine seems to go a bit further in the boot process compared with the others. I always boot with the 2.6 kernel, and it only stops when trying to load KDE. I cannot recall exactly what the message says but can certainly type it down once I am back home...

Someone pointed out earlier that it might be related to a lib from Unstable (since similar symptoms are reported on other install than Knoppix)... If this means there are no workaround for now, and considering that this is beyong Knoppix's original mandate (it works perfectly fine as a LiveCD), can any of you suggest to me a way to find the driver that 3.7 uses for my USB scanner (a way for me to look it up by myself I mean)? This way I can re-install 3.4, patch that driver in, and get the rest of the packages updates thru apt-get direct from the debian sources...

Thanks again for all your help,

Francis

[markb]

Hi All
I am also experiencing a similar problem after installing to Hdd using the Knoppix-installer which comes with the KNOPPIX_V3.7-2004-12-08-EN.iso (MD5 checksum passed)

Francis, I think you are in the wrong thread. You seem to be describing a different issue. Unless you are seeing the specific errors described by twistedalpha at the opening of this thread then you are not experiencing the problem we are discussing here. The errors are:

umount : devfs : not mounted
mount : fs type devfs not supported by kernel
umount : devfs : not mounted
pivot_root : No such file or directory
/sbin/init : 426 : cannot open dev/console : no such file
Kernel panic : Attempted to kill init!

Do you see these "devfs" errors and then the kernel panic?

[francisgirard]

Hi Markb,

No I do not have the exact same error messages which you (in another thread) and twistedalpha are mentioning, and you are right that it might have been better to open a complete new thread for it in this case...

The only reason I brought it up in the same thread is that I thought it might help since it is most likely related. Remember that the way I am installing is also slightly different (from what I recall reading both you and Twistedalpha installed it as dual-boot, not single boot) so this might account why it does not fail exactly at the same point (with the devfs errors) but just right after (once it starts loading) so if someone was inclined to test those 2 scenario and try to replicate the error to debug, they could better pinpoint at the fault.

But, as I already admitted, Linux is a brand new world from me. But the last years I was doing tech support on IBM HW (under MS windows) showed me that having a slight different perspective on a similar problem might pinpoint to the right solution.

Désolé...

Francis

[twistedalpha]

No I do not have the exact same error messages which you (in another thread) and twistedalpha are mentioning, and you are right that it might have been better to open a complete new thread for it in this case...

err .. if u can please help me