I am in the process of upgrading my motherboard. My current motherboard has 2 PATA and 2 SATA with a 4port SATA card. I am upgrading to a 1 PATA and 8 on-board SATA motherboard.

 

I currently have 4 PATA drives and 5 SATA hooked up and need to get rid of the two smallest (both PATA) because there is no room for them on the new motherboard. I have removed all of the data from the smallest drive and have disconnected it. UnRaid tells me I have a missing disk. How can I tell unraid I do not want to upgrade the disk so I can move on to removing the second PATA drive?

 

Thank you for the guidance!

I am in the process of upgrading my motherboard. My current motherboard has 2 PATA and 2 SATA with a 4port SATA card. I am upgrading to a 1 PATA and 8 on-board SATA motherboard.

 

I currently have 4 PATA drives and 5 SATA hooked up and need to get rid of the two smallest (both PATA) because there is no room for them on the new motherboard. I have removed all of the data from the smallest drive and have disconnected it. UnRaid tells me I have a missing disk. How can I tell unraid I do not want to upgrade the disk so I can move on to removing the second PATA drive?

 

Thank you for the guidance!

 

There are two ways to remove a disk.  The "official" way is easy to do but leaves the array unprotected for several hours while parity is rebuilt.  The "unofficial" way is a bit more involved but maintains parity protection throughout.  The unoffical way also results in the drive being removed  being completely blanked - suitable for sale but useless as a backup.

 

I am assuming you are doing this on the old hardware.  I am also assuming that you have copied the data off of the two disks you want to remove to a disk that will stay in the array.

 

First the "official" way.

1.  Perform a parity check.  Although technically optional, it is a very good idea to do this to ensure that the array is healthy.  You do not want to get any errors after the removal.

2.  Stop the array, go to the devices page and unassign the 2 disks that you want to remove (you can also move the other data disks to other slots if you want to, or even add new disks to the array if desired)

3.  Go to the main page, press the "restore" button (usually a very bad idea, but appropriate here).

4.  Start the array.

 

Your array will be unprotected while parity is built, but afterwards you will have accomplished your task.

 

The "unofficial" but safe way.

1.  Perform a parity check.  Not as critical here, but still recommended.

2.  Refer to this thread and follow the directions there (make sure you read the entire thread - you should increase the block size as Joe L. describes so the blanking process goes much quicker).  Note that you can clear both drives at the same time from 2 separate telnet sessions.

3.  Take your time.  Double and triple check that you have the right device names to clear.  Don't forget that you need to copy the data somewhere else before you blank the disks.  DO NOT TRY TO ADD ANY NEW DISKS TO THE ARRAY IN THE MIDDLE OF THIS PROCEDURE.

 

Post back with any questions.

I've posted a picture of where I am at. I have removed all of the data from disk5, stopped the server, removed the disk and restarted.

 

If I read you right, At this point I can go to devices and move disk8 to disk5 without losing any of the data on disk8. I will then press restore and after a parity check everything will be back to normal?

You would need to put disk5 back into the array to perform a parity check.  When was the last time you ran one?

 

Don't you have 2 disks that you need to remove?  Have you copied the data off of the other disk yet?

I've posted a picture of where I am at. I have removed all of the data from disk5, stopped the server, removed the disk and restarted.

 

If I read you right, At this point I can go to devices and move disk8 to disk5 without losing any of the data on disk8. I will then press restore and after a parity check everything will be back to normal?

You are correct in everything EXCEPT your terminology.

 

Yes, at this point, you can

Stop the array

Assign the Disk currently on Disk 8 to the Slot the Disk5 disk was in.

Press Restore.  This immediately invalidates any parity data previously computed.  It also sets a new initial configuration in the config/super.dat file (actually, it renames your old super.dat to super.old and creates a brand new file based on the current configuration of installed and working drives)  At this point, you have removed any knowledge of the old disk5, and have NO parity protection.

Start the array.  When you start the array you will not be doing a parity "check" but instead a full parity calculation.

 

Some number of hours later, depending on the speed of your array, you will again be protected against a disk failure.  Until this "initial" parity calculation is computed, you can lose data if a drive were to fail.

 

