Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am playing with a WD 500GB drive which I replaced on my daughter's PC. The drive seemed to be misbehaving.
I cannot get it to work under Windows XP but I was able to recover ALL the data by booting the PC with Knoppix.
Since then I have found that I cannot make the drive work under Xp but it seems happy under Linux (Debian Unstable). I have created 4 partitions on this disc, formatted them to ext3 and run e2fsck on all of them - they passed. Under XP I could not even complete a format - the PC hung.
Does anybody know whether WD's dlgdiag5.exe, running in FreeDOS, will read an ext3 formatted disc? When I tried Quick Diagnostics the machine hung. I can reformat and try but maybe somebody can answer the question (in which case I can spend more time on my grandson's toy chest :-) )
dlgdiag5 doesn't really care about the file system, as it reads and writes raw blocks. However, as you say the bootable ISO uses FreeDOS, and it's entirely possible that FreeDOS could choke on an unknown file system or partition table.
If the drive cannot be formatted in XP, there could very well be something physically wrong with it. You should look at the S.M.A.R.T. parameters with smartctl. Specifically, the Reallocated_Sector_Ct and Current_Pending_Sector values should tell you if the drive is developing bad sectors. Try:
smartctl -a /dev/sda | grep _Sector
smartctl -a /dev/sda | less
to see all S.M.A.R.T. information about the drive.
You could also do a non-destructive surface test with badblocks. The following command will perform a non-destructive write test of of /dev/sda and display a progress indicator:
badblocks -o /dev/null -ns /dev/sda
Do not run badblocks on a disk containing a mounted file system. Use a Live CD.
FWIW, I've done lots of XP installations to 250 Gb and 320 Gb drives with a single partition without issues. I used source media with SP3, though.
I can find no TechNet reference to a 130 Gb partition size limit for Windows XP. There was a 32 Gb BIOS limit ages ago, and a 137 Gb EIDE/ATA limit for older OSes lacking 48-bit LBA support, but 130 Gb?
Actually, I'm pretty sure I've installed Windows 2000 to partitions larger than 130 Gb.
No matter what, we may need to know the exact service pack and motherboard to decide more. What hard drive did it have? Where did you get the xp from? Is it an OEM disk that may not have all the drivers?
As noted you'd have to use a slipstreamed cd of xp for any chance of success.
I think the 130 and 137 are the same issue.
Many hard drives have a jumper to limit chs to use the disk.
Usually dos diags do work in freedos. One can get the ultimate boot cd that has generic tools on it. One can also see if there is a bootable disk image at WD. The IBM/hitachi diags ought to work.
Thanks to all for very informative replies. Some background:
The OS was XP SP3, the disc was partitioned into 2 x 250GB partitions and the PC worked well for 3 years.
Eldest daughter told me that the USB keyboard had failed. I lent her a PS/2 keyboard. This worked for a short while and then the PC would not boot at all. Did the keyboard trigger the failure? Who can tell?
The overriding priority was data recovery and i was able to do this by booting with Knoppix and copying files to an external 1TB HDD. I then installed a new HDD and reinstalled XP and a few essential programs. We also threw away the old keyboard to avoid any possible recurrence of the disaster.
I am now playing with the old disc as I would like to work out whether it failed or not. Windows says did, Linux says didn't!
Smart ctl did not print anything alarming. When I ran it with -q errorsonly it exited silently.
I will be running badblocks later on and will come back here.
Apologies for taking so long to come back but the tests take a whole day to run and life also got in the way.
The disc is partitioned into 4, 2x100GB and 2x150GB
Badblocks listed 13 bad blocks on partition1.
It then listed 880 bad blocks on partition2.
e2fsck -c -c -k -v -C 0 /dev/sdg2
on partition 2 and it reported
/dev/sdg2: ***** FILE SYSTEM WAS MODIFIED *****
11 inodes used (0.00%, out of 6225920)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
406254 blocks used (1.63%, out of 24903680)
232 bad blocks
1 large file
Bad blocks are an indicator of hard drive failure some time in the near future, so I recommend you replace the HDD. The SMART long test also checks for bad blocks, but as there are already some, there's no need for it.
The disc is not being used, except for experimental purposes.
As I posted earlier I was able to recover all the data off it using Knoppix when Windows wouldn't even boot from it.
Since then I have NOT been able to repartition and reformat it under Windows but was able to build an ext3 filesystem on it which passes a "simple" e2fsck although e2fsck -c -c -k -v -C 0 /dev/sdg2 reports badblocks but fewer than badbloaks run on its own.
This disc is going into a queue for the recovery of its magnets (useful in the workshop) and the platters (my wife plans some craftwork using disc platters).
It is not the first time that Knoppix was able to recover just about anything on a disc when Windows choked on it.