Re: Unrecognized Hard Drive
On Sun, Jan 04, 2009 at 02:14:16PM +1030, Tim wrote: > > Tim: > >> /me wonders whether warming them up, first, would have helped? > > Mikkel L. Ellertson: > > It might have - stick it in an oven or something. On the other hand, > > it might have cause other problems. What I think was happening is > > that the bearing lubrication had gotten into places it should not > > have, and then prevented the drive from starting to spin up. The > > jolt freed thing up enough to get the drive spinning. It also freed > > the head to move as well. > > I was thinking of metal contraction as it cools down seizing the moving > parts into position (remembering my days back in school of being told > not to leave the vices tightened up overnight). > > Of course warming them up would have to be to a sensible temperature. > Warming them up to normal operating temperatures, not roasting > them. ;-) > > I get odd looks when I tap the back of a screwdriver with another one, > with the first one's point in the slot, to loosen up stuck bolts. But > the principle's the same, you're trying to free up a moving part that's > jammed, but with the minimal amount of force that's required. > Hmmm this discussion sounds like the now solved "stiction" problem seen by a lot of vendors ten years+ ago when a new generation of heads was introduced. The issue was lubricant for the drive bearings and the new generation of very flat very low flying heads did not play well together.One vendor's explanation was that the lubricant migrated to the landing pad area and a year later when the drive shut down the heads would seek to the landing zone and "stick". Folks that have ever worked with optical flats, microscope slide coverslips knows how solidly "flats" can stick together. For the stiction problem the solution was to cycle the drive in software/ firmware so it would spin down for a moment a couple times a month and do the equivalent of a "touch and go" effectivly cleaning the heads and landing pad zone. Later changes to the lubricant, berrings and landing pad zone surface eliminated the need for the touch and go solution. For a stuck drive a field solution was to give the drive a "rap" in a corner giving additional "torque" at start up. The power on cycle of the drive gave the field tech. about five seconds to apply the "rap" before the drives self protection logic shut it down.This worked for most but not all drives. If the drive spins up but does not come on line then this is not the issue. -- T o m M i t c h e l l Found me a new hat, now what? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Tim: >> /me wonders whether warming them up, first, would have helped? Mikkel L. Ellertson: > It might have - stick it in an oven or something. On the other hand, > it might have cause other problems. What I think was happening is > that the bearing lubrication had gotten into places it should not > have, and then prevented the drive from starting to spin up. The > jolt freed thing up enough to get the drive spinning. It also freed > the head to move as well. I was thinking of metal contraction as it cools down seizing the moving parts into position (remembering my days back in school of being told not to leave the vices tightened up overnight). Of course warming them up would have to be to a sensible temperature. Warming them up to normal operating temperatures, not roasting them. ;-) I get odd looks when I tap the back of a screwdriver with another one, with the first one's point in the slot, to loosen up stuck bolts. But the principle's the same, you're trying to free up a moving part that's jammed, but with the minimal amount of force that's required. -- [...@localhost ~]$ uname -r 2.6.27.9-73.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Tim wrote: > On Fri, 2009-01-02 at 13:24 -0600, Mikkel L. Ellertson wrote: >> I can remember dropping a SCSI drive or two 4" to 6" onto the desk >> to free it up so it would spin up again. (Drop so it lands flat on >> its bottom, not sides or ends.) This was often necessary on drives >> that had run non-stop for years, and were shut down long enough to >> cool off. > > /me wonders whether warming them up, first, would have helped? > It might have - stick it in an oven or something. On the other hand, it might have cause other problems. What I think was happening is that the bearing lubrication had gotten into places it should not have, and then prevented the drive from starting to spin up. The jolt freed thing up enough to get the drive spinning. It also freed the head to move as well. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
On Fri, 2009-01-02 at 13:24 -0600, Mikkel L. Ellertson wrote: > I can remember dropping a SCSI drive or two 4" to 6" onto the desk > to free it up so it would spin up again. (Drop so it lands flat on > its bottom, not sides or ends.) This was often necessary on drives > that had run non-stop for years, and were shut down long enough to > cool off. /me wonders whether warming them up, first, would have helped? -- [...@localhost ~]$ uname -r 2.6.27.9-73.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Bill Davidsen wrote: > jdow wrote: > >> It sounds like the drive cannot get its head mounted and simply hangs >> somehow. It's not useful for backups. If I had data on it there are some >> "hacks" I might try, sharply twisting the drive on the axis of rotation >> as power is applied, for example. Sometimes that will get the disk to >> spin up if that's the problem. I've managed to rescue data that way a >> couple times. >> > I like "drive tapping" myself for spinup. Start tapping the drive with > the handle of a screwdriver (side impact, not on top) and apply power. I > have used that with success back to ESDI days, and most recently on a > PATA drive I brute copied to a file and accessed as a drive on a virtual > machine. It will get started one more time, to run DBAN on it and clean > off the data. Part of my "January is 'clean your office' month" program. > I can remember dropping a SCSI drive or two 4" to 6" onto the desk to free it up so it would spin up again. (Drop so it lands flat on its bottom, not sides or ends.) This was often necessary on drives that had run non-stop for years, and were shut down long enough to cool off. (Moving a computer room...) I believe there was a repair spec describing this... Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
jdow wrote: It sounds like the drive cannot get its head mounted and simply hangs somehow. It's not useful for backups. If I had data on it there are some "hacks" I might try, sharply twisting the drive on the axis of rotation as power is applied, for example. Sometimes that will get the disk to spin up if that's the problem. I've managed to rescue data that way a couple times. I like "drive tapping" myself for spinup. Start tapping the drive with the handle of a screwdriver (side impact, not on top) and apply power. I have used that with success back to ESDI days, and most recently on a PATA drive I brute copied to a file and accessed as a drive on a virtual machine. It will get started one more time, to run DBAN on it and clean off the data. Part of my "January is 'clean your office' month" program. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
On Thu, 2009-01-01 at 16:44 -0800, jdow wrote: > there are some "hacks" I might try, sharply twisting the drive on the > axis of rotation as power is applied, for example. Sometimes that will > get the disk to spin up if that's the problem. I've managed to rescue > data that way a couple times. I am now imagining how you start your computer: One foot on the chassis, and pulling a rope out the front, like an outboard motor on a small boat. ;-) -- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
From: "Jorge Luis" Sent: Thursday, 2009, January 01 13:06 jdow: OK, let's break the problem down into smaller pieces. Do you have a known good drive you can test on that adapter? Does it work? I have four drives that I'm using with the converter, including another 200 GiB Maxtor; all of them are EIDE. Only one of the drives exhibits this behavior; the others are fine. All drives are ext3. At this point one might suggest the drive is toast. Plugging the interface onto the drive upside down can do that. When you say you've tried with an EIDE cable how do you know the drive was not found? Did you look at dmesg after booting? Here is the dmesg output when the faulty drive is unplugged from a USB 2.0 input and then plugged into the running box again. [81041.572000] usb 4-6: USB disconnect, address 16 [81056.170272] usb 4-6: new high speed USB device using ehci_hcd and address 17 [81056.303917] usb 4-6: configuration #1 chosen from 1 choice [81056.348793] scsi11 : SCSI emulation for USB Mass Storage devices [81056.358481] usb-storage: device found at 17 [81056.358490] usb-storage: waiting for device to settle before scanning The output from the operation stops there; no other messages are emitted. It sounds like the drive is not spinning up or has not spun up. Holding it in your hand when you apply power to it can inform you somewhat about what is happening. If it gives a solid "clunk" then sits idle the head could not load and went back to idle. A damaged track might happen from pulling power while writing to the drive. I guess an obvious question is, "How did you abort the gpartd operation?" Pulling power while a drive is writing is "not a good thing." If I wrote that an aborted gparted was a likely suspect, I misspoke. I meant to say that I bailed out of a GRUB configuration. It was some time ago that this possibly unrelated event occured. It is true that neither gparted, nor parted, nor fdisk can find the drive now while scanning devices. Yes, you did say GRUB. My antiquated chunk of gray goo I call a brain twisted that up into gparted. Did you exit the configuration or did you bail out by pulling power? And a sense of your urgency to recover the drive might help. Is it a new one you'd hate to lose but all you'd lose is the drive or did it have a lot of precious data on it that you have to figure out how to recover, now. (If it is the latter you are going to have to do some serious learning and have the patience of Job.) We swap out three backup drives. One drive is always off the premises. An attempt to introduce the wonky drive back into the rotation gave me the first intimation of trouble. The drive contains no sensitive or irrecoverable information in its current state; I'd actually like to wipe it. I'm not about to go at it with Knoppix STD or some other forensic suite. Ah - well, you might learn more if you can actually mount it to a computer's IDE drive controller and see what happens. But the drive sounds like toast. If it's "too new for that to happen" remember that new drives have infantile failures. It's after the first few months of operation that drives are usually quite stable until well into old age. In terms of dmesg, set the drive to cable select. Plug it in to the drive cable as master (the end connector.) Plug the cable in to either of the IDE connectors, such as is free. Boot the machine. Interrupt the boot in the BIOS. Usually the first page contains a list of drives. Play with it to look for the drive. (Usually it's set to auto for all four possible IDE/PATA drives.) If you plugged into the secondary IDE connector check down, hold the drive in your hand, power up. You should FEEL the drive spin up.) No matter how the drive is jumpered--cable-select, primary, or slave (in the last instance, with the drive taking the secondary place on the primary EIDE ribbon)--the introduction of the drive locks up the computer. The machine halts just after the memory POST; from there, there's no way to get to the BIOS screens. It detects a legacy setting for USB storage and recognizes my precious IBM Model M as a legacy device and then stops cold. It's impossible to tell whether the BIOS recognizes the drive. There's no way into the BIOS screens, which are normally available after the POST by . The boot chain (at ) is similarly unavailable. I'd give up at this point. The drive is toast, sadly. How it got that way is a matter for conjecture. Hanging the BIOS POST is a little far out, though. You have an interesting case of failure there. If the BIOS finds the drive then exit the BIOS setup and proceed to the next step. Boot the machine. Then investigate /var/log/dmesg. Look through it for references to drives being found. (If need be save a dmesg from booting without the drive and one from booting with the drive and compare them. The drive should stick out in a diff like a sore thumb.) Note the drive's device name, say it is sdc
Re: Unrecognized Hard Drive
From: "Eli Pelcastre"
Sent: Thursday, 2009, January 01 11:19
Maybe this can guide you:
http://www-personal.umich.edu/~hnarayan/maxtor-harddrive-linux.html
Gustavo Eli Pelcastre H.
Aside from its egregious error using /dev/sda1 it's "sort of useful."
The first part of it will get him to the point of recognizing the drive.
{^_^}
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: > > No matter how the drive is jumpered--cable-select, primary, or slave (in the > last instance, with the drive taking the secondary place on the primary EIDE > ribbon)--the introduction of the drive locks up the computer. The machine > halts just after the memory POST; from there, there's no way to get to the > BIOS screens. It detects a legacy setting for USB storage and recognizes my > precious IBM Model M as a legacy device and then stops cold. It's impossible > to tell whether the BIOS recognizes the drive. There's no way into the BIOS > screens, which are normally available after the POST by . The boot chain > (at ) is similarly unavailable. > This puts a different light on the problem. This sure sounds like a hardware problem. Did someone drop the drive, or try and hot plug it? Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
jdow: > OK, let's break the problem down into smaller pieces. Do you have a known > good drive you can test on that adapter? Does it work? I have four drives that I'm using with the converter, including another 200 GiB Maxtor; all of them are EIDE. Only one of the drives exhibits this behavior; the others are fine. All drives are ext3. > When you say you've tried with an EIDE cable how do you know the drive was > not found? Did you look at dmesg after booting? Here is the dmesg output when the faulty drive is unplugged from a USB 2.0 input and then plugged into the running box again. [81041.572000] usb 4-6: USB disconnect, address 16 [81056.170272] usb 4-6: new high speed USB device using ehci_hcd and address 17 [81056.303917] usb 4-6: configuration #1 chosen from 1 choice [81056.348793] scsi11 : SCSI emulation for USB Mass Storage devices [81056.358481] usb-storage: device found at 17 [81056.358490] usb-storage: waiting for device to settle before scanning The output from the operation stops there; no other messages are emitted. > I guess an obvious question is, "How did you abort the gpartd operation?" > Pulling power while a drive is writing is "not a good thing." If I wrote that an aborted gparted was a likely suspect, I misspoke. I meant to say that I bailed out of a GRUB configuration. It was some time ago that this possibly unrelated event occured. It is true that neither gparted, nor parted, nor fdisk can find the drive now while scanning devices. > And a sense of your urgency to recover the drive might help. Is it a new > one you'd hate to lose but all you'd lose is the drive or did it have a > lot of precious data on it that you have to figure out how to recover, now. > (If it is the latter you are going to have to do some serious learning and > have the patience of Job.) We swap out three backup drives. One drive is always off the premises. An attempt to introduce the wonky drive back into the rotation gave me the first intimation of trouble. The drive contains no sensitive or irrecoverable information in its current state; I'd actually like to wipe it. I'm not about to go at it with Knoppix STD or some other forensic suite. > In terms of dmesg, set the drive to cable select. Plug it in to the drive > cable as master (the end connector.) Plug the cable in to either of the > IDE connectors, such as is free. Boot the machine. Interrupt the boot in > the BIOS. Usually the first page contains a list of drives. Play with it > to look for the drive. (Usually it's set to auto for all four possible > IDE/PATA drives.) If you plugged into the secondary IDE connector check > down, hold the drive in your hand, power up. You should FEEL the drive > spin up.) No matter how the drive is jumpered--cable-select, primary, or slave (in the last instance, with the drive taking the secondary place on the primary EIDE ribbon)--the introduction of the drive locks up the computer. The machine halts just after the memory POST; from there, there's no way to get to the BIOS screens. It detects a legacy setting for USB storage and recognizes my precious IBM Model M as a legacy device and then stops cold. It's impossible to tell whether the BIOS recognizes the drive. There's no way into the BIOS screens, which are normally available after the POST by . The boot chain (at ) is similarly unavailable. > If the BIOS finds the drive then exit the BIOS setup and proceed to the > next step. Boot the machine. Then investigate /var/log/dmesg. Look through > it for references to drives being found. (If need be save a dmesg from > booting without the drive and one from booting with the drive and compare > them. The drive should stick out in a diff like a sore thumb.) Note the > drive's device name, say it is sdc. THAT is what you use with partd > or fdisk. (fdisk -l /dev/sdc) The closest I can come to having the drive recognized by the system is through the USB cage. When I introduce the drive using the Coolmax converter, dmesg records the messages that I quoted above, in which the drive is recognized as a USB storage device. However, no userspace program that I've tried sees the drive, not gparted, not parted. > If you get that far post the results of the fdisk -l and folks here will > probably try to help you. fdisk is similarly uninformative: r...@satyr:~# fdisk -l Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00010917 Device Boot Start End Blocks Id System /dev/sda1 * 1 304 2441848+ 83 Linux /dev/sda276507776 1020127+ 82 Linux swap / /dev/sda3 30401 181735312+ 83 Linux /dev/sda4 305764958998712+ 83 Linux Partition table entries are not in disk order Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 1606
Re: Unrecognized Hard Drive
Maybe this can guide you: http://www-personal.umich.edu/~hnarayan/maxtor-harddrive-linux.html Gustavo Eli Pelcastre H. > I have a 200 MiB Maxtor HD that isn't being seen by the OS. I have it > plugged > into the system through an EIDE/USB converter hub. It appears that the > drive > isn't recognized, but the hub device is. > > gparted doesn't see the drive at all. Here are the outputs of lsusb and > lspci. > > r...@satyr:~# lsusb > Bus 004 Device 010: ID 152d:2338 JMicron Technology Corp. / JMicron USA > Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge > Bus 004 Device 001: ID : > Bus 003 Device 002: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000 > Bus 003 Device 001: ID : > Bus 002 Device 002: ID 0d3d:0001 Tangtop Technology Co., Ltd > Bus 002 Device 001: ID : > Bus 001 Device 004: ID 03f0:4b11 Hewlett-Packard > Bus 001 Device 003: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse > Bus 001 Device 001: ID : > r...@satyr:~# > > r...@satyr:~# lspci > 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM > Controller/Host-Hub Interface (rev 01) > 00:02.0 VGA compatible controller: Intel Corporation > 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) > 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) > 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) > 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) > 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 > EHCI Controller (rev 01) > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81) > 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC > Interface Bridge (rev 01) > 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller > (rev 01) > 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) > SMBus Controller (rev 01) > 01:01.0 Modem: Broadcom Corporation BCM4212 v.90 56k modem > 01:02.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) > 01:02.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port > 01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) > Ethernet Controller (rev 81) > r...@satyr:~# > > I've jumpered the drive and brought it up in every possible permutation. > I > also tried mounting the drive as the slave on both primary and secondary > EIDE > cables. > > I'm hoping that perhaps someone here can help me out with this. > > Thanks in advance, > > JL > > -- > JL > This message optimized for teletypes. > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: > Mikkel L. Ellertson: >> Jorge Luis wrote: >>> Barring a very lucky attempt to fdisk the drive, I'm afraid I'm pretty much >>> screwed. I believe the drive failed when I bailed out of a GRUB >>> configuration >>> in the middle of the operation. I hope I didn't damage any of the drive's >>> native electronics or the resident software that's written to a small hidden >>> partition. >>> >> Grub will not damage the drive electronics, or wipe out any firmware >> the drive may have. (Accessing the firmware requires special >> commands.) Now, you may have wiped out the partition table, and boot >> sector. This would not prevent you from using fdisk or parted on the >> drive. >> >> Fdisk may have problems with the size of the drive. (Look at the >> bugs section of the fdisk man page...) It does not do well with >> large partitions. You are better off using parted. > > Nothing detects the drive, whether connected via the USB converter or plugged > into the computer's EIDE ribbon cables. Same story with parted, gparted, > fdisk, et al.--they simply don't see the drive. I don't think there's any way > to restore the partition table. dmesg and the kernel messages log seem to > indicate that the drive is there (see previous posts), but I can't work with > it unless the drive is registered with the system. > > The drive can be jumpered to set the capacity limit to a size that shouldn't > make for any problems with legacy software. It doesn't make a difference. > I'd guess my partition table is hosed. > > TIA, > > JL > What happens if you run "fdisk /dev/sdd" or "parted /dev/sdd"? (You have to run them as root...) Do they produce an error message, or do they just not show a partition table? The fix for a "hosed" partition table is to use fdisk or parted to create a new one. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
From: "Jorge Luis"
Sent: Thursday, 2009, January 01 10:27
Mikkel L. Ellertson:
Jorge Luis wrote:
>
> Barring a very lucky attempt to fdisk the drive, I'm afraid I'm pretty
> much
> screwed. I believe the drive failed when I bailed out of a GRUB
> configuration
> in the middle of the operation. I hope I didn't damage any of the
> drive's
> native electronics or the resident software that's written to a small
> hidden
> partition.
>
Grub will not damage the drive electronics, or wipe out any firmware
the drive may have. (Accessing the firmware requires special
commands.) Now, you may have wiped out the partition table, and boot
sector. This would not prevent you from using fdisk or parted on the
drive.
Fdisk may have problems with the size of the drive. (Look at the
bugs section of the fdisk man page...) It does not do well with
large partitions. You are better off using parted.
Nothing detects the drive, whether connected via the USB converter or
plugged
into the computer's EIDE ribbon cables. Same story with parted, gparted,
fdisk, et al.--they simply don't see the drive. I don't think there's any
way
to restore the partition table. dmesg and the kernel messages log seem to
indicate that the drive is there (see previous posts), but I can't work
with
it unless the drive is registered with the system.
The drive can be jumpered to set the capacity limit to a size that
shouldn't
make for any problems with legacy software. It doesn't make a difference.
I'd guess my partition table is hosed.
OK, let's break the problem down into smaller pieces. Do you have a known
good drive you can test on that adapter? Does it work?
When you say you've tried with an EIDE cable how do you know the drive was
not found? Did you look at dmesg after booting?
I guess an obvious question is, "How did you abort the gpartd operation?"
Pulling power while a drive is writing is "not a good thing."
And a sense of your urgency to recover the drive might help. Is it a new
one you'd hate to lose but all you'd lose is the drive or did it have a
lot of precious data on it that you have to figure out how to recover, now.
(If it is the latter you are going to have to do some serious learning and
have the patience of Job.)
In terms of dmesg, set the drive to cable select. Plug it in to the drive
cable as master (the end connector.) Plug the cable in to either of the
IDE connectors, such as is free. Boot the machine. Interrupt the boot in
the BIOS. Usually the first page contains a list of drives. Play with it
to look for the drive. (Usually it's set to auto for all four possible
IDE/PATA drives.) If you plugged into the secondary IDE connector check
the master drive on the secondary connector's entry in the BIOS table,
usually the third entry. Tab down to that entry and hit ENTER if it says
AUTO. If the drive is not found there it is toast. (At that point power
down, hold the drive in your hand, power up. You should FEEL the drive
spin up.)
If the BIOS finds the drive then exit the BIOS setup and proceed to the
next step. Boot the machine. Then investigate /var/log/dmesg. Look through
it for references to drives being found. (If need be save a dmesg from
booting without the drive and one from booting with the drive and compare
them. The drive should stick out in a diff like a sore thumb.) Note the
drive's device name, say it is sdc. THAT is what you use with partd
or fdisk. (fdisk -l /dev/sdc)
If you get that far post the results of the fdisk -l and folks here will
probably try to help you.
{^_^} Joanne
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Mikkel L. Ellertson: > Jorge Luis wrote: > > > > Barring a very lucky attempt to fdisk the drive, I'm afraid I'm pretty much > > screwed. I believe the drive failed when I bailed out of a GRUB > > configuration > > in the middle of the operation. I hope I didn't damage any of the drive's > > native electronics or the resident software that's written to a small hidden > > partition. > > > Grub will not damage the drive electronics, or wipe out any firmware > the drive may have. (Accessing the firmware requires special > commands.) Now, you may have wiped out the partition table, and boot > sector. This would not prevent you from using fdisk or parted on the > drive. > > Fdisk may have problems with the size of the drive. (Look at the > bugs section of the fdisk man page...) It does not do well with > large partitions. You are better off using parted. Nothing detects the drive, whether connected via the USB converter or plugged into the computer's EIDE ribbon cables. Same story with parted, gparted, fdisk, et al.--they simply don't see the drive. I don't think there's any way to restore the partition table. dmesg and the kernel messages log seem to indicate that the drive is there (see previous posts), but I can't work with it unless the drive is registered with the system. The drive can be jumpered to set the capacity limit to a size that shouldn't make for any problems with legacy software. It doesn't make a difference. I'd guess my partition table is hosed. TIA, JL -- JL Late capitalism has reduced us to isolated integers of acquisitiveness. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: > > See my previous message regarding kernel messages. > I replied to that one as well. > The converter has a brick power supply that provides power to IDE drives. > Separately, the converter hub is a USB 2.0 interface with two USB connectors. > One of them provides bus power to SATA drives; the other USB plug is a > straight-through connector that communicates with the hard drive that's > plugged into the hub. > Ok - I read the specs. The brick is used to power 5-1/4" and 3-1/2" drives. 2-1/2" laptop drives are powered off the USB bus. In the case of 2-1/2" drives, you are going to want to plug in the "power" USB plug first, wait 10 seconds, and then plug in the "full" USB plug. When using the brick, plug in and turn on the brick first. This isn't always necessary, but I have found it works best with the adapters of this type that I have used. For some reason, the external 3-1/2" and 5-1/4" cases do not seam to have these problems, but the 2-1/2", bus powered cases do. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: > > Here's another tip for you all: > > r...@satyr:~# demsg | tail -12 > [73223.969759] usb 4-6: USB disconnect, address 11 > [73234.083956] usb 4-6: new high speed USB device using ehci_hcd and address > 13 > [73234.603566] usb 4-6: device not accepting address 13, error -71 > [73272.550985] usb 4-6: new high speed USB device using ehci_hcd and address > 15 > [73272.684685] usb 4-6: configuration #1 chosen from 1 choice > [73272.697756] scsi9 : SCSI emulation for USB Mass Storage devices > [73272.702383] usb-storage: device found at 15 > [73272.702391] usb-storage: waiting for device to settle before scanning > [73277.692887] usb-storage: device scan complete > [73277.694470] scsi 9:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS > [73277.707413] sd 9:0:0:0: [sdd] Attached SCSI disk > [73277.707491] sd 9:0:0:0: Attached scsi generic sg4 type 0 > Well, the drive is being found, but it does not look like any partitions are being found. It is being assigned as /dev/sdd. I would try using parted or qparted on /dev/sdd. You may have to create a new partition table. (Make sure you are using hte correct drive before saving a new partition table!!!) Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Mikkel L. Ellertson: > Jorge Luis wrote: > > I have a 200 MiB Maxtor HD that isn't being seen by the OS. I have it > > plugged > > into the system through an EIDE/USB converter hub. It appears that the > > drive > > isn't recognized, but the hub device is. > > > It would be handy to see the messages in /var/log/messages when you > plug the drive in. It would also help to know more about the > EIDE/USB converter. Does it have its own power supply, or is it bus > powered? Has it worked on any other machine? > > If possible, power up the drive and let it spin up before plugging > in the converter. See my previous message regarding kernel messages. The converter has a brick power supply that provides power to IDE drives. Separately, the converter hub is a USB 2.0 interface with two USB connectors. One of them provides bus power to SATA drives; the other USB plug is a straight-through connector that communicates with the hard drive that's plugged into the hub. You can see one of these adapters at: http://www.amazon.com/s/ref=nb_ss_pc?url=search-alias%3Dcomputers&field-keywords=coolmax+ide+sata&x=0&y=0 Thanks for your help. JL -- JL Mad, bad, and dangerous to know. --Caroline Lamb on Lord Byron -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: > > Barring a very lucky attempt to fdisk the drive, I'm afraid I'm pretty much > screwed. I believe the drive failed when I bailed out of a GRUB configuration > in the middle of the operation. I hope I didn't damage any of the drive's > native electronics or the resident software that's written to a small hidden > partition. > Grub will not damage the drive electronics, or wipe out any firmware the drive may have. (Accessing the firmware requires special commands.) Now, you may have wiped out the partition table, and boot sector. This would not prevent you from using fdisk or parted on the drive. Fdisk may have problems with the size of the drive. (Look at the bugs section of the fdisk man page...) It does not do well with large partitions. You are better off using parted. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis: > Robert Nichols: > > Jorge Luis wrote: > >> I have a 200 MiB Maxtor HD that isn't being seen by the OS. I have it > >> plugged > >> into the system through an EIDE/USB converter hub. It appears that the > >> drive > >> isn't recognized, but the hub device is. > > > > Was the drive powered up and ready when you plugged the converter into > > the USB port? The scan is performed when the new USB connection is > > seen, and if you want the drive to be seen it has to be ready at that > > time. There's probably a way to force a re-scan later, but I don't > > know what that might be. > > Bob, > > Thanks for the tip. I've actually tried the sequence you recommend, without > success. > > Barring a very lucky attempt to fdisk the drive, I'm afraid I'm pretty much > screwed. I believe the drive failed when I bailed out of a GRUB configuration > in the middle of the operation. I hope I didn't damage any of the drive's > native electronics or the resident software that's written to a small hidden > partition. > > Thanks, > > JL Here's another tip for you all: r...@satyr:~# demsg | tail -12 [73223.969759] usb 4-6: USB disconnect, address 11 [73234.083956] usb 4-6: new high speed USB device using ehci_hcd and address 13 [73234.603566] usb 4-6: device not accepting address 13, error -71 [73272.550985] usb 4-6: new high speed USB device using ehci_hcd and address 15 [73272.684685] usb 4-6: configuration #1 chosen from 1 choice [73272.697756] scsi9 : SCSI emulation for USB Mass Storage devices [73272.702383] usb-storage: device found at 15 [73272.702391] usb-storage: waiting for device to settle before scanning [73277.692887] usb-storage: device scan complete [73277.694470] scsi 9:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS [73277.707413] sd 9:0:0:0: [sdd] Attached SCSI disk [73277.707491] sd 9:0:0:0: Attached scsi generic sg4 type 0 Thanks to you all. JL -- JL Beware of all enterprises that require new clothes. --Thoreau -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Robert Nichols: > Jorge Luis wrote: >> I have a 200 MiB Maxtor HD that isn't being seen by the OS. I have it >> plugged >> into the system through an EIDE/USB converter hub. It appears that the drive >> isn't recognized, but the hub device is. > > Was the drive powered up and ready when you plugged the converter into > the USB port? The scan is performed when the new USB connection is > seen, and if you want the drive to be seen it has to be ready at that > time. There's probably a way to force a re-scan later, but I don't > know what that might be. Bob, Thanks for the tip. I've actually tried the sequence you recommend, without success. Barring a very lucky attempt to fdisk the drive, I'm afraid I'm pretty much screwed. I believe the drive failed when I bailed out of a GRUB configuration in the middle of the operation. I hope I didn't damage any of the drive's native electronics or the resident software that's written to a small hidden partition. Thanks, JL -- JL This message optimized for teletypes. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: > I have a 200 MiB Maxtor HD that isn't being seen by the OS. I have it plugged > into the system through an EIDE/USB converter hub. It appears that the drive > isn't recognized, but the hub device is. > It would be handy to see the messages in /var/log/messages when you plug the drive in. It would also help to know more about the EIDE/USB converter. Does it have its own power supply, or is it bus powered? Has it worked on any other machine? If possible, power up the drive and let it spin up before plugging in the converter. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unrecognized Hard Drive
Jorge Luis wrote: I have a 200 MiB Maxtor HD that isn't being seen by the OS. I have it plugged into the system through an EIDE/USB converter hub. It appears that the drive isn't recognized, but the hub device is. Was the drive powered up and ready when you plugged the converter into the USB port? The scan is performed when the new USB connection is seen, and if you want the drive to be seen it has to be ready at that time. There's probably a way to force a re-scan later, but I don't know what that might be. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
