Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

first hard drive swap with 4.5.4 any suggestions?

Featured Replies

I need to swap one of my hd's and running 4.5.4 with unmenu and all latest patches.  Given this is kind of a new version and the recent format issues, I just wanted to ask if there is anything I should look out for or do first.  My plan is this,

 

Run a parity check

power down

swap the drive - replacing a good 1tb drive with a 2tb drive for more space and the 1tb drive is very old.

power up

then????    -  I assume unraid will auto rebuild with parity, but do I need to do anything or is this all automatic with this version?

 

last, toss the 1tb drive in the trash....LOL

 

Thanks!

I need to swap one of my hd's and running 4.5.4 with unmenu and all latest patches.  Given this is kind of a new version and the recent format issues, I just wanted to ask if there is anything I should look out for or do first.  My plan is this,

 

Run a parity check

power down

swap the drive - replacing a good 1tb drive with a 2tb drive for more space and the 1tb drive is very old.

power up

then????    -  I assume unraid will auto rebuild with parity, but do I need to do anything or is this all automatic with this version?

 

last, toss the 1tb drive in the trash....LOL

 

Thanks!

Assuming your parity drive is a 2TB one already, that is it.

 

After you power up you'll probably need to press "Start" to begin the re-construction onto the replacement disk.

 

Also, before you install the new drive in place of the old, you might want to physically install it and run the preclear_disk.sh script on it before you assign it to your array.  This will not do anything for the re-construction, but it will exercise the drive for about 30 hours and give you some confidence that the drive will not die an early death from some mechanical issue.

 

Joe L.

  • Author

Thanks Joe!

 

Yup, installed a 2tb parity drive a while back so I'm good there.  Thanks for the suggestion on running the preclear.  I will either do that, or just save the old 1tb drive for a week or two, as it is still working and it will still have my data on it.

 

I do have another question for you.  I have 4 of these 1tb drives, all about 4 years old.  I got these when they first came out.  Being they have been in a NAS and now my unraid server, they have been powered on all the time.  The result is I'm now getting Smart alerts on all 4 drives that says

GTG000PAG051KC: WARNING - Power_On_Hours it is now 21892 (warning threshold is 20000)

So I'm proactively swapping them out one at a time, mainly due to lack of funds.  My question is which one should be swapped first, then second, and so on.  In looking at the other Smart data, I can't really tell which drive should go first.  I do notice that when the system is doing a Parity Check, some of the drives really get hot, but that is the only time they do so I've not worried about it too much.  Can you please take a look at this data and let me know if you see any red flags, and then specifically the 4 Hitachi 1tb drives, what order would you swap them out?

 

Here is my SMART data, hope it's ok to post all of this stuff here... ;D

 

STARTED, 9 disks in array.    Parity is Valid:.  Last parity check 13 days ago with no sync errors.    6QF1MPC3: OK - ATA_Error_Count is 0

6QF1MPC3: OK - Raw_Read_Error_Rate is 144170345

6QF1MPC3: OK - Spin_Up_Time is 0

6QF1MPC3: OK - Start_Stop_Count is 829

6QF1MPC3: OK - Spin_Retry_Count is 0

6QF1MPC3: OK - Power_Cycle_Count is 22

6QF1MPC3: OK - Reallocated_Sector_Ct is 0

6QF1MPC3: OK - Seek_Error_Rate is 211459669

6QF1MPC3: OK - Temperature_Celsius is 35 (0 22 0 0)

6QF1MPC3: OK - Current_Pending_Sector is 0

6QF1MPC3: OK - Power_On_Hours is 5163

6QF1MPC3: OK - Offline_Uncorrectable is 0

6QF1MPC3: OK - UDMA_CRC_Error_Count is 0

6QF1MPC3: OK - Multi_Zone_Error_Rate is 0

Disk 8: OK - ATA_Error_Count is 0

Disk 8: OK - Raw_Read_Error_Rate is 189974401

Disk 8: OK - Spin_Up_Time is 0

