February 10, 201511 yr got it. any idea why i get these, though? root@unRAID:/boot# preclear_disk.sh -l -bash: preclear_disk.sh: command not found and root@unRAID:/boot# screen Cannot find terminfo entry for 'xterm-256color'. do i need to first install the preclear_disk.sh command somehow, and if so, how? and how do i get the screen command to work correctly? i guess there would be a screen emulator visible if it worked correctly? preclear script See if this thread helps with your MAC telnet client. Also, some hints on searching the forum. I say this because it can be puzzling if you're not familiar with the way this forum works.
February 10, 201511 yr Author ok, so now i get: root@unRAID:/boot# preclear_disk.sh -l ====================================1.15 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdj = ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T0056148 thank you! and yeah, anyone requiring 125 Replies (and counting) to get through a problem such as this, is certainly in a position to do a better job finding already existing info within this forum i'll try to figure out the terminal/telnet thing next...can't guarantee that i won't have more questions, but i'll try to get there on my own.
February 10, 201511 yr ok, so now i get: root@unRAID:/boot# preclear_disk.sh -l ====================================1.15 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdj = ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T0056148 thank you! and yeah, anyone requiring 125 Replies (and counting) to get through a problem such as this, is certainly in a position to do a better job finding already existing info within this forum i'll try to figure out the terminal/telnet thing next...can't guarantee that i won't have more questions, but i'll try to get there on my own. As I'm sure you know, some search results may not always be appropriate advise, so please don't hesitate to ask.
February 10, 201511 yr Author since that Telnet thread is from 2011 and the Nano package it links to (ftp://slackware.osuosl.org/pub/slackware/slackware-current/slackware/ap/nano-2.2.3-i486-1.txz) from a post from 2010, and the the link doesn't work anymore and was probably for an older Slackware package...the only one i could find with Google is to the one for Slackware v14.0...any ideas where i would find the correct Nano package for the current Slackware 13.37 implementation? i can only find text files that refer to it, but no working links.
February 10, 201511 yr since that Telnet thread is from 2011 and the Nano package it links to (ftp://slackware.osuosl.org/pub/slackware/slackware-current/slackware/ap/nano-2.2.3-i486-1.txz) from a post from 2010, and the the link doesn't work anymore and was probably for an older Slackware package...the only one i could find with Google is to the one for Slackware v14.0...any ideas where i would find the correct Nano package for the current Slackware 13.37 implementation? i can only find text files that refer to it, but no working links. Forget about nano, that was not the point I was trying to make with that thread. You just need to read the thread for some ideas about how to set up your telnet on either your MAC or on unRAID.
February 10, 201511 yr Author before i do the pre-clear with the -n option, as garycase suggested i could do to save some time, i want to make sure that this would be the right way to start...i do see a warning here, but don't quite know what to make of it: root@unRAID:~# cd /boot root@unRAID:/boot# preclear_disk.sh -l ====================================1.15 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdj = ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T0056148 root@unRAID:/boot# preclear_disk.sh -n /dev/sdj Pre-Clear unRAID Disk /dev/sdj ################################################################## 1.15 Model Family: Western Digital Red (AF) Device Model: WDC WD30EFRX-68AX9N0 Serial Number: WD-WMC1T0056148 LU WWN Device Id: 5 0014ee 058b2111d Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] WARNING: GPT (GUID Partition Table) detected on '/dev/sdj'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdj: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdj1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. ######################################################################## invoked as ./preclear_disk.sh -n /dev/sdj ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'):
February 10, 201511 yr The warning r.e. GPT is fine ... pre-clear will work fine with the disk. The important thing is to be CERTAIN that you're pre-clearing the correct disk Since it's only presenting you with one disk outside of the array, it's virtually certain that's the right one -- but just to be triple-sure I'd confirm that the serial number matches what you're expecting !! ... in fact, looking back at one of your early GUI posts, the serial # for Disk #13 matches what pre-clear is showing -- so you're good to go
February 11, 201511 yr Author and go, i did: ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdj = cycle 1 of 1, partition start on sector 1 = = 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 Temperature: 28C, Elapsed Time: 7:13:04 ========================================================================1.15 == WDCWD30EFRX-68AX9N0 WD-WMC1T0056148 == Disk /dev/sdj has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 122 120 0 ok 28 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 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@unRAID:/boot# now on to adding'er back into the array and copying the data back onto this disk...then, i should be back to where i started from many months ago. i'll report back again when this is truly done.
February 11, 201511 yr Author weeelllll, while copying the data from disk 13, which i backed up yesterday, back onto the newly pre-cleared and formatted disk 13, my Parity disk threw up this disturbing (mostly visually disturbing) message (see attached). Data is still copying back to Disk 13, slowly, very slowly, and will continue doing so for another "1 day 12 hours" (although that changes from 2 days 6 hours to 11 hours and everything in-between, constantly), so will let it finish that process, but when it is finished, i imagine that since i still haven't done the actual parity-check (i was still running on trusted parity), i'll have to do yet another parity-sync *and* then the parity-check, which i was going to do next, is that right? so i am looking at another 3 days of parity operations before i'll have a chance to be "back in the game"? since my ex-girlfriend, who is visiting me right now, simply shrugs this all off by reminding me that "Mercury is in retrograde", i really do wonder what voodoo forces are at work here! good grief!
February 11, 201511 yr I would post a syslog. At first glance I would think that writes to the parity disk are failing.
February 11, 201511 yr Author stupid question: the newest syslog on my flash is 4 days old...how do i go about retrieving one from today? also, the red alert boxes are now alternating with green ones...the red ones all say that the SMART test on Parity has failed, while the green ones all say that is has passed...they alternate, red, green, red, green, etc. ad nauseum.
February 11, 201511 yr Ouch !! You're definitely not having good luck with this system !! Writes to the parity disk aren't simply failing -- the disk has been disabled, so you have NO parity at this point. This means writes to that disk failed, so the system disabled it. The good news is it was the parity disk, so no data has been effected; the bad news is it means your system is not currently fault tolerant. I'd stop the writes to the new disk and resolve the issue with parity before proceeding, so the system will be protected. While it's possible you simply don't have the parity disk seated well in its cage, I suspect that the drive has actually failed and needs to be replaced. If you want to try just reseating it, do that -- then see if it passes SMART -- and if it passes SMART okay you can try doing a parity sync (which, if successful, should be followed by a parity check to confirm all is okay). Unfortunately there's no way to do these steps quickly ... so it's going to be another couple days at least before you've got this all put to bed !!
February 11, 201511 yr Author i just purchased this 4TB Red drive before i left to Germany, so it's unlikely (albeit not impossible, knowing WD) that the disk is bad...i won't be physically near the system until tomorrow and will check cabling and seating, and if worst comes to worst (being that WD doesn't honor USA purchased drives' warranty outside of the USA) i'll have to take the drive with me on my upcoming trip to San francisco and do a quick exchange then...but i hope it won't come to that. more tomorrow, for cryin' out loud! thanks, garycase...longest thread ever! (not quite, but getting there...)
February 11, 201511 yr Author can i stop the array and simply un-assign parity for now, remotely, just to keep the parity disk from being written to?
February 11, 201511 yr can i stop the array and simply un-assign parity for now, remotely, just to keep the parity disk from being written to? You could stop the array and do a New Config -- assigning all of the data drives, but no parity drive; then Start the array and continue writing your data to #13. In fact, those writes would be very fast, as they'd be at full disk speed with no parity computation overhead.
February 11, 201511 yr ... i just purchased this 4TB Red drive before i left to Germany, so it's unlikely (albeit not impossible, knowing WD) that the disk is bad ... Don't blame WD exclusively for that possibility. Drives from all manufacturers will suffer from what is called 'infant morality'. (Google "bathtub curve Failure rate" for more information.) That is one of the reasons why many of us run three cycles of the preclear script in an attempt to weed-out those early failures before we put them into a server. The hours required for that many preclear cycles will find many of those disks that are going to fail early so that we don't have to deal with the issue of a failure soon after installation. Most of the time, once a disk gets past that point, the probability is very high that will will not fail for at least a couple of years.
February 11, 201511 yr Author i do see your point, Frank1940...maybe i will start that practice as well soon...heck, when i go in tomorrow and find that reseating the drive and replugging the SATA cable will bring it back online, i may just try to do a full pre-clear on it...if it fails, i'll take it with me to Cali on the 25th and arrange for a drop-ship replacement from WD before i get there...wish they honored their warranties internationally!
February 11, 201511 yr i do see your point, Frank1940...maybe i will start that practice as well soon...heck, when i go in tomorrow and find that reseating the drive and replugging the SATA cable will bring it back online, i may just try to do a full pre-clear on it...if it fails, i'll take it with me to Cali on the 25th and arrange for a drop-ship replacement from WD before i get there...wish they honored their warranties internationally! If you can access the drive, take a look at the SMART report first. If Parameters with ID# 5, 196, 197 or 198 are non-zero that indicates a (potential) problem with the drive. Perhaps not enough to warrant not trying to use that drive but a need to further evaluate it. As I understand it, if parameter ID# 199 is non-zero that indicates that the problem was external to the drive and that the drive is most likely good.
February 11, 201511 yr Yes, #199 is a data transfer error -- most likely a cable or connector issue external to the drive. Non-zero values for #5 (Reallocated Sector count) and #196 (Reallocation Events) aren't necessarily bad ... in fact, modern drives are DESIGNED to automatically reallocated defective sectors [Old-timers will remember when drives came with defector sector maps on the drive that you had to manually enter into the drivers so they'd be avoided]. A non-zero #197 (Pending Reallocations) isn't good however -- that means they've been noted as bad but not yet reallocated ... which generally means they contain data so they can't simply be re-mapped. I immediately replace drives that have non-zero pending counts.
February 12, 201511 yr Author i went in today to re-seat Disk 15 (Parity) and check the cabling...after i rebooted the server i did a new config and assigned all disks but parity, then did a pre-clear - n on the parity disk...i just didn't wanna do the full pre-clear cycle at this point, but will do it if i run into another issue with disk 15...the results of the pre-clear that just finished are this: Disk Temperature: 28C, Elapsed Time: 9:46:11 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdp = cycle 1 of 1, partition start on sector 1 = = 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 Temperature: 28C, Elapsed Time: 9:46:17 ========================================================================1.15 == WDCWD40EFRX-68WT0N0 WD-WCC4EM0WNZKU == Disk /dev/sdp has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdp /tmp/smart_finish_sdp ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 123 0 ok 28 No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 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, a change of -1 in the number of sectors pending re-allocation. 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@unRAID:/boot# so what's the best way to go about getting back the SMART data you wanted me to double-check? is the Dynamix WebGUI's read-out of SMART values capable of displaying them? is it enough to just add the disk back in while the array is stopped or do i need to do another New Config just to get the correct SMART values?
February 12, 201511 yr Author garycase, when you said A non-zero #197 (Pending Reallocations) isn't good however -- that means they've been noted as bad but not yet reallocated ... which generally means they contain data so they can't simply be re-mapped. I immediately replace drives that have non-zero pending counts. you were referring to the very error the pre-clear found when it said 1 sector was pending re-allocation before the start of the preclear., right? so if i were you, i'd give up on this drive, if i understood you correctly, and send it in for replacement, right?
February 12, 201511 yr garycase, when you said A non-zero #197 (Pending Reallocations) isn't good however -- that means they've been noted as bad but not yet reallocated ... which generally means they contain data so they can't simply be re-mapped. I immediately replace drives that have non-zero pending counts. you were referring to the very error the pre-clear found when it said 1 sector was pending re-allocation before the start of the preclear., right? so if i were you, i'd give up on this drive, if i understood you correctly, and send it in for replacement, right? What I would do, if it were my server, is to set this drive aside for now. (You said you had purchased it in the USA and are now in Europe so getting warranty service on it is going to be a hassle in any case.) I would get a new drive and run three preclear cycles on it (personal preference!). If it clears the preclear tests, install it as the new parity drive. I would want to get my array protected as soon as possible. I would run another couple of Preclear cycles on THIS drive and see if all of these parameters remain at zero. I know it takes a long time to run these tests but that will tell the tale on this drive. I believe Parameter #198 is the real killer. The data in those sectors is unreadable and, hence, that fact will prevent data rebuild on another disk. I believe Parameter 197 means that the data reads are flaky and there is a real possibility that the next time an attempt is made to read those sectors, the data may not be recoverable. (Basically, there are some sectors that can not be read directly but through the drive's data recovery logarithm, the data can be reconstructed.) Also, someone has worked on a script which tests drives much more completely than the standard preclear script does. Basically, it uses a more complicated pattern of ones-and-zeros to verify that the disk is performing properly. AT this point, I can't remember who it was or what the name of the script was to do the job. (It will probably come to me about 4 o'clock in the morning! ) It also probably requires a much longer time to run a full cycle on the drive! Don't worry about getting warranty service on a drive. I have never heard of anyone getting turned down! On the drives that I have sent in, the replacements were shipped within a couple of days, so I know they never really looked at the drive except to verify that it was still in warranty.
February 13, 201511 yr Author i'm not worried about the warranty exchange, as i've been though that with them so many times by now that i know that it's as easy as the click of a "Submit" button on their website. my problem, embarrassingly enough, has been that i just haven't had enough work lately and that after this move back to Berlin every $20 bill is real money to me...the suitcase with the server that my ex-girlfriend brought over with her cost me almost $300 in extra/overweight luggage fees, replacing the broken drive cages another $500, and i just bit the bullet and tracked down a replacement WD 4TB Red drive near Alexanderplatz, which i dropped into my server on my way back home and started the full preclear_disk...so, it's a money thing, more than anything else. but enough whining...i appreciate the help i'm getting here and don't wanna be "that stubborn guy" that refuses to heed the advice that is given to him...of course, drive 12 threw up a red flag after i stopped the array, but after rebooting the server it looked fine again...after i get the other 4TB drive replaced, i guess that old 2TB disk 12 WD Green drive (the oldest in the array, from before they even had green labels) will get replaced with it. phew...what a freakin' ride! i'll report back with the results of that preclear...in 2 or 3 days, i guess :-/
February 13, 201511 yr ... phew...what a freakin' ride! i'll report back with the results of that preclear...in 2 or 3 days, i guess :-/ Yes, clearly you've had a stressful 3 weeks or so with this thread. In addition to the problems with your server, I also noticed the following ... ...my girlfriend arrived at Berlin airport from San Francisco last night ... and ...the suitcase with the server that my ex-girlfriend brought over ... The subtle change [from "girlfriend" to "ex-girlfriend"] has probably also caused a bit of stress But things will all work out. While you've been dealing with this, I had to cancel a long-planned month-long vacation to Australia and New Zealand we were supposed to go on starting next week because my wife fell in the shower and fractured her vertebrae 2 weeks ago. A couple of disk cages and a new hard drive are pretty trivial compared to issues like that ... as you very well know with the even more major medical issues you've dealt with.
February 13, 201511 yr Author i am *so* sorry to hear about that, garycase! surely nothing with our technology and the troubles that come along with it will ever be as deep-reaching as our health and that of our loves ones...i hope that she will be on her feet again as soon as humanly possible and that you will have that adventure together soon after that! oh man, that must have been a shock to both of you...i don't know what to say about such things...some people say everything happens for a reason, but i believe sometimes things just happen for no reason at all...i know better people than me have died from lesser cancers than mine, and worse people than your wife have not slipped in the shower...it simply isn't fair sometimes what happens to us, but it's in how we deal with it that makes us the people we are. please extend you well wishes to your wife, and may she heal quickly and well! funny you mentioned the "girlfriend"/"ex-girlfriend" thing...Emma (is her name) and i have been by each others sides for 8 years and counting, and through thick and thin we've become best friends...she is my best friend who is a "girl", who used to be my girlfriend, in the sense that most people define such things, but we will always be the "Tillemma" that we are...so no, nothing on that end has been a cause of stress...it boils down to re-immigrating to my native Germany in the middle of winter, after 30 years in the California sun and amongst the easy-going nature of "West Coast folk" and the easy-going San Francisco/Bay Area lifestyle...the expense of moving, the lack of work while new (again) here, technology problems every day, etc...like i said, i'm healthy (save for a pesky cold that won't let go) and have a roof over my head and food in the fridge and a great woman to laugh with, so all is well. but i do think about throwing that server with 30 years worth of my digital life in it out the window every single day...that's all. thanks for being part of keeping me from doing that be well, and give your wife a big hug from a stranger that feels for her and your pain!
Archived
This topic is now archived and is closed to further replies.