Unable to format drive
Folks - does anyone know why windows XP is saying it is unable to format a hard drive? I am adding an external 400gb drive and windows can see it, and I can set the drive letter ( L: ), but I can't use the drive because it needs to be formatted. When I try to format it, after windows goes through the whole lengthy process (hour long) of what appears to be formatting, it gives a short and sweet error message at the end "Windows was unable to complete the format". I guess i don't want to automatically assume the drive is bad, because of the hassle, and would rather try to troubleshoot the problem fist. I was wondering if anyone was familiar with this?
0
Comments
Funny that you ask. I tried to run error-checking from the disk properties on it, but nothing happens. And it doesnt schedule chkdsk to run on the drive at startup either. I tried to run chkdsk from the cmd prompt, but I'm not sure how for the chkdsk to run on the L drive and not my C drive.
chkdsk L: /r
OK. It does not run and comes back with an message: "The type of the file system is RAW. CHKDSK is not available for RAW drives."
This is the first I've heard or RAW drives. ??
Would GParted be of any assistance here, Thrax? Only other thing I can think of is a low-level format somewhere in the BIOS. Those are both rather intense, though.
What is GParted? Is it shareware?
OK - I tried to download it and it is .bz2 file. I'm not familiar with that file format.
http://sourceforge.net/project/showfiles.php?group_id=115843&package_id=271779
Either an ISO or a zip
Also what Jared said... I could have sworn I went to the Live section. Hrm.
OK - I will download it, read up on it, run it and let you know what happens. I have to go to work now, so will pick up on this saturday morning. Thanks!
Folks - can you give me some starting hints about how to use gparted. the zip file I downloaded has files that I am not clear how to proceed with it - or even how to create a bootable CD with it. help?
Download the ISO file at the link Jared posted, then use a burning program like ImgBurn or some other CD burning option, tell it you want to burn an image, and then point it at that ISO file. Then reboot and boot via CD to run GParted.
Update: got the bootable GParted CD running. The problem drive (L) is connected via firewire to the PC. At first, GParted sees the L drive, indicating it has no file system. So I attempt to format it using the NTFS option, and it begins and then stops and says the drive is not specified and to make sure you specify it. At that point, the L drive is no longer listed in GParted among the identified drives. Am I missing a step? What is the first thing I should do with GParted on this RAW drive?
Here are the on screen results from the last attempt to create a partition:
>create empty partition
- path: /dev/sda1
- start: 63
- end: 781417664
- size: 781417602 (327.61GB)
>set new partitiontype on /dev/sda1
- new partitiontype: ntfs
>create new ntfs filesystem
- mkntfs -Q -vv -L "" /dev/sda1
-- The device doesn't exist; did you specify it correctly?
That's it. What am I doing wrong?
What is DFT? Seatools in DOS means run Seatools from a DOS booted disk? The problem is it is an external drive and I suppose running tools from a DOS diskette wont support IEEE 1394 drivers?
Download it, run it, and see if your drive passes the test.
Sounds like it might be failing
Unfortunately, DFT "Does not support external USB or Firewire attached drives." So that shoots that idea out the window. There must be some tool that can scan and diagnose an externally attached drive, no?
http://www.seagate.com/www/en-us/support/downloads/seatools
I know that USB drives are just IDE drives with a IDE-USB interface in a box. You can open them up unplug the drive and plug it straight into your IDE on your PC. I assume the same is true with Firewire but I guess you will void any warrentee if you open the unit. I dont suppose you have any other firewire devices laying around to test with?
Doesn't that mean it's exceptionally accurate sometimes?
All I know is my son bought two new drives for nothing and according to Seatools they have both failed.
I took apart a PC and installed this drive into it so I am not attempting to test or format over the firewire link. Running DFT from a floppy. DFT seems to be finicky that this is not a Hitachi drive. If comes back with a Disposition code = 0x71. I searched the web and it means "The selected drive is not ready for operation. Check cabling and HDD connectors." Well, the cabling seems fine, given that the drive was properly identified by DFT.
I then tried to run Seatools from a CD and it doesnt see the drive. Maybe the jumber settings are wrong? I will play with that.
I think what might be an issue is this PC is using an ATA RAID controller card to attach to the drive, since the mother board on this PC does not support 48bit LBA. The PC runs fine in this configuration with the system drive being a 250gb drive connected to the RAID controller. (there is no RAID of drives, just one drive).
Thrax - if you take a look at my last post, do you think my PC Card drive controller which is also a RAID controller might be preventing me from running DFT? As a test, I used a known working hard drive connected to the RAID controller and booted from the DFT floppy and still ran into the 0x71 error message. So that means, it may not be a hard drive issue. Which is good news. I simply dont have a PC with a motherboard that supports 48bit LBA. I was shopping on ebay to look for a new PCI card based disk controller that is not specifically a RAID controller (in other words something simpler). This is what I found - do you think it may help?
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&ssPageName=STRK:MEWAX:IT&item=120332123214
Thanks.
A new controller may help, but obviously I cannot guarantee that.
Thanks. The controller card that is in there isnt very old, about 2 years, but it has RAID functions on it and I suspicious that may be gumming things up. So I was contemplating a simple controller card. Did you take a look at the link I sent you? What do you think?
I remain skeptical that the card is the problem when the drive is still having issues being connected via Firewire. The system shouldn't freak out, it should simply limit the maximum visible size to 127GB and move on with its life.