If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Maxtor Drive Belly Up!
Greetings:
I have a 6 month old Dell Dimension 8400 with 2 Maxtor 6Y160M0 drives (160GB) attached to an internal Intel RAID Controller configured as RAID 0 (stripe) that won't boot. I get an "Error Occured(0)" on the first drive (drive 0). Below is the Intel Config Utility Report: Intel Application Accelerator RAID Option ROM v4.0.0.6211 RAID Volumes: ID Name Level Stripe Size Status Bootable 0 ARRAY RAID0(Stripe) 128kb 298.0GB Normal Yes Physical Disks: Port Drive Model Serial # Size Type/Status(Vol ID) 0 Maxtor 6Y160M0 Serial # 149.0GB Error Occured(0) 2 Maxtor 6Y160M0 Serial # 149.0GB Member Disk(0) If I try to run the Dell Hard Drive Diagnostics (CTRL-ALT-D, note the "D" key, not the "Del" key"), it tells me: Drive 0: Maxtor 6Y160M0 - Fail. Return Code: 7 ALL other drives appear healthy as expected. If I try to boot into XP Pro (Safe or LKG config), I get a BSOD with "UNMOUNTABLE_BOOT_VOLUME" STOP 0X00000ED, which would be expected at this point. What puzzles me is why Status above is Normal and Bootable is Yes. Is this just the controller reporting back? Dell says they are sending a new drive, but is there any way to get this drive to come back so I can get the data off? Partition Magic 8 (boot from CD) sees a drive but reports "Error #48" and can't repair the drive. Based on all this data, it would appear the drive interface electronics might be working (diags can see it as a Maxtor 6Y160M0), but maybe drive is not spinning up??? Any software out there that might help? Maxtor's PowerMax won't see it because its in a RAID config, but if I remove it from the 8400 and place it in my 8300 (non-RAID system that I have), I am afraid it might do something to the data integrity on that striped disk. I know this is a lot to swallow, but I figured I would present all my data right away, to minimize time and questions. Do you think "Drive Savers" can do anything here? Anyone one have any experience with there pricing? Thanks in advance, Bret |
#2
|
|||
|
|||
Previously Bret wrote:
[...] What puzzles me is why Status above is Normal and Bootable is Yes. Is this just the controller reporting back? Looks very much like it. Dell says they are sending a new drive, but is there any way to get this drive to come back so I can get the data off? The '0' in RAID0 stands for zero redundancy'. Unless you get the defective drive to work again, your data is gone. Partition Magic 8 (boot from CD) sees a drive but reports "Error #48" and can't repair the drive. Based on all this data, it would appear the drive interface electronics might be working (diags can see it as a Maxtor 6Y160M0), but maybe drive is not spinning up??? Any software out there that might help? If the disk is gone, unlikely. If it just has a high rate of errors, a knowledgeable person might be able to copy the data off sector by sector and reconstruct it on a spare disk. A RAID controller may deem a disk unfit for use for any number of reasons, some of them still allowing pure-software data recovery that does not require disk-specific knowledge or tools. It is really impossible to tell what the problem of the disk is without further diagnostics. Maxtor's PowerMax won't see it because its in a RAID config, but if I remove it from the 8400 and place it in my 8300 (non-RAID system that I have), I am afraid it might do something to the data integrity on that striped disk. Unlikely, if you boot the machine with the PowerMax floppy disk. The BIOS does not usually write to disks by itself. On the other hand PowerMax does not tell you a lot. Getting a SMART attribute listing from the disk would be far more enlightening. My advice: Mess as little as possible with the defective drive. First try to copy the data to a second disk to conserve it. The drive may still be readable, but usually the symptoms get worse. For copying I would use 'dd_rescue' from a KNOPPIX CD-only Linux, since it can copy from sources with errors. For this you need a spare disk that is at least as large as your defective disk (in sectors!), a PC with CDROM and a KNOPPIX CD. Procedure is like this: 1. Remove all other disks from the PC. 2. Add the source (defective) and target disks as first and second disks to the system. 3. Boot from the KNOPPIX CD. 4. Go to a text-console (the GUI does not allow you to become root ieasily): crtl-alt-F2 5. Check where your sisks a fdisk -l Should list the two HDDs either as /dev/hda and /dev/hdb or as /dev/sda and /dev/sdb. The second set is SATA vie SCSI driver, the first is SATA via the ATA driver. Depengind on Linux kernel version you can see either. If it is the first, you can also read the full SMART attribute list with the command smartctl -a /dev/hda Unfortunately for the second version SMART is not yet (reliably) implemented with Linux. 6. Copy: dd_rescue /dev/hda /dev/hdb This will copy over the first disk to the second sector by sector. It will not abort on read errors but list them. There will be a progress indicator. 7. If the copying finishes withouut error, congratulations, your data is still there. You can now put the target disk into your RAID array in place of the defective one. If there are errors you can still try that, but there might be holes in the target. If ther are errors you can also try to copy the affected areas again, by using the '-s position' and '-m amount to be copied' options of dd_rescue to try specific parts again. You can exit from Knoppix by giving it the 'halt' command. Arno |
#3
|
|||
|
|||
Thanks for all the info. For the last few hours I have been perusing the
'net for some solutions. I tried hddreg.exe demo version on a floppy disk and it sees the full RAID as one disk or volume along with the full 300GB+. It scans sectors and sees errors, but the demo version only corrects the first encountered bad sector then stops. You can repeat the process, instructing the program to start with the next sector, but this is labor intensive as I quickly found out. If I knew it was actually going to fix my problem, I'd buy the full version, but I would be out $60 if it didn't allow me to recover the data. If you add up the cost of all the software that is out there to do this, it could be cheaper to try a recovery service. Anyway the good news is that on the sector level, the drive appears to be readable, so it would seem the drive is spinning and the drive interface is working. Perhaps Knoppix is the solution, and I will try it out when Dell sends me the replacement drive so that I will have a target of sufficient size to dump to. Meanwhile, there is a product out there called RAID Reconstructor that claims it can take a RAID 0 config and move data off of it onto other media, like a DVD+R or what ever. It has a 30 day trial, then $99 for full use. Right now I am having some problems with the boot CD creation process that they recommend with BartPE software. CD gets created without error, but when I boot with it, it gets to the "BartPE" splash screen and then freezes. Need to work on it some more. Thanks, Bret |
#4
|
|||
|
|||
Bret:
I might give a word of friendly caution here, the less you mess with that the better if your data is even remotely important. I suggest a recovery service, one who does raid in particular. IF the data is less than critical, then by all means have at it and good luck!!!! Let me know if I can be of any assistance - Media Recovery Engineer |
#5
|
|||
|
|||
"Jimguru" wrote:
Bret: I might give a word of friendly caution here, the less you mess with that the better if your data is even remotely important. I suggest a recovery service, one who does raid in particular. IF the data is less than critical, then by all means have at it and good luck!!!! Let me know if I can be of any assistance - Media Recovery Engineer I’m having the same problem with 2 Maxtor Hard Drives in Raid 0 on a Dell 8400. If anyone has an update to this situation, it would be great to see! I tried Knoppix and I could not get the drive to mount. What commands should I try or is there any other software out there that might help? Thanks in advance. -- Posted using the http://www.hardwareforumz.com interface, at author's request Articles individually checked for conformance to usenet standards Topic URL: http://www.hardwareforumz.com/PC-Sto...pict55915.html Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.hardwareforumz.com/eform.php?p=284917 |
#6
|
|||
|
|||
"Bret" wrote:
Greetings: I have a 6 month old Dell Dimension 8400 with 2 Maxtor 6Y160M0 drives (160GB) attached to an internal Intel RAID Controller configured as RAID 0 (stripe) that won't boot. I get an "Error Occured(0)" on the first drive (drive 0). Below is the Intel Config Utility Report: Intel Application Accelerator RAID Option ROM v4.0.0.6211 RAID Volumes: ID Name Level Stripe Size Status Bootable 0 ARRAY RAID0(Stripe) 128kb 298.0GB Normal Yes Physical Disks: Port Drive Model Serial # Size Type/Status(Vol ID) 0 Maxtor 6Y160M0 Serial # 149.0GB Error Occured(0) 2 Maxtor 6Y160M0 Serial # 149.0GB Member Disk(0) If I try to run the Dell Hard Drive Diagnostics (CTRL-ALT-D, note the "D" key, not the "Del" key"), it tells me: Drive 0: Maxtor 6Y160M0 - Fail. Return Code: 7 ALL other drives appear healthy as expected. If I try to boot into XP Pro (Safe or LKG config), I get a BSOD with "UNMOUNTABLE_BOOT_VOLUME" STOP 0X00000ED, which would be expected at this point. What puzzles me is why Status above is Normal and Bootable is Yes. Is this just the controller reporting back? Dell says they are sending a new drive, but is there any way to get this drive to come back so I can get the data off? Partition Magic 8 (boot from CD) sees a drive but reports "Error #48" and can't repair the drive. Based on all this data, it would appear the drive interface electronics might be working (diags can see it as a Maxtor 6Y160M0), but maybe drive is not spinning up??? Any software out there that might help? Maxtor's PowerMax won't see it because its in a RAID config, but if I remove it from the 8400 and place it in my 8300 (non-RAID system that I have), I am afraid it might do something to the data integrity on that striped disk. I know this is a lot to swallow, but I figured I would present all my data right away, to minimize time and questions. Do you think "Drive Savers" can do anything here? Anyone one have any experience with there pricing? Thanks in advance, Bret I think I’m having the same problem. A Dell 8400 with a Maxtor Drive. Dell replaced the drive on site, but it is still doing the same thing. Bret, what was your problem in the end? Regards, Frank -- Posted using the http://www.hardwareforumz.com interface, at author's request Articles individually checked for conformance to usenet standards Topic URL: http://www.hardwareforumz.com/PC-Sto...pict55915.html Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.hardwareforumz.com/eform.php?p=292874 |
#7
|
|||
|
|||
"" wrote:
Greetings: I have a 6 month old Dell Dimension 8400 with 2 Maxtor 6Y160M0 drives (160GB) attached to an internal Intel RAID Controller configured as RAID 0 (stripe) that won't boot. I get an "Error Occured(0)" on the first drive (drive 0). Below is the Intel Config Utility Report: Intel Application Accelerator RAID Option ROM v4.0.0.6211 RAID Volumes: ID Name Level Stripe Size Status Bootable 0 ARRAY RAID0(Stripe) 128kb 298.0GB Normal Yes Physical Disks: Port Drive Model Serial # Size Type/Status(Vol ID) 0 Maxtor 6Y160M0 Serial # 149.0GB Error Occured(0) 2 Maxtor 6Y160M0 Serial # 149.0GB Member Disk(0) If I try to run the Dell Hard Drive Diagnostics (CTRL-ALT-D, note the "D" key, not the "Del" key"), it tells me: Drive 0: Maxtor 6Y160M0 - Fail. Return Code: 7 ALL other drives appear healthy as expected. If I try to boot into XP Pro (Safe or LKG config), I get a BSOD with "UNMOUNTABLE_BOOT_VOLUME" STOP 0X00000ED, which would be expected at this point. What puzzles me is why Status above is Normal and Bootable is Yes. Is this just the controller reporting back? Dell says they are sending a new drive, but is there any way to get this drive to come back so I can get the data off? Partition Magic 8 (boot from CD) sees a drive but reports "Error #48" and can't repair the drive. Based on all this data, it would appear the drive interface electronics might be working (diags can see it as a Maxtor 6Y160M0), but maybe drive is not spinning up??? Any software out there that might help? Maxtor's PowerMax won't see it because its in a RAID config, but if I remove it from the 8400 and place it in my 8300 (non-RAID system that I have), I am afraid it might do something to the data integrity on that striped disk. I know this is a lot to swallow, but I figured I would present all my data right away, to minimize time and questions. Do you think "Drive Savers" can do anything here? Anyone one have any experience with there pricing? Thanks in advance, Bret I have exact the same problem. What to do? Can’t repair Windows XP while it can’t find my harddrive. Dimension 8400, two 6Y160M0 in RAID configuration -- Posted using the http://www.hardwareforumz.com interface, at author's request Articles individually checked for conformance to usenet standards Topic URL: http://www.hardwareforumz.com/PC-Sto...pict55915.html Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.hardwareforumz.com/eform.php?p=305716 |
#8
|
|||
|
|||
"jhn" wrote:
I have exact the same problem. What to do? Can't repair Windows XP while it can't find my harddrive. Dimension 8400, two 6Y160M0 in RAID configuration same damn problem here...same dimension, hdd..etc.. now the good thing out of playing around...with some linux live cd’s for a while, I found out the only one out of a bunch that did the work for me was Slax 5.0.6 you can see the hdd. read the content etc... good luck and let’s suit those lossers on Dell and Microsoft (...windows sucks... !) we’re lossing valuable time ..with this kind of annoiances... |
#9
|
|||
|
|||
"kaliman" wrote:
same damn problem here...same dimension, hdd..etc.. now the good thing out of playing around...with some linux live cd's for a while, I found out the only one out of a bunch that did the work for me was Slax 5.0.6 you can see the hdd. read the content etc... good luck and let's suit those lossers on Dell and Microsoft (...windows sucks... !) we're lossing valuable time ..with this kind of annoiances... upadate...!.. well; after rescueing my data using Slax 5.0.6 live cd, I run the free version of killdisk to write 00’s in one quick pass then using a regular boot cd, (no floppy here) I create a new partition but did not formated the c: drive( to slow in dos)well again I try to install xp pro in a miriad of ways(using different ways, like floppie’s, mounting the i386 folder to hd..etc..nope,,can’t see hdd.. like before, (even I try the new windows vista beta 1 etc....)..inposible to detect the maxtor sata hdd, well.. hell with windows....this is my friends pc..and 2 months after warranty expiration date..and no imediate budget for a new hdd. I decide to try Suse 10.0 beta 4.. and .. blammm...!! detected the had...even saw the reminences of windows on it(RIP) and ...right away It was partitioned in a blink of an eye. Hell man!..linux...forever....I’m telling you guys and gals..try linux on this drive...for now. is the only option I hope this dude like his new pc with quality O.S. .I’ll help him out all the way. good luck guys...sorry for this long posts..and my english...still learning..have a nice life. |
#10
|
|||
|
|||
"kaliman" wrote:
upadate...!.. well; after rescueing my data using Slax 5.0.6 live cd, I run the free version of killdisk to write 00's in one quick pass then using a regular boot cd, (no floppy here) I create a new partition but did not formated the c: drive( to slow in dos)well again I try to install xp pro in a miriad of ways(using different ways, like floppie's, mounting the i386 folder to hd..etc..nope,,can't see hdd.. like before, (even I try the new windows vista beta 1 etc....)..inposible to detect the maxtor sata hdd, well.. hell with windows....this is my friends pc..and 2 months after warranty expiration date..and no imediate budget for a new hdd. I decide to try Suse 10.0 beta 4.. and .. blammm...!! detected the had...even saw the reminences of windows on it(RIP) and ...right away It was partitioned in a blink of an eye. Hell man!..linux...forever....I'm telling you guys and gals..try linux on this drive...for now. is the only option I hope this dude like his new pc with quality O.S. .I'll help him out all the way. good luck guys...sorry for this long posts..and my english...still learning..have a nice life. I did not give up. so doing some more reading I found the solution,which is on the bios settings..there you go...good luck to you guys.; When attemting to reinstall Windows on a Dimension 8400 or XPS Gen 3 system an error No Disks Detected occurs even when not in a RAID configuration. Discussion: This error is caused by the fact that the Windows XP media does not natively support the AHCI controller on these systems. In order to install Windows you must either load the drivers using the AHCI/RAID diskette during the install or turn off AHCI in the BIOS. Solution: If the customer has a floppy drive you can create the floppy disk using the following directions: 1) Boot to the Resource CD and select the Create AHCI driver from the list of items. (You will need a diskette for this selection.) 2) Once created, boot to the Operating System CD and start the installation. 3) Press the {F6} key to install the SCSI drivers. 4) Press the {S} key for specific drivers. 5) Insert the diskette and finish the installation. This will allow the operating system to be installed in AHCI mode. If the customer does not have a floppy drive or the option to create the AHCI disk is not in the Resource CDs menu, perform the following steps: 1) Enter the BIOS setup. 2) Use the Down-Arrow key to scroll down to Drives and press Enter to expand this menu. 2) Scroll down to select SATA Operation and press Enter to enter the menu. 3) Select RAID Autodetect / ATA Mode. 4) Save changes and exit the BIOS. This will allow the operating system to be installed in ATA mode. NOTE: If the customer is in a non-RAID configuration this will NOT cause a performance decrease. |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Belly up | Rudy Kazuti | Gigabyte Motherboards | 3 | February 4th 05 03:36 AM |
Epson CX5400. Scan Function and Status Monitor gone belly up? | IlanAvraham | Scanners | 0 | October 2nd 04 09:42 PM |
Epson CX5200 Went Belly Up After Changing An Ink Cartridge | T. D. Treat | Printers | 1 | September 15th 03 08:36 PM |