Re: Drive failure and ASUS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux