Hard drive shows up empty on reboot
in [Home Built PC]
|
From: JediSpork on 16 May 2010 02:10 I'm mostly sure its the hard drive and will be calling wd for another replacement. Actually the disc itself seems to be fine when it works except for this funky glitch. It will come up as 32 mb RAW in windows. It also shows the same amount of space in the bios yet when I use wd tools it shows the full capacity. I've already wrote 0's to the drive before I send it back. The backup drive works fine on the same sata connector. As for the bad comments about ntfs. I've never had a issue with ntfs either but I know they exist. I've heard that you can loose a entire drive due to a crash, power interruption, etc. I've heard that even Microsoft recognizes that ntfs has problems and we need a new file system. IMO win 7 should of had a new one. I'm no linux pro but ex3/4 is said to be vastly better. Faster, less bugs, and not as many problems with fragmentation.
From: Flasherly on 16 May 2010 03:38 On May 16, 2:10 am, JediSpork <jedisp...(a)gmail.com> wrote: > I'm mostly sure its the hard drive and will be calling wd for another > replacement. Actually the disc itself seems to be fine when it works > except for this funky glitch. It will come up as 32 mb RAW in windows. > It also shows the same amount of space in the bios yet when I use wd > tools it shows the full capacity. > > I've already wrote 0's to the drive before I send it back. The backup > drive works fine on the same sata connector. > > As for the bad comments about ntfs. I've never had a issue with ntfs > either but I know they exist. I've heard that you can loose a entire > drive due to a crash, power interruption, etc. I've heard that even > Microsoft recognizes that ntfs has problems and we need a new file > system. IMO win 7 should of had a new one. I'm no linux pro but ex3/4 > is said to be vastly better. Faster, less bugs, and not as many > problems with fragmentation. Sound like you know what you're doing if you're working with WD's utilities and able to compare results. I'm not the point where I can actually use the biggest drives I have properly, (my BIOS is too old and exceeded by limitations), so it's back to the translation thing via a USB drive "station's" electronics (free w/ a drive purchase makes it kinda nifty). Formatting, I want 3rd party utilities before going back to Windows, then the manufacturer's diagnostics/utilities, but only if problems surface, to be sure I know what I'm talking about before calling their techsupport hotline for a RMA (and start raising hell). You've got a "green" drive (laptop ported technology), so it's probably going to be big at a 3.5" interface -- could assume a minimum of 1T. RAW results - now, that I don't like (lazy Winderz man, though I get around good, very, in DOS and Unix is feasibly a pain if in need). You're also saying a Linux CD. Skip that unless you need and run Linux. Stay in the Windows environment start to finish. EASEUS is showing up freeware (limited?) version with some really highly- regarded reviews -- not sure, but they also may provide a boot ISO. Way I ran it, straight thru Windows and am impressed -- it was high time for me to force my mind to update from Partition Magic. Might try that for a second-opinion in the way of a 3rd party formatter. Suspect or problematic drives I wouldn't go near for active primaries, either, not until they started feeling stable. NTFS, whatever floats your boat. Times I'm do maintenance out of DOS, I'd as soon FAT32 transparent drives for various HD utilities that work with FAT, and don't bother with messing with programs such as off HIREMS to get into NTFS structures. When push comes to shove and I fall off Windows and onto my butt, like I said, it's second nature to me getting around in DOS. Might try EASEUS and FAT32 for funs&grins, anyway... Hm...think that docking station I got came with a 640MEG WD (non-green 7200) that worked in my old socket 754 AMD BIOS, and effectively saved my butt harder work when transferring off what I needed on the crashed 1T NTFS via USB (migrated the 640G WD into the box's HD cage, displacing one of my 200M old Seagates for backup medium). When I bought the 1T Samsung, it was after looking over NewEgg's WD reviews -- seemed to me Samsung, then Hitachi, had a definite edge on WD in the failure-rate dept. Drop a line back if you try EASEUS.
From: John Doe on 16 May 2010 08:02 JediSpork <jedispork(a)gmail.com> wrote: > I'm mostly sure its the hard drive You need to test it in another computer.
From: Don Phillipson on 15 May 2010 09:23 "JediSpork" <jedispork(a)gmail.com> wrote in message news:f932c8c2-56f7-41ac-9ccc-990d60e58364(a)s41g2000vba.googlegroups.com... > Had a problem with my first wd green drive. Using the replacement now. > Sometimes when I reboot the drive will show up as empty in windows > ready to be formatted. Now it stays this way and the only way to > access is through a linux cd. I've tried wiping the drive and > creating a brand new partition but after reboot the problem is back. > Also tried doing a full scan for errors and bad sectors and everything > shows up fine. Does this sound like another faulty drive? These intermittent errors suggest the user should find out whether the fault is in the Master Boot Region or elsewhere on the drive. Tools for the MBR are (early) FDISK /MBR or (late) FIXMBR. Either seems worth a try. -- Don Phillipson Carlsbad Springs (Ottawa, Canada)
From: Franc Zabkar on 5 Jun 2010 05:27
On Sat, 15 May 2010 23:10:40 -0700 (PDT), JediSpork <jedispork(a)gmail.com> put finger to keyboard and composed: >I'm mostly sure its the hard drive and will be calling wd for another >replacement. Actually the disc itself seems to be fine when it works >except for this funky glitch. It will come up as 32 mb RAW in windows. >It also shows the same amount of space in the bios yet when I use wd >tools it shows the full capacity. I'm betting that you have a Gigabyte motherboard with an Xpress Recovery BIOS, and that your drive has a native capacity of 1TB. If so, then your BIOS has a bug that is truncating your drive. What happens is that the BIOS writes a copy of itself to the uppermost LBAs of the drive, and then hides this image by reducing the capacity of the drive by a corresponding amount. This thread has more information: http://forum.hddguru.com/viewtopic.php?f=1&t=15662 The above bug causes 1TB drives to be reduced to 32MB, 1.5TB drives become 500GB, and 2TB drives shrink to 1TB. The solution is to remove the HPA (Host Protected Area) using a tool such as HDAT2. - Franc Zabkar -- Please remove one 'i' from my address when replying by email. |