To repeat, once you press "Restore" to remove a drive and create a new supet.dat file holding the new superblock, you have NO parity protection until the full parity CALCULATION is performed...  It is not a "check" but a calculation.  You will see lots of "writes" to the parity disk, and "lots of reads" from all your other disks.

 

Joe L.

I've got it doing a full parity calculation with disk8 in the disk5 spot. Thank you guys for the help!

 

First the "official" way.

1.  Perform a parity check.  Although technically optional, it is a very good idea to do this to ensure that the array is healthy.  You do not want to get any errors after the removal.

2.  Stop the array, go to the devices page and unassign the 2 disks that you want to remove (you can also move the other data disks to other slots if you want to, or even add new disks to the array if desired)

3.  Go to the main page, press the "restore" button (usually a very bad idea, but appropriate here).

4.  Start the array.

 

Your array will be unprotected while parity is built, but afterwards you will have accomplished your task.

 

The "unofficial" but safe way.

1.  Perform a parity check.  Not as critical here, but still recommended.

2.  Refer to this thread and follow the directions there (make sure you read the entire thread - you should increase the block size as Joe L. describes so the blanking process goes much quicker).  Note that you can clear both drives at the same time from 2 separate telnet sessions.

3.  Take your time.  Double and triple check that you have the right device names to clear.  Don't forget that you need to copy the data somewhere else before you blank the disks.  DO NOT TRY TO ADD ANY NEW DISKS TO THE ARRAY IN THE MIDDLE OF THIS PROCEDURE.

Can this procedure also works if I am transfering my unRAID to a whole new system (new MB/CPU)?

Thanks!

 

First the "official" way.

1.  Perform a parity check.  Although technically optional, it is a very good idea to do this to ensure that the array is healthy.  You do not want to get any errors after the removal.

2.  Stop the array, go to the devices page and unassign the 2 disks that you want to remove (you can also move the other data disks to other slots if you want to, or even add new disks to the array if desired)

3.  Go to the main page, press the "restore" button (usually a very bad idea, but appropriate here).

4.  Start the array.

 

Your array will be unprotected while parity is built, but afterwards you will have accomplished your task.

 

The "unofficial" but safe way.

1.  Perform a parity check.  Not as critical here, but still recommended.

2.  Refer to this thread and follow the directions there (make sure you read the entire thread - you should increase the block size as Joe L. describes so the blanking process goes much quicker).  Note that you can clear both drives at the same time from 2 separate telnet sessions.

3.  Take your time.  Double and triple check that you have the right device names to clear.  Don't forget that you need to copy the data somewhere else before you blank the disks.  DO NOT TRY TO ADD ANY NEW DISKS TO THE ARRAY IN THE MIDDLE OF THIS PROCEDURE.

Can this procedure also works if I am transfering my unRAID to a whole new system (new MB/CPU)?

Thanks!

You need to ask a more specific question.

 

This procedure was to remove a disk permanently from the array.  Will you be removing a disk and not replacing it?

Or, will you be transferring all your disks to the new system?  (if so, all you need do is verify/assign the drives on the "devices" page to their correct slots in the array...and then press "Start")

Can this procedure also works if I am transfering my unRAID to a whole new system (new MB/CPU)?

Thanks!

 

The procedure I documented is useful in a few different situations:

1 - Removing of disks (doh!)

2 - Downsizing disks (replacing a disk with another disk that is smaller than the original) - (install new disk, copy data from original to new disk, remove the original disk)

3 - Upsizing disks the safe way (install new disk, copy data from original disk to new disk, remove the original disk)

 

The OP was asking about moving to a new MB/CPU - but the new MB did not have support for his 4 PATA drives.

@ Joe L & bjp999

 

Thanks for your responses.

 

To be clear - yes, I am transfering all my hard disk (all SATA) to a new Motherboard with a new CPU.

 

I guess it is straight forward then huh! Assign and verify that all my hard drive to the original order that I set then just hit "Start" OR I can do the "Restore" if I am changing the order of my hard disk, right?

 

Is performing parity check before and after necessary?

 

Thanks.

@ Joe L & bjp999

 

Thanks for your responses.

 

To be clear - yes, I am transfering all my hard disk (all SATA) to a new Motherboard with a new CPU.

 

I guess it is straight forward then huh! Assign and verify that all my hard drive to the original order that I set then just hit "Start" OR I can do the "Restore" if I am changing the order of my hard disk, right?

 

