[ale] slackware 10.1 crash

[James P. Kinney III]

On Fri, 2005-05-06 at 15:45 +0000, zeb morgan wrote:
> I have a problem.
> 
> Running Slack 10.1 and it won't boot.  LILO comes up o.k.  When booting,
>       when the system gets to "e2fsck" it hangs.  The error message is
> "bad magic number in superblock."  "The superblock could not be read..."

This is not an issue with slackware. It's a hardware issue. The super
block is damaged or worn out and can't be read. When that is gone, the
ability to boot from that drive is also gone. It is best to replace the
drive and migrate over any data.
> 
> Yet, when I boot from a Knoppix CD, I can read everything on the system,
> so apparently the data is all o.k.

The Knoppix boot up is not accessing the superblock on the drive so it
works just fine. The rest of the drive data has nothing to do with the
superblock so it shows up OK as well.
> 
> I don't think I did anything stupid.  I was installing and configuring
> Slack and never got the configuration complete.
> 
> I have not been able to find any method of restoring the superblock. I
> can "fix" the system by reinstalling Slack. There is nothing critical on
> this system.  So the only real loss is my time
> 
> It is an old machine that I use for experimental purposes.  I have had
> the identical problem recurrently on another old system.  The two
> systems are different--different CPUs, different system boards.

The key here is "old systems". Hard drives have a finite lifespan. Yours
have been exceeded :)  Time for a trip to the parts store. WooHoo!!
> 
> I can run Slack 9.1 on either system without any problems at all.
> 
> Now....I am running Slack 10.1 on a third (old) system without any
> problems (so far) for several weeks.
> 
> To identify my systems:  #7 is the one that has no problems.  #10 is the
>   one that is currently crashed.  #11 is the one that has given me
> repeated problems (and the system I am using as I "speak")--now running
> Slack 9.1 and using Thunderbird for e-mail.
> 
> Does anyone have an idea as to the cause of this problem?
> 
> Does anyone have any suggestions as to how this problem can be repaired?
> 
> I will be happy to provide details as to the systems, if that is needed.
>   I have omitted them here in the interest of time.
> 
> Thanks for reading this.  More thanks for any replies.
> 
> Zeb Morgan
> 
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO & Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part