Joe L. Posted April 1, 2010 Share Posted April 1, 2010 my vista machine (with the telnet sessions) rebooted due to a windows update. That was funny! (Sorry, ShawnFumo!) Earlier in this thread Joe L. made a very good suggestion to run the preclear script in a "screen" session. That way you can detach from it, and later reattach to it from anywhere. http://lime-technology.com/forum/index.php?topic=2817.msg24827#msg24827 Screen is the way to go for any long running command. True... And, don't assume that the disks were precleared! That would be asking for trouble. Just do it over again. Actually, since I don't write the final bytes until the very end, if the disk tests as pre-cleared, it is highly likely it is. You can use preclear_disk -t /dev/sdX to test if it has a pre-clear signature without it writing to the disk at all. -t = Test if disk has pre-clear signature. This option may NOT be combined with the -c or -n options. The test does not write to the disk. It makes no changes to a disk at all. It only reads the first 512 bytes of the disk to verify a pre-clear signature exists. Note: "-t" does not read the entire disk to verify it it pre-cleared as that could take hours for a large disk. since the pre-clear-signature is written *after* a disk is entirely filled with zeros, if it exists, we assume the disk is cleared. Quote Link to comment
ShawnFumo Posted April 1, 2010 Share Posted April 1, 2010 This looks like a good time of night to post! Thanks guys.. Hmmm.. they do all say they are precleared using the -t flag. Quote Link to comment
purko Posted April 1, 2010 Share Posted April 1, 2010 And, don't assume that the disks were precleared! That would be asking for trouble. Just do it over again. Actually, since I don't write the final bytes until the very end, if the disk tests as pre-cleared, it is highly likely it is. Good point! I missed that. So, it is still: don't assume that the disks were precleared! Test them. Hmmm.. they do all say they are precleared using the -t flag. Then you're good to go. Get a SMART report on the disks, just to be safe. Quote Link to comment
Joe L. Posted April 1, 2010 Share Posted April 1, 2010 This looks like a good time of night to post! Thanks guys.. Hmmm.. they do all say they are precleared using the -t flag. As you said, the post-read probably did not finish, but you can basically do a crude equivalent by typing dd if=/dev/sdX bs=1M of=/dev/null Where sdX = your drive's device It will run for 4 or 5 hours and will not print statistics as it goes. If you wish to see how it is doing, in a different telnet session type killall dd -s USR1 That will signal the "dd" program to print the ongoing statistics in the first window. The "dd" will not verify it is reading all zeros, but it will read all the bytes on the disk. The goal of the post-read is to identify any blocks that were written in the zeroing that are unreadable. (indicating possible bad sectors) If the post-read marks a sector for possible re-allocation, that is good. (Good we identify it before putting real data on the disk) Joe L. Quote Link to comment
ShawnFumo Posted April 1, 2010 Share Posted April 1, 2010 Thanks purko and Joe. I'm running the dd command for the three drives right now (all in screen!). Will there be any way to know if it marks a sector for re-allocation? Quote Link to comment
Joe L. Posted April 1, 2010 Share Posted April 1, 2010 Thanks purko and Joe. I'm running the dd command for the three drives right now (all in screen!). Will there be any way to know if it marks a sector for re-allocation? You'll see it when you run a SMART report after they finish if the re-allocated sector count increases from the pre-clearing smart report, (or more likely,you will see the pending-re-allocation count increasing, since the actual re-allocation cannot occur until data it written to the bad blocks.) Joe L. Quote Link to comment
ShawnFumo Posted April 1, 2010 Share Posted April 1, 2010 No reallocated sectors on any of them or anything else that seems like a real error. There's tons of Hardware ECC Recovered, but it sounds like that is relatively normal for the larger drives these days. Looks like I'm golden. Thanks! Quote Link to comment
greybeard Posted April 1, 2010 Share Posted April 1, 2010 In the past I would "break in" new drives by running multiple erase/verify passes using a standalone utility. I would make 5 passes varying the bit pattern from X'00' to x'55' to x'aa' to x'ff' and finally another x'00'. Just thought I would suggest there might be some benifit to this instead of always using x'00'. I understand the the final pass of a multiple pass preclean would always have to use x'00' to leave the drive in proper condition for addition to the the array but that doesn't mean different patterns couldn't be used in earlier passes. I guess you would also only want to write the signature indicating the disk is clean after an x'00' pass and make sure the signature is destroyed at the beginning of a non x'00' pass. One other observation. I am wondering about is if the preread could be skipped on passes 2-n based on the assumption a verify read would have just finished from the previous pass. I wouldn't think doing two read passes in a row helps to achieve the desired objective and it sure would save a lot of time. Just a couple of thoughts to take or leave as you see fit. Either way, thanks for a great tool. PS: I am sure those bit patterns are not ideal because of the way the way data is encoded before being written to the drive. It would take a smarter person then me to figure out what patterens would really be best but I have got to think some varyation would be better than always using x'00'. Quote Link to comment
MrLeek Posted April 5, 2010 Share Posted April 5, 2010 Maybe I'm just being stupid (very good possibility!) but how do you run this? This is my first unraid build (everything is fine so far). I've got the preclear_disk.sh script on the usb stick and my limited knowledge of linux tells me that bash doesn't know where the script is located in order to run it. (I'm still reading as I'd like to solve this myself, but chances are it's a obvious solution to everyone but me!) Edit: something like cd /boot....... stupid welshman! It recognises the command now, but I need to specify the hard drives now Quote Link to comment
Joe L. Posted April 5, 2010 Share Posted April 5, 2010 The flash drive is mounted at /boot therefore, you most likely will find the script at /boot/preclear_disk.sh Log in on the system console, or via telnet as "root" Then type cd /boot Then type ls -l Odds are the preclear_disk.sh program is there. The just type preclear_disk.sh /dev/sdX where sdX = your disk drive device Joe L. Quote Link to comment
MrLeek Posted April 5, 2010 Share Posted April 5, 2010 Yep - just solved it! I was using /dev /sda (notice the space).... Got it running using Putty on the first HDD (which will be my parity drive). I'll create a second Putty instance (i think!) and do the same on the second HDD (data drive 1) Cheers for the quick response Joe! Quote Link to comment
Guzzi Posted April 5, 2010 Share Posted April 5, 2010 Hi Joe L., thnks for the feedback - preclear now has finished and this is final smart differences reported. I have attached syslog also, because there are smarterrors reported and post would become too long (there is 2 harddrives in syslog, cause I was running 2 preclears at the same time, one is a brandnew disk (sda), one is an older one (sdb) to reuse where I get those problems). ============================================================================ == == Disk /dev/sdb has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x000e 100 253 051 Old_age Always - 0 65c65 < 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 --- > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 71c71 < ATA Error Count: 156 (device log contains only the most recent five errors) --- > ATA Error Count: 174 (device log contains only the most recent five errors) 86c86 < Error 156 occurred at disk power-on lifetime: 7415 hours (308 days + 23 hours) --- > Error 174 occurred at disk power-on lifetime: 7416 hours (309 days + 0 hours) 97,101c97,101 So it seems the relocation was done - but I am worried about all those ata errors in syslog - I don't have any of those with "healthy" harddisks. What would you recommend? Running another preclear and see, if it's better now? Thanks for your help, Guzzi Ok, so I installed the drive and added to the array, copied data onto it, all without "obvious" errors - but since yesterday I can't copy anymore and get reiserfs-related errors. Even reading brings entries like this: Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS error (device md16): vs-5150 search_by_key: invalid format found in block 163348502. Fsck? Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS (device md16): Remounting filesystem read-only Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS error (device md16): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87 608 0x0 SD] Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-5150 search_by_key: invalid format found in block 163348502. Fsck? Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87 608 0x0 SD] Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-5150 search_by_key: invalid format found in block 163348502. Fsck? Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87 608 0x0 SD] Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: BMDMA2 stat 0x80d0009 Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: failed command: READ DMA EXT Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: cmd 25/00:00:17:71:ed/00:04:64:00:00/e0 tag 0 dma 524288 in Apr 5 18:14:09 XMS-GMI-02 kernel: res 51/04:3f:d8:72:ed/00:02:64:00:00/e0 Emask 0x1 (device error) Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: status: { DRDY ERR } Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: error: { ABRT } Apr 5 18:14:10 XMS-GMI-02 kernel: ata11.00: configured for UDMA/100 Apr 5 18:14:10 XMS-GMI-02 kernel: ata11: EH complete Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: BMDMA2 stat 0x80d0009 Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: failed command: READ DMA EXT Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: cmd 25/00:a0:47:60:59/00:02:04:00:00/e0 tag 0 dma 344064 in Apr 5 18:14:27 XMS-GMI-02 kernel: res 51/04:bf:28:62:59/00:00:04:00:00/e0 Emask 0x1 (device error) Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: status: { DRDY ERR } Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: error: { ABRT } Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: configured for UDMA/100 Apr 5 18:14:27 XMS-GMI-02 kernel: ata11: EH complete No parity errors shown and all drive errors in main page show "0" What should I do? Is the data lost? Should I remove the drive to get the data via the rest of the drives + parity? Quote Link to comment
Mopar_Mudder Posted April 7, 2010 Share Posted April 7, 2010 Just ran a Preclear on a disk and it has been a year or so since I did one. Could anyone take a quick look at the smart findings and see if their is anything to worry about? I will start to copy a bunch of data to the drive tonight. =========================================================================== = unRAID server Pre-Clear disk /dev/hda = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Elapsed Time: 15:35:43 ============================================================================ == == Disk /dev/hda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 11591 --- > 1 Raw_Read_Error_Rate 0x000f 120 100 006 Pre-fail Always - 243374677 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 65018 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 76213 63,66c63,66 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 < 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 < 190 Airflow_Temperature_Cel 0x0022 070 067 045 Old_age Always - 30 (Lifetime Min/Max 29/33) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 189 High_Fly_Writes 0x003a 096 096 000 Old_age Always - 4 > 190 Airflow_Temperature_Cel 0x0022 069 067 045 Old_age Always - 31 (Lifetime Min/Max 29/33) > 195 Hardware_ECC_Recovered 0x001a 066 061 000 Old_age Always 69,72c69,72 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 78683800862731 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2755 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 244491013324821 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2924575149 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1565195389 ============================================================================ Quote Link to comment
3560freak Posted April 11, 2010 Share Posted April 11, 2010 this is the first time I have run preclear and I am not 100% sure how to read this. Can anyone tell me if this is ok, thanks ============================================================================ == == Disk /dev/sda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 29 --- < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 30 Quote Link to comment
purko Posted April 11, 2010 Share Posted April 11, 2010 this is the first time I have run preclear and I am not 100% sure how to read this. Can anyone tell me if this is ok, thanks ============================================================================ == == Disk /dev/sda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 29 --- < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 30 http://lime-technology.com/forum/index.php?topic=4068.msg53785#msg53785 Quote Link to comment
3560freak Posted April 11, 2010 Share Posted April 11, 2010 awesome, I knew someone had to know more than me about this I guess the "Old Age" was just confusing, but thanks for the quick response. Quote Link to comment
Joe L. Posted April 14, 2010 Share Posted April 14, 2010 awesome, I knew someone had to know more than me about this I guess the "Old Age" was just confusing, but thanks for the quick response. The attribute "type" is one when it finally reaches its threshold, will be considered an old-age failure. In other words, after X load cycles the disk will have worn some physically, and the disk manufacturer will have considered the disk to have worn out, even if it is still perfectly working. I would expect a lot more head-load cycles before you have to worry about that specific parameter. Quote Link to comment
barrygordon Posted April 19, 2010 Share Posted April 19, 2010 I think I recall reading a request for statistics on preclear operations: The preclear finished after 24 hours 33 minutes. This was a full 1 cycle preclear (pre-read, clear, post-read) on a Hitachi 2 TB 7200 RPM drive connected to a mobo (Gigabyte GA-MA785GM-US2H) Sata port via a reverse SAS-SATA breakout cable. At the start of the pre-read cycle transfer rate was in the 120 mb/s range and at the end of the pre-read it was in the 64 mb/s range. I am assuming that is due to disk geometry (Anyone know?). The following messages appeared at the end of the preclear and I would appreciate it if someone could explain them to me: Smart error count differences detected after preclear Note, some raw values may change, but not an indication of a problem 19,20c19,20 Offline Data collection status: 0x80 Offline data collection activity was never started Offline data collection status: 0x84 offline data collection activity was suspended by an interrupting command from the host Quote Link to comment
Joe L. Posted April 19, 2010 Share Posted April 19, 2010 I think I recall reading a request for statistics on preclear operations: The preclear finished after 24 hours 33 minutes. This was a full 1 cycle preclear (pre-read, clear, post-read) on a Hitachi 2 TB 7200 RPM drive connected to a mobo (Gigabyte GA-MA785GM-US2H) Sata port via a reverse SAS-SATA breakout cable. At the start of the pre-read cycle transfer rate was in the 120 mb/s range and at the end of the pre-read it was in the 64 mb/s range. It is because less data can be stored on the inner cylinders than on the outer cylinders. The rotational speed is the same, therefore the rate at which you can read the outer cylinders will always be faster than the inner ones. I am assuming that is due to disk geometry (Anyone know?).Yes, it is the physical length of the tracks on the disks. outer ones are longer, with more data. Inner ones shorter, with less data. The following messages appeared at the end of the preclear and I would appreciate it if someone could explain them to me: Smart error count differences detected after preclear Note, some raw values may change, but not an indication of a problem 19,20c19,20 Offline Data collection status: 0x80 Offline data collection activity was never started Offline data collection status: 0x84 offline data collection activity was suspended by an interrupting command from the host The output is a "diff" between the starting SMART report and the ending SMART report. The full reports are in the syslog and also in individual files in the /tmp directory. The "offline data collection" is usually referred to as the "long" or "short" SMART test. Apparently, the disk was in the middle of one when the clearing operations started. Joe L. Quote Link to comment
barrygordon Posted April 19, 2010 Share Posted April 19, 2010 Joe, Thanks for the quick reply (as always) One last (Ha Ha) slightly off topic question. It appears that it takes about 8 hours to read a full 2 TB disk. If I do a parity sheck on an array with 1 parity disk and 2 data disks all disks being identical, should I expect a completion time (approximately) of 8*3=24 hours? Quote Link to comment
Joe L. Posted April 19, 2010 Share Posted April 19, 2010 Joe, Thanks for the quick reply (as always) One last (Ha Ha) slightly off topic question. It appears that it takes about 8 hours to read a full 2 TB disk. If I do a parity sheck on an array with 1 parity disk and 2 data disks all disks being identical, should I expect a completion time (approximately) of 8*3=24 hours? The time would typically be shorter. The disks are all read in parallel. Most people with modern SATA controllers and fast disks report parity check speeds between 65 and 95 MB/s, regardless of the number of disks involved, as long as they are not limited by PCI bus speeds. At an average of 75MB/s, to read 2TB (2000000 MB) = roughly 7.4 hours. Add in some time for the actual calculations and you should be in the 8 or 9 hours range. Joe L. Quote Link to comment
Mopar_Mudder Posted April 19, 2010 Share Posted April 19, 2010 Joe, Thanks for the quick reply (as always) One last (Ha Ha) slightly off topic question. It appears that it takes about 8 hours to read a full 2 TB disk. If I do a parity sheck on an array with 1 parity disk and 2 data disks all disks being identical, should I expect a completion time (approximately) of 8*3=24 hours? I don't think it works that way. I have 5 - 1.5TB drives (one it parity) and it takes about 8 hours for a parity check Quote Link to comment
barrygordon Posted April 19, 2010 Share Posted April 19, 2010 Good. That makes me feel much better! Quote Link to comment
Guzzi Posted April 19, 2010 Share Posted April 19, 2010 Hi Joe L., thnks for the feedback - preclear now has finished and this is final smart differences reported. I have attached syslog also, because there are smarterrors reported and post would become too long (there is 2 harddrives in syslog, cause I was running 2 preclears at the same time, one is a brandnew disk (sda), one is an older one (sdb) to reuse where I get those problems). ============================================================================ == == Disk /dev/sdb has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x000e 100 253 051 Old_age Always - 0 65c65 < 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 --- > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 71c71 < ATA Error Count: 156 (device log contains only the most recent five errors) --- > ATA Error Count: 174 (device log contains only the most recent five errors) 86c86 < Error 156 occurred at disk power-on lifetime: 7415 hours (308 days + 23 hours) --- > Error 174 occurred at disk power-on lifetime: 7416 hours (309 days + 0 hours) 97,101c97,101 So it seems the relocation was done - but I am worried about all those ata errors in syslog - I don't have any of those with "healthy" harddisks. What would you recommend? Running another preclear and see, if it's better now? Thanks for your help, Guzzi Ok, so I installed the drive and added to the array, copied data onto it, all without "obvious" errors - but since yesterday I can't copy anymore and get reiserfs-related errors. Even reading brings entries like this: Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS error (device md16): vs-5150 search_by_key: invalid format found in block 163348502. Fsck? Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS (device md16): Remounting filesystem read-only Apr 5 18:13:22 XMS-GMI-02 kernel: REISERFS error (device md16): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87 608 0x0 SD] Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-5150 search_by_key: invalid format found in block 163348502. Fsck? Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87 608 0x0 SD] Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-5150 search_by_key: invalid format found in block 163348502. Fsck? Apr 5 18:13:56 XMS-GMI-02 kernel: REISERFS error (device md16): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87 608 0x0 SD] Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: BMDMA2 stat 0x80d0009 Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: failed command: READ DMA EXT Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: cmd 25/00:00:17:71:ed/00:04:64:00:00/e0 tag 0 dma 524288 in Apr 5 18:14:09 XMS-GMI-02 kernel: res 51/04:3f:d8:72:ed/00:02:64:00:00/e0 Emask 0x1 (device error) Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: status: { DRDY ERR } Apr 5 18:14:09 XMS-GMI-02 kernel: ata11.00: error: { ABRT } Apr 5 18:14:10 XMS-GMI-02 kernel: ata11.00: configured for UDMA/100 Apr 5 18:14:10 XMS-GMI-02 kernel: ata11: EH complete Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: BMDMA2 stat 0x80d0009 Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: failed command: READ DMA EXT Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: cmd 25/00:a0:47:60:59/00:02:04:00:00/e0 tag 0 dma 344064 in Apr 5 18:14:27 XMS-GMI-02 kernel: res 51/04:bf:28:62:59/00:00:04:00:00/e0 Emask 0x1 (device error) Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: status: { DRDY ERR } Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: error: { ABRT } Apr 5 18:14:27 XMS-GMI-02 kernel: ata11.00: configured for UDMA/100 Apr 5 18:14:27 XMS-GMI-02 kernel: ata11: EH complete No parity errors shown and all drive errors in main page show "0" What should I do? Is the data lost? Should I remove the drive to get the data via the rest of the drives + parity? Sorry to bring this up again, but my box is sitting since to weeks in the corner and I hoped to get some good advices what to do best... If there is no comment, I will remove the drive and see, if this makes the situation better and do reiserfck on the drive and see, what happens ... Quote Link to comment
Joe L. Posted April 19, 2010 Share Posted April 19, 2010 Follow the instructions in the wiki: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems You have file-system corruption. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.