unRAID Server Pro

version: 5.0-rc5

 

So I picked up a 3TB drive, popped it in, ran the pre-clear, and went to add it to the array.

 

Here is where I either screwed up or am just confused; I thought the point of the pre-clear was to stop the array from having to be off-line while the new disk clears.

 

What's happened is, I went to the web interface, stopped the array, added the disk, and told it to start.

 

Now it seems to be clearing again.

 

Am I adding disks incorrectly or misunderstanding? 

 

 

From my understanding preclear will place an I'd string on the drive after all it's test, that tell unraid the drive is ready to go. This tells unraid it doesn't have to format the drive when added to the array. Saving all the down time from the array being down while adding a disk. Ian be wrong on this but from what I can remember you will still experience some down time while the drive is added to the array. But it shouldn't be too long. I think when I last added a drive my array was back up and running within 10 minutes max.  If your array has been unresponsive for longer then I'd said post a syslog and someone with more experience will need to take a look at it.

It's been down for about 1.5 hours now.

 

It doesn't respond to any http requests (and hasn't since I hit "Start").

 

I'm hesitant to do a cold shutdown though.

One of the mods may be able to give you better advice. Can you telnet via putty into unraid?  It may be the GUI has crashed. In which case a hard reset might be your only option. I would wait to see if someone else has a thought first.

 

 

It may be that the preclear script didn't finish correctly and the array is formatting the drive. In which case depending on the size it may take a while. Though the manaent page should come up and say the drive was currently being reformatted.

If you do have to reset, run preclear script with -t flag to test the drive for the flag. Ive been preclearing the same 3TB drive for weeks because of random issues. Takes forever to begin with under ideal conditions so I am hopeful you dont have to re-preclear

I'm able to telnet into the server. Not sure what that can tell me.

 

How can I re-open the screen session I had running for the pre-clear? I don't think I ever shut it down.

 

I'll leave it for tonight and see what it's like in the morning or after work.

If you are using screen, then you can run screen -r to reattach to the screen session

Did you keep the telnet session running pre-clear open until it finished? It sounds like pre-clear didn't complete and unRAID is clearing the drive. It will take around 12 hours to complete. The sever will be unavailable until it completes.

I did keep the telnet session running. And I used screen. Here is what it output BEFORE I stopped the array and added the new disk:

================================================================== 1.12

=                unRAID server Pre-Clear disk /dev/sdf

=              cycle 1 of 1, partition start on sector 63

= 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: 30C, Elapsed Time:  24:40:58

========================================================================1.12

==  ST3000DM001-1CH166    Z1F19W8V

== Disk /dev/sdf has been successfully precleared

== with a starting sector of 63

============================================================================

** 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 =  114    100            6        ok          68391280

        Spin_Retry_Count =  100    100          97        near_thresh 0

        End-to-End_Error =  100    100          99        near_thresh 0

          High_Fly_Writes =    98    100            0        ok          2

  Airflow_Temperature_Cel =    70      72          45        near_thresh 30

      Temperature_Celsius =    30      28            0        ok          30

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# send-mail: Authorization failed (535 5.7.1 http://support.google.com/mail/bin/answer.py?answer=14257 fh6sm7883627qab.19)

 

Obviously the mail failed, but that shouldn't be an issue.

 

The drive did finish the clear in about 12 hours, and it is formatting now (I told it to do so when I woke up). But I'm still not sure what I did wrong.

Grrr...

 

And now I'm getting permission errors on a bunch of the folders I'm trying to access on the array.

 

 

I really hope I didn't mess up so bad as to lose some of this data.

So checking further, when I browse from another machine on the network, it would seem that on Disk 3, I can see the folder structure for the most part, but I encounter the above error whenever I try digging down into the directory structure.

 

Any idea what's going on? Please please please tell me this data is still there or that I can recover it.

 

I can't logically think of anything that I did that would have messed this up.

 

Here's what I did since getting the new drive:

1. Insert new drive.

2. Telnet in via Putty and run the pre-clear (the full array was available up to this point and I was accessing data on the disk that is now giving me trouble)

3. When the pre-clear completed, I logged in via a web browser and stopped the array.

4. Selected the new disk (sdf) and assigned it to the next spot in the array.

5. Started it up again (this is where it started to do the unexpected clear).

6. When clear had completed (~12 hours later), I formatted the new drive and brought the array on-line.

 

That's where I am now.

 

EDIT: Just about to head to work, figured I'd check one more thing, when I browse through the UnRAID UI in a browser, it LOOKS like the data is still there... so it seems to be a permission error only (hopefully). I just have no idea what I've done...

if it is a permissions problem, run the newperms script in the unraid webgui.

or via telnet

newperms /mnt/user/SHARE_YOU_WANT_TO_CORRECT

 

this can take a while

if it is a permissions problem, run the newperms script in the unraid webgui.

or via telnet

newperms /mnt/user/SHARE_YOU_WANT_TO_CORRECT

 

this can take a while

 

I'll hit that when I get home this evening, Benni-Chan. Thanks.

 

Any further thoughts on what went wrong with the pre-clear?

It appears you used version 1.12 of the preclear script. You have to use version 1.13 to properly tag a 3T drive. You can also look at how it says it was setting up the MBR, which is wrong since a MBR isn't used on 3T drives. I believe the older version will do the read-write-read correctly so the drive did get the burn-in test but you're now just going to have to wait for unRAID to clear it again.

 

It appears you used version 1.12 of the preclear script. You have to use version 1.13 to properly tag a 3T drive. You can also look at how it says it was setting up the MBR, which is wrong since a MBR isn't used on 3T drives. I believe the older version will do the read-write-read correctly so the drive did get the burn-in test but you're now just going to have to wait for unRAID to clear it again.

 

Excellent. That makes sense. It's finished and in the array now. I'll confirm that it's working when I get home.

 

Forgive my ignorance, but with a script like that, do I just need to download the new script and overwrite the old one? I'm not much of a Linux guy, so I'll have to muddle through how to do that.

yes, just replace the old version with the new one.

it could be, that the script needs execution permissions after you replaced it.

in that case just run

chmod 777 preclear_disk.sh

inside the directory you've downloaded the script to.

Thanks, everybody.

 

Both issues fixed.

 

Recap:

1. Disks larger than 2.2 TB need preclear_disk.sh 1.13 or higher.

2. Run "New Permissions" util from GUI to fix permission errors.