[Sussex] Re: Suse 8.1 disk error

[Paul Bruce]

Thanks for the advice Steve, but it's a CD-ROM It doesn't have heads to crash 
does it?


On Sunday 27 April 2003 11:00, sussex-request at mailman.lug.org.uk wrote:
> Send Sussex mailing list submissions to
> 	sussex at mailman.lug.org.uk
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mailman.lug.org.uk/mailman/listinfo/sussex
> or, via email, send a message with subject or body 'help' to
> 	sussex-request at mailman.lug.org.uk
>
> You can reach the person managing the list at
> 	sussex-admin at mailman.lug.org.uk
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sussex digest..."
>
>
> Today's Topics:
>
>    1. Re: Suse 8.1 technical question? (Steve Dobson)
>    2. Re: thanks and questions (john davis)
>
> --__--__--
>
> Message: 1
> Date: Sat, 26 Apr 2003 23:42:11 +0100
> To: sussex at mailman.lug.org.uk
> Subject: Re: [Sussex] Suse 8.1 technical question?
> From: Steve Dobson <steve.dobson at krasnegar.demon.co.uk>
> Reply-To: sussex at mailman.lug.org.uk
>
> On Sat, Apr 26, 2003 at 11:21:59PM +0000, Paul Bruce wrote:
> > When I boot my Suse 8.1 machine I get the following error
> >
> > I/O error, dev 16:40 (hdd), sector 78
> > blah
> > blah
> > blah
> >
> > (interpret "blah" as me being too lazy to type out the same thing over
> > and over again)
> >
> > hdd is one of my IDE CD  ROMs (that operates under SCSI emulation)
> > A search of the SUSE database gave no obvious answer.  Do any of you
> > super geeks know what the error refers to? :-)
>
> When the disk drive interrupts to say that it has completed a command
> (to read date to/write data from the disk) it indicates weather the
> command completed or not.  If the command did not complete then it
> reports this type of error.
>
> Any I/O error with the disk is something to worry about.  The more sectors
> that are reporting problems the more damage your disk has.  My guess is
> at you've had a head crash.  Get any important data off that disk now.
> It's time to dip your hand in your pocket and get a new disk.
>
> You might be able to partition the disk so that the damaged sectors are
> not used.  I did this once, many moons ago, with a SCSI disk that some
> chap brought into the shop I was in at the time.  I bought it off him for
> a fiver, and five plus years ago any SCSI disk for a fiver was a steal.
>
> But when a disk starts to go wrong I think it is time to stop storing
> important data on it.
>
> Steve
>
>
>
> --__--__--
>
> Message: 2
> From: john davis <big-john at dsl.pipex.com>
> To: sussex at mailman.lug.org.uk
> Subject: Re: [Sussex] thanks and questions
> Date: Sun, 27 Apr 2003 11:58:32 +0100
> Reply-To: sussex at mailman.lug.org.uk
>
> On Saturday 26 Apr 2003 5:39 pm, John Crowhurst wrote:
> <snip>
>
> > What you could try is the command, free:
> >
> > #free
> >              total       used       free     shared    buffers     cach=
>
> ed
>
> > Mem:        190636     186216       4420          0      61324      124=
>
> 20
>
> > -/+ buffers/cache:     112472      78164
> > Swap:       128516        768     127748
>
> </snip>
>
> And that would explain why I got this
>
> [root at localhost john]# free
>              total       used       free     shared    buffers     cached
> Mem:        775592     153184     622408          0       4596      78756
> -/+ buffers/cache:      69832     705760
> Swap:            0          0          0
> [root at localhost john]
>
>
> more specifically the "Swap:   0   0   0" bit!
>
> Many thanks one and all, at least I now have a vague idea what to do.
>
> regards
>
> John d:-?
> --=20
> At the end of the day, where ever you go, there you are :-?
>
>
>
> --__--__--
>
> _______________________________________________
> Sussex mailing list
> Sussex at mailman.lug.org.uk
> http://mailman.lug.org.uk/mailman/listinfo/sussex
>
>
> End of Sussex Digest