Played with hdparm, now my server won't boot.

[happybunny]

AAAAAA!!

After monkeying with hdparm, my server crashed...

Now on boot up i get kernel panics on boot.

This is what i get trying to mount on knoppix:
# mount -t ext3 /dev/hda1 /savem/

mount: wrong fs type, bad option, bad superblock on /dev/hda1,
or too many mounted file systems


which isn't true...it is ext3

Also:
# tune2fs -j /dev/hda1
or
#e2fsck -b 32768 /dev/hda1

results in:

tune2fs 1.35 (28-Feb-2004)
tune2fs: Bad magic number in super-block while trying to open /dev/hda1
Couldn't find valid filesystem superblock.
or
e2fsck 1.35 (28-Feb-2004)
e2fsck: Bad magic number in super-block while trying to open /dev/hda1

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 you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>


Am i out of luck? I hope not....160gig harddrive with some good stuff on it.

It was Slackware 10 with 2.4 kernel.

2 partitions, / and swap
it boots to lilo, starts to boot, but then kernel panics....weird that it gets that far if the drive is bad or corrupt.

Any ideas?

[Dark Ninja]

I would attempt to boot off Knoppix and tune your settings back down (reverse your changes). You can mount your Slack drive in Knoppix.

Good luck.

[happybunny]

if i was just doing them from the command line in slackware, they are not perminant, correct? Those "bad" settings should not have survived a reboot?

[rocketpcguy]

then hdparm probably f*cked up your hdd.

[blobaugh]

hdparm is an extremely powerful program. if you don't know what you are doing with it then you should probably not mess with it. goto G4L (http://google.com/linux) and look for some good tutorial on hdparm. i don't know if you can undo the damage or not without loosing all your information on the drive