March 28, 201115 yr I've successfully per-cleared a WD 2TB EARS (unjumpered), stopped the array, assigned it to slot 5 (sde). As expected, the server tells me that a new disk was found, I click the box that "I'm sure I want to do this" (add to array), and then hit START. Nothing happens thereafter though, even after a few more refreshes and a few more attempts. None of the disks actually come online, and I have no clue as to why. I haven't even gotten as far as seeing the "Format" button. I'm attaching a syslog, and I'm also copying also the results from the pre-clear below. Not sure if rebooting the server would help, or anything... Anyone have any insight into this? It'd be much appreciated. Thanks! PS I had posted this in reply to another thread, and lionelhutz pointed out I'm getting errors on sde, which is the new drive in question. ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 64 = 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: 26:16:41 ========================================================================1.9 == WDC WD20EARS-00MVWB0 WD-WCAZA5534462 == Disk /dev/sde has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 123 120 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. syslog.txt
March 28, 201115 yr Author I'm also attaching a screenshot of the state I seem to be stuck in, for what it's worth.
March 28, 201115 yr Looks like it cannot write to /dev/sde (the new disk) to create the MBR on it. can you type the following and see what the partitioning looks like? fdisk -l -u /dev/sde Joe L.
March 28, 201115 yr Something is very odd with you system. First it is not the complete syslog, but perhaps only the last 1000 lines. Second, you precleared WD20EARS but "sde" from the partial syslog with a lots of errors is your old Seagate 1.5TB. You are sure that they are no cabling errors (it can happens to everyone).
March 28, 201115 yr Author @Joe L., I typed it via telnet, and nothing happens. @bcbgboy13, I'm attaching the entire syslog here now, I thought I'd only include what I thought was the relevant bits... Hm, weird, the whole thing with the Seagate (which, afaik, should be on sbd). Well you never know, maybe some cables did come loose - should I power down, you think, and check the connections, and reboot? sysloglong.rtf.txt
March 28, 201115 yr Author Alright, so the culprit was indeed a SATA cable that was ever so slightly off-axis - sometimes, it really is that simple. Funny though that it pre-cleared with no problems, because I didn't touch it since. Weird. Your mention of my (sdd) Seagate drive, what with the erros and such, could you take a quick peek at my new syslog to see if the matter is remedied? @Joe, here's the result of what you asked: Device Boot Start End Blocks Id System /dev/sde1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Thanks for your help! syslog_new.rtf_1.txt
Archived
This topic is now archived and is closed to further replies.