Fireball3 Posted November 20, 2013 Share Posted November 20, 2013 run another preclear From my understanding there should be no pending reallocations. My WD also started like this and ended up with a lot more bad sectors. The WD tool finally said "drive defective". Try the WD tool and run the extended test. Quote Link to comment
lumpumun Posted November 21, 2013 Share Posted November 21, 2013 thank you for your comment Fireball3. I did another preclear and now there are 2 sectors pending for allocation. The wd diagnostic tool is a good suggestion but is only windows and I do not have a windows computer where I can put the hdd in. So if others encounter this problem, there is also the same tool in a bootable cd format. Here is the download link: http://support.wdc.com/download/dlg/Diag504cCD.iso regards lumpumun Quote Link to comment
EdgarWallace Posted November 25, 2013 Share Posted November 25, 2013 I have precleared a drive that I was using earlier, before I replaced it with a 3TB drive. I pulled the 2TB drive off the server and used it as "cold" spare device. I haven't seen any issues from the preclear process (log attached) but the log is showing a massive amount of write errors when the server were starting the rebuild. The drive is now showing: DISK_DSBL What are my options? Quote Link to comment
Joe L. Posted November 26, 2013 Share Posted November 26, 2013 Your options are to determine WHY the writes failed. It could be anything from a bad/loose/intermittent cable/splitter/connector/drive-tray/back-plane to a bad/intermittent disk drive. Joe L. Quote Link to comment
RobJ Posted November 26, 2013 Share Posted November 26, 2013 I have precleared a drive that I was using earlier, before I replaced it with a 3TB drive. I pulled the 2TB drive off the server and used it as "cold" spare device. I haven't seen any issues from the preclear process (log attached) but the log is showing a massive amount of write errors when the server were starting the rebuild. The drive is now showing: DISK_DSBL What are my options? Well, the good news is the drive is probably fine, but unfortunately, there was a serious error in the interface between the drive and the system. My best guess is an issue with either the driver module or the SAS controller, but there does not appear to be any better info as to what the specific problem was. You started the rebuild at about 6:26pm, and less than 8 minutes later the SAS subsystem reported trouble. When it tried to hard reset the device for the drive, then the device stopped responding completely, and was disabled by the kernel, only 18 seconds after the problem first appeared. You can completely ignore all of the subsequent errors, as the drive was essentially not present once disabled, and the higher level write routines were not aware of that. Nov 25 18:25:59 Tower kernel: md: recovery thread rebuilding disk1 ... ... Nov 25 18:33:53 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 625:command active 00000019, slot [1]. Nov 25 18:33:53 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 625:command active 00000018, slot [2]. Nov 25 18:33:53 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1957:Release slot [4] tag[4], task [f2426800]: Nov 25 18:33:53 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 625:command active 00000018, slot [4]. Nov 25 18:33:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a Nov 25 18:33:53 Tower kernel: sd 0:0:6:0: [sdi] command f26e1840 timed out Nov 25 18:33:53 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1957:Release slot [3] tag[3], task [f2426400]: Nov 25 18:33:53 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 625:command active 00000008, slot [3]. Nov 25 18:33:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a Nov 25 18:33:53 Tower kernel: sd 0:0:6:0: [sdi] command f26e1000 timed out Nov 25 18:33:53 Tower kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2 Nov 25 18:33:53 Tower kernel: sas: ata7: end_device-0:6: cmd error handler Nov 25 18:33:53 Tower kernel: sas: ata1: end_device-0:0: dev error handler Nov 25 18:33:53 Tower kernel: sas: ata2: end_device-0:1: dev error handler Nov 25 18:33:53 Tower kernel: sas: ata3: end_device-0:2: dev error handler Nov 25 18:33:53 Tower kernel: sas: ata4: end_device-0:3: dev error handler Nov 25 18:33:53 Tower kernel: sas: ata5: end_device-0:4: dev error handler Nov 25 18:33:53 Tower kernel: sas: ata6: end_device-0:5: dev error handler Nov 25 18:33:53 Tower kernel: sas: ata7: end_device-0:6: dev error handler Nov 25 18:33:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a Nov 25 18:33:53 Tower kernel: ata7: failed to read log page 10h (errno=-5) Nov 25 18:33:53 Tower kernel: ata7.00: exception Emask 0x1 SAct 0xc SErr 0x0 action 0x6 Nov 25 18:33:53 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED Nov 25 18:33:53 Tower kernel: ata7.00: cmd 61/00:00:c8:78:b8/04:00:03:00:00/40 tag 2 ncq 524288 out Nov 25 18:33:53 Tower kernel: res 01/04:00:c8:7c:b8/00:00:03:00:00/40 Emask 0x3 (HSM violation) Nov 25 18:33:53 Tower kernel: ata7.00: status: { ERR } Nov 25 18:33:53 Tower kernel: ata7.00: error: { ABRT } Nov 25 18:33:53 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED Nov 25 18:33:53 Tower kernel: ata7.00: cmd 61/00:00:c8:7c:b8/04:00:03:00:00/40 tag 3 ncq 524288 out Nov 25 18:33:53 Tower kernel: res 01/04:00:c8:7c:b8/00:00:03:00:00/40 Emask 0x3 (HSM violation) Nov 25 18:33:53 Tower kernel: ata7.00: status: { ERR } Nov 25 18:33:53 Tower kernel: ata7.00: error: { ABRT } Nov 25 18:33:53 Tower kernel: ata7: hard resetting link Nov 25 18:33:53 Tower kernel: sas: ata8: end_device-0:7: dev error handler Nov 25 18:33:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a Nov 25 18:33:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a Nov 25 18:33:53 Tower kernel: ata7.00: both IDENTIFYs aborted, assuming NODEV Nov 25 18:33:53 Tower kernel: ata7.00: revalidation failed (errno=-2) Nov 25 18:33:54 Tower kernel: mvsas 0000:0b:00.0: Phy2 : No sig fis Nov 25 18:33:58 Tower kernel: ata7: hard resetting link Nov 25 18:34:04 Tower kernel: ata7.00: qc timeout (cmd 0xec) Nov 25 18:34:04 Tower kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x5) Nov 25 18:34:04 Tower kernel: ata7.00: revalidation failed (errno=-5) Nov 25 18:34:04 Tower kernel: ata7: hard resetting link Nov 25 18:34:04 Tower kernel: sas: sas_form_port: phy2 belongs to port6 already(1)! Nov 25 18:34:06 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[2]:rc= 0 Nov 25 18:34:11 Tower kernel: ata7.00: qc timeout (cmd 0x27) Nov 25 18:34:11 Tower kernel: ata7.00: failed to read native max address (err_mask=0x4) Nov 25 18:34:11 Tower kernel: ata7.00: HPA support seems broken, skipping HPA handling Nov 25 18:34:11 Tower kernel: ata7.00: revalidation failed (errno=-5) Nov 25 18:34:11 Tower kernel: ata7.00: disabled A side issue, of unknown significance, a possibly critical error was logged, probably related to the installation/initialization of the open_vm_tools package. I have no relevant expertise here, perhaps someone else can help? It may be harmless... Nov 25 18:23:42 Tower vmsvc[4133]: [ warning] [GLib-GObject] invalid (NULL) pointer instance Nov 25 18:23:42 Tower vmsvc[4133]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Quote Link to comment
EdgarWallace Posted November 26, 2013 Share Posted November 26, 2013 Joe & Rob, thanks a lot for your attention. I was trying to make sure that I read the information correctly - that the drive is basically ok but that the issue is the cabling or anything around it. [EDIT: It was indeed an issue with the cabling - to be more specific an issue with the Molex <--> SATA power adapter that I was using for that drive. Currently rebuilding and being at 50.6% readiness] Quote Link to comment
wolferl99 Posted December 3, 2013 Share Posted December 3, 2013 Hi All, just precleared a new seagate 4TB and wanted a second set of eyes on the report. root@Tower:/boot/preclear_reports# cat preclear_rpt_Z30066L1_2013-12-03 ========================================================================1.14 == invoked as: ./preclear_disk.sh -A /dev/sdf == ST4000VN000-1H4168 Z30066L1 == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 9:25:43 (117 MB/s) == Last Cycle's Zeroing time : 8:08:29 (136 MB/s) == Last Cycle's Post Read Time : 20:21:54 (54 MB/s) == Last Cycle's Total Time : 37:57:06 == == Total Elapsed Time 37:57:06 == == Disk Start Temperature: 35C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 113 6 ok 157046680 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 72 100 0 ok 28 Airflow_Temperature_Cel = 73 65 45 ok 27 Temperature_Celsius = 27 35 0 ok 27 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ root@Tower:/boot/preclear_reports# ================================================================== 1.14 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 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 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 37:57:06 ========================================================================1.14 == ST4000VN000-1H4168 Z30066L1 == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 113 6 ok 157046680 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 72 100 0 ok 28 Airflow_Temperature_Cel = 73 65 45 ok 27 Temperature_Celsius = 27 35 0 ok 27 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Tower:/boot# === START OF INFORMATION SECTION === Device Model: ST4000VN000-1H4168 Serial Number: Z30066L1 Firmware Version: SC43 User Capacity: 4,000,787,030,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 9 ATA Standard is: Not recognized. Minor revision code: 0x001f Local Time is: Tue Dec 3 07:50:41 2013 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 107) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x10bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 157084784 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 450558 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 40 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 072 072 000 Old_age Always - 28 190 Airflow_Temperature_Cel 0x0022 074 050 045 Old_age Always - 26 (Min/Max 25/36) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1 194 Temperature_Celsius 0x0022 026 050 000 Old_age Always - 26 (0 25 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 40 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. I think it looks great overall, the only two values I'm not too sure about are Raw_Read_Error_Rate & High_Fly_Writes. Anything you guys see you wouldn't like? Quote Link to comment
Joe L. Posted December 4, 2013 Share Posted December 4, 2013 everything looks great... enjoy your new drives. Quote Link to comment
squirrellydw Posted December 4, 2013 Share Posted December 4, 2013 running unraid 5.0.3 and getting ready to clear a new drive. Just want to make sure this is correct. I want to clear it 3 times. Drive is a WD Red, do I need to worry about aligning sector 64 or will I be fine with what I have below? cd /boot, preclear_disk.sh -c 3 /dev/xxx thanks Quote Link to comment
ryanth Posted December 5, 2013 Share Posted December 5, 2013 I'm running 3 pre-clear cycles on 2 drives I've added to my server. I can tell that both of them are still running because I'm getting emails about progress but I'm not sure how to check the results of the earlier cycles? I ran both the pre-clears through screen and haven't been able to reconnect to them. Can anyone point me towards instructions on how to recover the cycle reports? Quote Link to comment
Fireball3 Posted December 5, 2013 Share Posted December 5, 2013 Screen should still be running. Have you tried screen -r? But that won't show you the results of the passed cycles. To see them you have to look for the log files in /var/logs I think (not sure about the path). There are a couple of files for each cycle. Quote Link to comment
Joe L. Posted December 5, 2013 Share Posted December 5, 2013 running unraid 5.0.3 and getting ready to clear a new drive. Just want to make sure this is correct. I want to clear it 3 times. Drive is a WD Red, do I need to worry about aligning sector 64 or will I be fine with what I have below? We cannot tell. What version of the preclear script are you running? What size disk is being cleared? How do you have your preferred alignment setting set? (Settings->Disk Settings->Default partition format) Only by having those answers can your question be given an answer. Quote Link to comment
squirrellydw Posted December 5, 2013 Share Posted December 5, 2013 running unraid 5.0.3 and getting ready to clear a new drive. Just want to make sure this is correct. I want to clear it 3 times. Drive is a WD Red, do I need to worry about aligning sector 64 or will I be fine with what I have below? We cannot tell. What version of the preclear script are you running? 1.13. how do I update it if it's not the latest? What size disk is being cleared? 3TB How do you have your preferred alignment setting set? (Settings->Disk Settings->Default partition format) MBR 4K aligned Only by having those answers can your question be given an answer. Thanks for the help Quote Link to comment
Joe L. Posted December 5, 2013 Share Posted December 5, 2013 running unraid 5.0.3 and getting ready to clear a new drive. Just want to make sure this is correct. I want to clear it 3 times. Drive is a WD Red, do I need to worry about aligning sector 64 or will I be fine with what I have below? We cannot tell. What version of the preclear script are you running? 1.13. how do I update it if it's not the latest?Download and replace it with the newer version. (newest at this time=1.14) What size disk is being cleared? 3TB ALL disks > 2.2TB use GPT partitions. They are always properly aligned on a 4k boundary. The "-a" or "-A" options are silently ignored if used. How do you have your preferred alignment setting set? (Settings->Disk Settings->Default partition format) MBR 4K alignedThat setting is used if disks are <= 2.2TB in the absence of an overriding "-a" option to the preclear script. Only by having those answers can your question be given an answer. Thanks for the help You are welcome. Quote Link to comment
squirrellydw Posted December 6, 2013 Share Posted December 6, 2013 So once I upgrade to 1.14 this will work cd /boot, preclear_disk.sh -c 3 /dev/xxx thanks Quote Link to comment
Joe L. Posted December 6, 2013 Share Posted December 6, 2013 So once I upgrade to 1.14 this will work? Yes. Quote Link to comment
chaz4070 Posted December 9, 2013 Share Posted December 9, 2013 Hi everyone. Had a couple of 3TB Seagates that I got on sale last year that were in an enclosure for a bit. The enclosure failed so I'm claiming the drives for my unRaid. Ran the pre clear on the first with no issue... The second gives what I think are a rather large number of re-allocated sectors but it says everything passed. I only ran the one pass on it and am now in process of running a long SMART test but wanted to post the results here to see what you think. ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 118 6 ok 74683984 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 1 1 0 near_thresh 762 Airflow_Temperature_Cel = 56 60 45 In_the_past 44 Temperature_Celsius = 44 40 0 ok 44 No SMART attributes are FAILING_NOW 120 sectors were pending re-allocation before the start of the preclear. 64 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 8 sectors are pending re-allocation at the end of the preclear, a change of -112 in the number of sectors pending re-allocation. 34808 sectors had been re-allocated before the start of the preclear. 34808 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Is 34808 a lot for a 3TB? Cause for concern? Thanks for any insight you can provide. Quote Link to comment
Fireball3 Posted December 9, 2013 Share Posted December 9, 2013 Long SMART is OK. Save the report. I would run the preclear again to see if there are further changes in bad sectors. I've never seen so many reallocated sectors... What's the threshold value for reallocated sector count in the SMART report? If you're still in warranty period I would RMA the drive. Quote Link to comment
chaz4070 Posted December 9, 2013 Share Posted December 9, 2013 I was thinking the same thing. I have attached the long test results. Threshold of "36" and I have 34808. Now I need to find the enclosure I ripped this out of to see if I still have a warranty... Anybody ever played with Seagate's "SeaTools"? Not sure if I should run it before asking for a return. smart.txt Quote Link to comment
RobJ Posted December 10, 2013 Share Posted December 10, 2013 Threshold of "36" and I have 34808. '36' and '34808' aren't directly comparable, as 36 is essentially the scaled percentage of reallocatable sectors left, and 34808 is a count of the ones already used. The Value for Reallocated_Sector_Ct is 74, and that provides a rough way to calculate the number of available sectors. In this case, since 74 indicates that about a quarter of the total sectors have been used, you can multiply 34808 by 3 and determine that about 103,000 sectors remain. That should NOT however be a comfort, because 34808 is a rather high number, and indicates a high probability of something seriously wrong with the drive. All of the SMART numbers related to the mechanical condition of the drive look very good however. Uncorrectable sectors count (Reported_Uncorrect) looks rather high, but nothing like the Reallocated_Sector_Ct. The Preclear caused all of the suspicious sectors (Current_Pending_Sector) to be recovered, with none requiring remapping, but then found 8 more! That's a bad sign. The only 2 causes I can think of are (1) a large area with marginal magnetic media (weakly magnetized) or (2) a source of shorting (or other bad electrical noise) in the drive that is corrupting sectors. I personally would not trust this drive. You can Preclear it one more time, but I expect to see more instability in the Current_Pending_Sector count, and that is unacceptable. Anybody ever played with Seagate's "SeaTools"? Not sure if I should run it before asking for a return. It's a commonly run tool, and likely to be requested by Seagate reps, but (unless something has changed) requires the drive to be attached to a Windows machine. I doubt you can return this drive, outside of its enclosure. Quote Link to comment
Fireball3 Posted December 10, 2013 Share Posted December 10, 2013 I doubt you can return this drive, outside of its enclosure. He should try it. I read somewhere that people have been successful in doing so. Quote Link to comment
archedraft Posted December 10, 2013 Share Posted December 10, 2013 Does anyone know why this happens "SORRY: Disk /dev/sdb MBR could NOT be precleared" This disk is no longer shown in unMenu, Syslog now shows 0 lines in unMenu whereas before the preclear there was 2000? After a reboot I can see the hard drive again. I have attached a smart report but it looks OK to me. This is the second time it has happened. Also the motherboard is an ASUS P5N-e if that is relevant. eSilo login: root Password: Linux 3.9.6p-unRAID. root@eSilo:~# screen -r = 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 - Verifying if the MBR is cleared. DONE = Elapsed Time: 10:15:41 ========================================================================1.13 == == SORRY: Disk /dev/sdb MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0000000 0+0 records in 0+0 records out 0 bytes (0 B) copied, 3.2404e-05 s, 0.0 kB/s root@eSilo:/boot# EDIT: The PSU is an "areocool s620" which has 2 - 12V rails (also currently there are 2 - 8800gt graphics cards installed). Could this be a power issue? smart_sdb_131210_WD3TB.txt Quote Link to comment
Joe L. Posted December 11, 2013 Share Posted December 11, 2013 simple, apparently the disk stopped responding. The last "dd" showed 0 bytes read. Quote Link to comment
archedraft Posted December 11, 2013 Share Posted December 11, 2013 Any thoughts on why that happened? Quote Link to comment
Joe L. Posted December 11, 2013 Share Posted December 11, 2013 Any thoughts on why that happened? poor power, loose cable, defective drive? 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.