Your email indicates iirc that you are using a deathstar hard drive. If you don't know the issues with the drives, I'd suggest searching on tech report's site for IBM GXP failure or similar search terms. And from personal experience (I lost two that were backing up to each other, a few days apart), I can tell you to IMMEDIATELY transfer all valuable data off of this drive. What you do with it after is your business. But I would strongly advise against using it for anything, except maybe a second swap drive that you can afford to have go down with little or no warning. Here's a few links for you to chew on: http://techreport.com/ja.zz?comments=3494 Note that the above link only appears to have one comment. They reformatted the site. Prior to the reformat, there were over 1000 comments there iirc. Similar to the next link. You might want to let the site owners know so that they make the comments available again. With the previous 1000+ comments, more comments were being added daily. This one: http://www.tech-report.com/news_reply.x/3494/ Is working a bit better than the previous one. http://techreport.com/onearticle.x/2799 http://techreport.com/onearticle.x/3465 Bing. On Thursday 19 June 2003 09:05 pm, you wrote:
For a year or so I've noticed some change in Linux has made dual OS life a bit interesting for me.
Typically I would create all of the partitions with Linux FDisk since it gave the most control over the task. For example the listing below:
Pri 100MB FAT C: Ext All Free Space Log 100MB Reiser /boot Log 2GB FAT D: Log 4GB FAT E: Log 4GB Reiser / Log 4GB Reiser /home Log 200MB Swap
Grub is the OS menu on the hard drive MBR.
Once Linux is installed and working, I then boot to MS DOS 7, check the partitions C, D, and E, format them, and unzip a prepared Windows image. Upon reboot, the partitions are scrambled - example:
<- GDISK Screen Scrape ->
Disk Partitions Cylinders Heads Sectors Mbytes Model 1 4 2501 255 63 19623.5 IBM-DTLA-307020
Partition Status Type Volume Label Mbytes System Usage 1 PRIMARY 682794.4 UNKNOWN 3479% 2 PRIMARY *UNKNOWN* 263172.0 UNKNOWN 1341% 3 PRIMARY *UNKNOWN* 10.4 UNKNOWN 1% 4 PRIMARY *UNKNOWN* 904228.1 UNKNOWN 4608%
<- GDISK Screen Scrape ->
The only solution I have found to this is to build the partitions with GDisk, then install Linux and set up file systems and mount points.
At first I thought it was the new Dell Optiplex GX150 system with Maxtor 40GB drive I had just gotten the first time this happened, payment for not keeping with the tradition of quality clone systems. But today the same thing happened on a clone system of mine - based on a Gigabyte GA7IXE4 with latest BIOS and an IBM 20GB drive. So all I can think is that it is the newer Linux code - FDisk...???
Ideas? Solutions?
TIA!
Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/