linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: Drive failure and ASUS
Date: Mon, 24 Nov 2008 14:25:22 +0900	[thread overview]
Message-ID: <492A3AC2.5020801@kernel.org> (raw)
In-Reply-To: <4928B36B.5030005@shaw.ca>

Robert Hancock wrote:
> Gene Heskett wrote:
>> Greetings;
>>
>> The only way I can get this box to boot is to disconnect the data
>> cable on a drive with 121 badblocks as somehow ASUS and JMicron-pata
>> all seem to think its /dev/sda when hooked up, and it is no longer
>> bootable.  I'm presently booted from a sata drive on that interface,
>> which this ASUS board has about 8 of.
> 
> The bad disk is PATA?
> 
>>
>> So I've booted with the data cable off, and hooked it up once booted. 
>> Unforch there seems to be no discovery of its presence.
>>
>> No /dev/sdd stuff was created when I plugged the data cable into the
>> drive.
>>
>> The install is the August 2008 F8 respin and is uptodate.
>>
>> How can I make the system aware that it is now there?  It has about 40
>> Gb of data I'd like to recover if I can.

echo "- - -" > /sys/class/scsi_host/host*/scan

> Hotplug isn't supported with PATA, so you shouldn't really try that.
> Fedora installs usually use labels for the disk partitions, so it
> shouldn't matter what device node the disk gets detected as?

It isn't but if you're willing to accept the risk of frying the
controller and/or the drive, it works.  I sometimes do that which
sometimes makes the whole machine shut off instantly.  :-)

-- 
tejun

      reply	other threads:[~2008-11-24  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 14:01 Drive failure and ASUS Gene Heskett
2008-11-23  1:35 ` Robert Hancock
2008-11-24  5:25   ` Tejun Heo [this message]

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=492A3AC2.5020801@kernel.org \
    --to=tj@kernel.org \
    --cc=hancockr@shaw.ca \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).