Disk 8: OK - Start_Stop_Count is 875

Disk 8: OK - Spin_Retry_Count is 15

Disk 8: OK - Power_Cycle_Count is 21

Disk 8: OK - Reallocated_Sector_Ct is 0

Disk 8: OK - Seek_Error_Rate is 47365005

Disk 8: OK - Temperature_Celsius is 31 (0 19 0 0)

Disk 8: OK - Current_Pending_Sector is 0

Disk 8: OK - Power_On_Hours is 11175

Disk 8: OK - Offline_Uncorrectable is 0

Disk 8: OK - UDMA_CRC_Error_Count is 0

S13PJ9BQ920079: OK - ATA_Error_Count is 0

S13PJ9BQ920079: OK - Raw_Read_Error_Rate is 0

S13PJ9BQ920079: OK - Spin_Up_Time is 8180

S13PJ9BQ920079: OK - Start_Stop_Count is 1103

S13PJ9BQ920079: OK - Spin_Retry_Count is 0

S13PJ9BQ920079: OK - Calibration_Retry_Count is 1

S13PJ9BQ920079: OK - Power_Cycle_Count is 26

S13PJ9BQ920079: OK - Reallocated_Sector_Ct is 0

S13PJ9BQ920079: OK - Seek_Error_Rate is 0

S13PJ9BQ920079: OK - Temperature_Celsius is 25 (Lifetime Min/Max 21/30)

S13PJ9BQ920079: OK - Reallocated_Event_Count is 0

S13PJ9BQ920079: OK - Current_Pending_Sector is 0

S13PJ9BQ920079: OK - Power_On_Hours is 9856

S13PJ9BQ920079: OK - Offline_Uncorrectable is 0

S13PJ9BQ920079: OK - UDMA_CRC_Error_Count is 0

S13PJ9BQ920079: OK - Multi_Zone_Error_Rate is 0

S13PJ9AQ908010: OK - ATA_Error_Count is 0

S13PJ9AQ908010: OK - Raw_Read_Error_Rate is 0

S13PJ9AQ908010: OK - Spin_Up_Time is 7960

S13PJ9AQ908010: OK - Start_Stop_Count is 1035

S13PJ9AQ908010: OK - Spin_Retry_Count is 0

S13PJ9AQ908010: OK - Calibration_Retry_Count is 0

S13PJ9AQ908010: OK - Power_Cycle_Count is 26

S13PJ9AQ908010: OK - Reallocated_Sector_Ct is 0

S13PJ9AQ908010: OK - Seek_Error_Rate is 0

S13PJ9AQ908010: OK - Temperature_Celsius is 24 (Lifetime Min/Max 20/29)

S13PJ9AQ908010: OK - Reallocated_Event_Count is 0

S13PJ9AQ908010: OK - Current_Pending_Sector is 0

S13PJ9AQ908010: OK - Power_On_Hours is 9233

S13PJ9AQ908010: OK - Offline_Uncorrectable is 0

S13PJ9AQ908010: OK - UDMA_CRC_Error_Count is 0

S13PJ9AQ908010: OK - Multi_Zone_Error_Rate is 0

GTG000PAG051KC: OK - ATA_Error_Count is 0

GTG000PAG051KC: OK - Raw_Read_Error_Rate is 0

GTG000PAG051KC: OK - Spin_Up_Time is 546 (Average 665)

GTG000PAG051KC: OK - Start_Stop_Count is 1136

GTG000PAG051KC: OK - Spin_Retry_Count is 0

GTG000PAG051KC: OK - Power_Cycle_Count is 55

GTG000PAG051KC: OK - Reallocated_Sector_Ct is 0

GTG000PAG051KC: OK - Seek_Error_Rate is 0

GTG000PAG051KC: OK - Temperature_Celsius is 34 (Lifetime Min/Max 20/53)

GTG000PAG051KC: OK - Reallocated_Event_Count is 0

