public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manohar Pradhan <mpml@isp.primuseurope.com>
To: "Jakob Østergaard" <jakob@unthought.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re[2]: Urgent SCSI I/O Error
Date: Mon, 25 Feb 2002 20:36:35 +0000	[thread overview]
Message-ID: <197784956397.20020225203635@isp.primuseurope.com> (raw)
In-Reply-To: <20020225210239.H24109@unthought.net>
In-Reply-To: <194779754037.20020225190953@isp.primuseurope.com> <20020225210239.H24109@unthought.net>

Hello Jakob,

Thanks. I got another HDD read. but How can I install it, format and
make partition as earlier ( I have partition info though ..) and mount
it? Do I need to compile the Kernel or I can attach new HDD, and start
to create file systems inside.

Thanks for your enlightments.

Regards
Manohar




Monday, February 25, 2002, 8:02:39 PM, you wrote:

JØ> On Mon, Feb 25, 2002 at 07:09:53PM +0000, Manohar Pradhan wrote:
>> Hi,
>> 
>> This question might have been raised before but I am stucked in
>> between wierd/helpless situation and wondering if someone can help me
>> out.
>> 
>> I have Red Hat Linux 6.2 (2.2.14-5.0smp) running in my HP Netserver
>> box. I have 2 9.1 GB HDD. The server has been up for few months and
>> have not had seen any problem. But today all of sudden it gave
>> panicking message saying following:
>> 
JØ> ...
>> Feb 25 18:48:12 nsdb1 kernel: [valid=0] Info fld=0x0, Current sd08:06: sense key Not Ready
>> Feb 25 18:48:12 nsdb1 kernel: scsidisk I/O error: dev 08:06, sector 0
>> Feb 25 18:48:12 nsdb1 kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 28000002
>> Feb 25 18:48:12 nsdb1 kernel: [valid=0] Info fld=0x0, Current sd08:07: sense key Not Ready
>> Feb 25 18:48:12 nsdb1 kernel: scsidisk I/O error: dev 08:07, sector 0

JØ> Your disk died.  Physically.

JØ> ...
>> I can access files in all the other partitions but cannot access
>> files/directories in partition /www. I can see files in the
>> directories listing using 'ls' however accessing any file gives
>> Input/Output error saying:
>> 
>> cat check1.htm: Input/output error
>> 

JØ> Yep - can't read from bad blocks.

>> Can anyone help/suggest me what should I do to make it work? I am
>> wondering if I reboot the system, I may fall into problem on booting
>> itself. Is there any thing I need to do to make this partition work?

JØ> Replace the harddrive, restore from backup.

JØ> You will only have a problem booting, if the boot sector / kernel 
JØ> resides on that drive - and if that part of the drive is damaged
JØ> too.   It seems like that's not the case, but it would be wise
JØ> to run an "mkbootdisk" now, just in case.




-- 
Best regards,
 Manohar                            mailto:mpml@isp.primuseurope.com


  reply	other threads:[~2002-02-25 20:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 19:09 Urgent SCSI I/O Error Manohar Pradhan
2002-02-25 20:02 ` Jakob Østergaard
2002-02-25 20:36   ` Manohar Pradhan [this message]
2002-02-25 20:42     ` Re[2]: " Jakob Østergaard
2002-02-25 20:44   ` Manohar Pradhan
2002-02-25 21:02     ` Jakob Østergaard
2002-02-25 21:18     ` Richard B. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=197784956397.20020225203635@isp.primuseurope.com \
    --to=mpml@isp.primuseurope.com \
    --cc=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox