[NTLUG:Discuss] Lost drive

[agoats at compuserve.com]

I've had some weird stuff like this happen to me. What worked was to do 
a file system check on the entire file system starting with /  .  It 
seemed that something got screwed up on the main system that caused the 
OS to not be able to see the drive.  Assuming an ext2/ext3 system:

e2fsck -v -y -D -f  /dev/hda1  (assuming / is on hda1)

The flags say verbose, answer "yes" to everything, optimize the 
Directory and FORCE it to do the filesystem check, even if it doesn't 
think it's needed. If you're using a different file system, use a 
similar command set.

You may have to use a bootable CD image to do the file system check at 
this high a level ( "/"). 

Good luck,

Alvin

 

fdisk might miss the drive and it looks like it shows up

Michael Barnes wrote:
> Changed slots, no good.
>
> On Tue, Oct 25, 2011 at 2:44 PM, Jay Urish <jay at unixwolf.net> wrote:
>   
>> bad slot on the mobo?
>>
>>
>> On 10/25/2011 2:37 PM, Michael Barnes wrote:
>>     
>>> I've got an old ftp server running SLES 9.  I needed more drive space,
>>> so I added a SIIG SATA PCI card and a 500G Barracuda drive.  It's been
>>> perking along happy as a clam until this morning when suddenly it
>>> doesn't see the drive.  I put the card and the drive in another
>>> machine and they work fine.  I put a new card and a new drive in and
>>> it still doesn't recognize them.  When it boots up, the POST splashes
>>> the card and the drive.  fdisk -l /dev/sdb returns nothing.
>>>
>>> Any ideas on other things to check?  At first, it wouldn't even boot
>>> until I commented out the drive mounting in fstsab.
>>>
>>> Thanks,
>>> Michael
>>>
>>> _______________________________________________
>>> http://www.ntlug.org/mailman/listinfo/discuss
>>>       
>> _______________________________________________
>> http://www.ntlug.org/mailman/listinfo/discuss
>>
>>     
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>
>