GTG000PAG051KC: OK - Current_Pending_Sector is 0

GTG000PAG051KC: WARNING - Power_On_Hours it is now 21892 (warning threshold is 20000)

GTG000PAG051KC: OK - Offline_Uncorrectable is 0

GTG000PAG051KC: OK - UDMA_CRC_Error_Count is 0

GTG000PAG18NNC: OK - ATA_Error_Count is 0

GTG000PAG18NNC: OK - Raw_Read_Error_Rate is 0

GTG000PAG18NNC: OK - Spin_Up_Time is 672 (Average 672)

GTG000PAG18NNC: OK - Start_Stop_Count is 1157

GTG000PAG18NNC: OK - Spin_Retry_Count is 0

GTG000PAG18NNC: OK - Power_Cycle_Count is 55

GTG000PAG18NNC: OK - Reallocated_Sector_Ct is 0

GTG000PAG18NNC: OK - Seek_Error_Rate is 0

GTG000PAG18NNC: OK - Temperature_Celsius is 34 (Lifetime Min/Max 20/54)

GTG000PAG18NNC: OK - Reallocated_Event_Count is 0

GTG000PAG18NNC: OK - Current_Pending_Sector is 0

GTG000PAG18NNC: WARNING - Power_On_Hours it is now 21895 (warning threshold is 20000)

GTG000PAG18NNC: OK - Offline_Uncorrectable is 0

GTG000PAG18NNC: OK - UDMA_CRC_Error_Count is 0

GTG000PAG19J7C: OK - ATA_Error_Count is 0

GTG000PAG19J7C: OK - Raw_Read_Error_Rate is 0

GTG000PAG19J7C: OK - Spin_Up_Time is 692 (Average 693)

GTG000PAG19J7C: OK - Start_Stop_Count is 1169

GTG000PAG19J7C: OK - Spin_Retry_Count is 0

GTG000PAG19J7C: OK - Power_Cycle_Count is 55

GTG000PAG19J7C: OK - Reallocated_Sector_Ct is 0

GTG000PAG19J7C: OK - Seek_Error_Rate is 0

GTG000PAG19J7C: OK - Temperature_Celsius is 35 (Lifetime Min/Max 21/58)

GTG000PAG19J7C: OK - Reallocated_Event_Count is 0

GTG000PAG19J7C: OK - Current_Pending_Sector is 0

GTG000PAG19J7C: WARNING - Power_On_Hours it is now 21892 (warning threshold is 20000)

GTG000PAG19J7C: OK - Offline_Uncorrectable is 0

GTG000PAG19J7C: OK - UDMA_CRC_Error_Count is 0

GTG000PAG0VUXC: OK - ATA_Error_Count is 0

GTG000PAG0VUXC: OK - Raw_Read_Error_Rate is 0

GTG000PAG0VUXC: OK - Spin_Up_Time is 657 (Average 656)

GTG000PAG0VUXC: OK - Start_Stop_Count is 1174

GTG000PAG0VUXC: OK - Spin_Retry_Count is 0

GTG000PAG0VUXC: OK - Power_Cycle_Count is 55

GTG000PAG0VUXC: OK - Reallocated_Sector_Ct is 0

GTG000PAG0VUXC: OK - Seek_Error_Rate is 0

GTG000PAG0VUXC: OK - Temperature_Celsius is 34 (Lifetime Min/Max 20/58)

GTG000PAG0VUXC: OK - Reallocated_Event_Count is 0

GTG000PAG0VUXC: OK - Current_Pending_Sector is 0

GTG000PAG0VUXC: WARNING - Power_On_Hours it is now 21895 (warning threshold is 20000)

GTG000PAG0VUXC: OK - Offline_Uncorrectable is 0

GTG000PAG0VUXC: OK - UDMA_CRC_Error_Count is 0

Disk 0: OK - ATA_Error_Count is 0

Disk 0: OK - Raw_Read_Error_Rate is 0

Disk 0: OK - Spin_Up_Time is 9850