Is performing parity check before and after necessary?

 

Thanks.

The only disk that is critical to get assigned correctly is the parity drive. The others can be assigned t various devices as needed.

The array will not start if it does not have a valid array.  Just assign the drives on the devices page and press "Start"

 

You should NEVER press "Restore" unless are removing a disk from the array and are not going to replace it with another.   If you do press it you will be without parity protection until a full parity calculation is performed.

 

I would do a full parity check before and after... most important is to take a screen-shot before and after to ensure you have the disks in the correct order in the new MB.

 

Joe L.

@ Joe L.

 

Thank you - unRAID "Restore" is much clearer now. Whew...!

 

Wanted to clarify the disk order issue.

 

Parity calculations are not order dependent.  The disks can be in any order and parity will calculate correctly.  Obviously the parity disk needs to be in the parity slot.  But the data disks can be in any slot and parity will be maintained.

 

Some other configurations in the machine, however, ARE disk specific, especially in the user share configurations (e.g., include disks, exclude disks, etc.).  If you are using disk shares you likely have bat files or config files in other programs that reference specific disks by name (e.g., disk1, disk2).  If you are using the samba extra feature, you are coding specific disk names there.  So although the order is not important from a parity perspective, shuffling the disk order may create some less severe but nonetheless annoying problems.

 

Therefore I recommend maintaining the disk order.  If you don't know the disk order, however, just make sure that you put the parity disk in the parity slot and assign the other disks to the other slots.  You might have some configuration issues to straighten out, but your data will be protected.

@ Joe L.

 

Thank you - unRAID "Restore" is much clearer now. Whew...!

 

I've said this before, but it is worth saying once more.  The button labeled "Restore" is very poorly labeled.

 

At least one person tried to use the "Restore" button to "Restore" data to a failed disk they had replaced. Instead, it caused them to lose their data, as it wiped out their old parity and went about calculating parity based on their current configuration.  As far as I can remember, other than a multiple disk failure, or user-error in assigning a data disk to the parity slot, it is the only time an unRaid user lost data.

 

It is too easy for a user to incorrectly assume at the time of a failure that the "Restore" button is how to proceed, especially if English is not their native language:

A google search for the definition of "Restore" came back with these definitions:

# The process of replacing data from a backup taken previously.
www.titan.co.nz/Amigaak/AA050118.htm

# To brining data back into its original or former state. It is the opposite of archiving and deleting.
www.donaldfish.com/Articles/A101B.htm

# The process of retrieving files from a backup if the original files are lost or deleted.
www.uen.org/lessonplan/upload/6948-2-10837-Networking12.doc

 

All three of those definitions indicate data would be restored... not that a new disk configuration would be set.

 

As far as wording for the button...

I would prefer to see "Set Device Configuration" for the text on the button.   Some have suggested "Reset ..." but I don't like the label on the button starting with "reset" since you are almost always changing the configuration when pressing the button.  You are "setting" a configuration, not "resetting" it to a prior configuration.   This makes more sense to me since as far as I know, the "Restore" button is normally only needed to delete a physical disk on the devices page after un-assigning it from a logical slot on the unRaid array.   Its normal use is when removing a drive from the array where you do not intend to replace it immediately and want to compute a new set of parity values without the removed drive.   

 

The descriptive text to the right of the button should indicate something like:

"Set Device Configuration" should only be used after making a change on the devices page to un-assign a disk.   Pressing it will calculate parity when the array is started based on the remaining assigned and working data drives. Any previous parity data will be over-written.

 

Now, there is a procedure that involves the button currently labeled "Restore" that will cause parity to be trusted and not rebuilt, or to cause a different drive to be rebuilt, but it involves a command be entered at the telnet prompt before starting the array.  That procedure is described in the wiki as a "Trust My Parity" process.  It is very rarely needed...

 

Joe L.

@ Joe L & bjp999

 

Great stuff!

By reading all this informations I did understand a lot about parity & how it works and also the scary labeled "restore" button.

English is my second language and if I don't read enough on this forum I would probably hit that "restore" button few times already, hehehe! 

 

Windows users would and might actually hit that "restore" button if un-informed.

 

Thanks guys!