[Novalug] IDE Drive problem, need advice

[Mike Shade]

Looks good, so far.  Open a terminal and list the partitions.

fdisk -l /dev/sdc

You should see the partition table of the drive listed.  Make a directory
to mount the main partition in...

mkdir /mnt/sdc

And attempt to mount it:

mount -t vfat /dev/sdc1 /mnt/sdc

That's assuming the partition is FAT32.  If NTFS, specify that -- you
could also try -t auto.

Browse to /mnt/sdc and get that stuff off the disk!

-- Shade


On Wed, March 21, 2007 9:52 am, Jay Hart wrote:
> I'm trying this now, here is what I see via dmesg:
>
> SCSI device sdc: 8544940 512-byte hdwr sectors (4375 MB)
> sdc: test WP failed, assume Write Enabled
> sdc: assuming drive cache: write through
> SCSI device sdc: 8544940 512-byte hdwr sectors (4375 MB)
> sdc: test WP failed, assume Write Enabled
> sdc: assuming drive cache: write through
>  sdc:<6>NET: Registered protocol family 10
> Disabled Privacy Extensions on device c0380760(lo)
>
> usb 3-2.2: reset high speed USB device using address 3
> usb 3-2.2: reset high speed USB device using address 3
> usb 3-2.2: reset high speed USB device using address 3
> suse:/var/log #
>
> I'm pretty sure that the drive in question is sdc, since I don't have any
> other drives that would
> use this designation.
>
> No meesages have been logged in /var/log/messages
>
> When I open My Drives (via Konqueror), I can't get any of the drives to
> display.
>
> Suse 9.2 is what I am using.
>
> Jay
>
>> On Wed March 21 2007 9:06 am, Ben Creitz wrote:
>>> On 3/20/07, Jay Hart <jhart at kevla.org> wrote:
>>> > > What happens if you put drive A with controller A back into the
>>> > > USB enclosure and hook that up to a linux PC?  See if you're able
>>> > > to mount the drive then.
>>> >
>>> > Why do you think this would work if I can't get a PC to boot when
>>> > this drive is connected?
>>>
>>> Why believe that it wouldn't work?  You only say that you can't get a
>>> PC to boot when this drive is attached.  You never say whether or not
>>> you can read the filesystem (from Windows or Linux) if you hook it up
>>> after the system has booted.  So far, your only problem sounds like
>>> "PC does not boot if this drive is plugged in."  That does not
>>> necessarily indicate "I can't read what is on the disk."
>>
>> I had something similar happen recently. Putting the drive in a USB
>> enclosure and mounting it on a Linux box after boot-up enabled me to
>> recover almost all the files.
>>
>> Dan Arico
>>
>> --
>> One OS to rule them all, One OS to find them,
>> One OS to bring them all, and in the Darkness bind them,
>> In the land of Redmond, where the Sales Reps lie.
>> _______________________________________________
>> Novalug mailing list
>> Novalug at calypso.tux.org
>> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>>
>
>
> _______________________________________________
> Novalug mailing list
> Novalug at calypso.tux.org
> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>