Disk 0: OK - Start_Stop_Count is 150

Disk 0: OK - Spin_Retry_Count is 0

Disk 0: OK - Calibration_Retry_Count is 0

Disk 0: OK - Power_Cycle_Count is 10

Disk 0: OK - Reallocated_Sector_Ct is 0

Disk 0: OK - Seek_Error_Rate is 0

Disk 0: OK - Temperature_Celsius is 33

Disk 0: OK - Reallocated_Event_Count is 0

Disk 0: OK - Current_Pending_Sector is 0

Disk 0: OK - Power_On_Hours is 1088

Disk 0: OK - Offline_Uncorrectable is 0

Disk 0: OK - UDMA_CRC_Error_Count is 0

Disk 0: OK - Multi_Zone_Error_Rate is 0

9VS14WNM: OK - ATA_Error_Count is 0

9VS14WNM: OK - Raw_Read_Error_Rate is 116824793

9VS14WNM: OK - Spin_Up_Time is 0

9VS14WNM: OK - Start_Stop_Count is 1064

9VS14WNM: OK - Spin_Retry_Count is 9

9VS14WNM: OK - Power_Cycle_Count is 22

9VS14WNM: OK - Reallocated_Sector_Ct is 0

9VS14WNM: OK - Seek_Error_Rate is 17697088

9VS14WNM: OK - Temperature_Celsius is 31 (0 19 0 0)

9VS14WNM: OK - Current_Pending_Sector is 0

9VS14WNM: OK - Power_On_Hours is 11198

9VS14WNM: OK - Offline_Uncorrectable is 0

9VS14WNM: OK - UDMA_CRC_Error_Count is 0

10 device(s) active, 0 sleeping, 1 did not return SMART data.

 

 

Thanks Joe!

 

Yup, installed a 2tb parity drive a while back so I'm good there.  Thanks for the suggestion on running the preclear.  I will either do that, or just save the old 1tb drive for a week or two, as it is still working and it will still have my data on it.

Sorry, the removed parity drive will be out-of-date as soon as you modify ANY file or directory on ANY drive, therefore, keeping it around for several weeks really does not help, not unless you make no other changes to any of the other disks.

 

I do have another question for you.  I have 4 of these 1tb drives, all about 4 years old.  I got these when they first came out.  Being they have been in a NAS and now my unraid server, they have been powered on all the time.  The result is I'm now getting Smart alerts on all 4 drives that says

GTG000PAG051KC: WARNING - Power_On_Hours it is now 21892 (warning threshold is 20000)

So I'm proactively swapping them out one at a time, mainly due to lack of funds.  My question is which one should be swapped first, then second, and so on. 

I would swap them out as funds and space requirement dictate.  There is no indication that any of the drives is having any difficulty at all.  You are more likely to have a new drive with a mechanical problem than one that has been spinning for 20,000 hours and shows no problems.

 

Yes, you can be pro-active... but no need to rush.

 

I have a pair of Hitachi 500Gig drives that have been in my server since I originally purchased it from lime-technology about 4 1/2 years ago. 

(At the time, they were the biggest available, and cost over $300 each)

 

Their hours in their SMART reports look like this:

  9 Power_On_Hours          0x0012  095  095  000    Old_age  Always      -      40386

and this:

  9 Power_On_Hours          0x0012  095  095  000    Old_age  Always      -      40258

 

Both have twice the hours of your drives, and neither shows any signs of problems in any way.  Their "normalized" value is "95" and the failure threshold is "0."  I can guess that they both started with a normalized value of "100."  That would indicate to me that 40,000 = a decrement of the normalized value by a count of 5.  Going by that scale, it will be a very long time before the manufacturer considers the drive hours to be excessive.  I doubt the drive will be in existence that long.

 

Wait for sales and good deals for the replacement drives.  No need to rush unless you actually have a failure of an existing disk, or need the additional space.

 

Joe L.

  • Author

Thanks Joe!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.