• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Knoppix prob

Ibanez3434

Bad Trader
Joined
Jun 15, 2004
Messages
669
ok, so I ran "sudo knoppix-installer"

made a 512m linux swap, and the rest (about 3gb) for the linux part. ok, So it booted once fine, but after that it wont boot anymore, I get a bunch of HD errors, such as "read only device" stuff like that. I tried ext3 and rieserfs, installed about 3 times. Same thing every single time. Any ideas?

 
Sounds like an issue with the bootloader. Might want to create a bootfloppy this time around just in case. It's simple to edit/reinstall the bootloader once you're up and running. You may want to try a different install style option. I almost always use the debian-style choice.
 
hmm, well I tried reinstalling. while I was partitioning it, it said in the console,
"warning: filesystem has errors! You should run e2fsck.
No implementation: This ext2 filesystem has a rather strange layout! Parted can't resize this (yet)."

So I tried the logical thing (run e2fsck). I got this error,

"couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to correct /dev/hde

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and tou might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>"

I have no earthly idea wtf that means... Im a huge Linux noob. so uh, now what?

 
NVM, obviously was my Highpoint controller. I put it in the primary controller, and it worked fine. Solved my own prob again. lol.
 
Back
Top