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.

Disk in parity slot is not biggest

Featured Replies

Hello,

 

I'm having a problem setting up parity for the first time, and I'm getting the 'Disk in parity slot is not biggest' message... I have searched the forums and I can't seem to find an answer to my problem... 

 

All three drives are 4tb seagate ironwolf NAS drives, and all appear to be the same size:

 

/dev/sdb:
 max sectors   = 7814037168/7814037168, HPA is disabled

/dev/sdc:
 max sectors   = 7814037168/7814037168, HPA is disabled

/dev/sdd:
 max sectors   = 7814037168/7814037168, HPA is disabled

 

I have attached a diagnostic file because I don't know what else is wrong... is there something I'm missing?

nagato-diagnostics-20210503-2142.zip

Set up ST4000VN008-2DR166_ZGY94T2F as the parity.  It's the largest

 

Were these shucked drives?  There may be a hidden partition on the other 2 as they are a hair smaller.

 

Do the drives already contain files?

  • Author
8 minutes ago, Squid said:

Set up ST4000VN008-2DR166_ZGY94T2F as the parity.  It's the largest

 

Were these shucked drives?  There may be a hidden partition on the other 2 as they are a hair smaller.

 

Do the drives already contain files?

Argh, yes they do contain files already... I was doing a rolling migration from my older server. They weren't shucked drives...

 

I'm curious, how did you find out that was the larger drive? Is there another file I missed? The smart output looked almost exactly the same...

 

I take it there's a tool I can use that empties a drive for another one?

Edited by drgambit

May  3 21:21:40 Nagato kernel: md: import disk0: (sdc) ST4000VN008-2DR166_ZDH8RTH2 size: 3907017540 
May  3 21:21:40 Nagato kernel: md: import_slot: 0 replaced
May  3 21:21:40 Nagato kernel: mdcmd (2): import 1 sdb 64 3907018532 0 ST4000VN008-2DR166_ZGY94T2F
May  3 21:21:40 Nagato kernel: md: import disk1: (sdb) ST4000VN008-2DR166_ZGY94T2F size: 3907018532 
May  3 21:21:40 Nagato kernel: mdcmd (3): import 2 sdd 2048 3907017540 0 ST4000VN008-2DR166_ZDH8DGWH
May  3 21:21:40 Nagato kernel: md: import disk2: (sdd) ST4000VN008-2DR166_ZDH8DGWH size: 3907017540 
May  3 21:21:40 Nagato kernel: mdcmd (4): import 3

 

What you'll have to do then is add that drive into the array, copy all of the files from it to the smaller one(s) and then reassign everything.

  • Author

Thanks a lot for your help, I really appreciate it. I'm looking on fdisk and I see that the other two drives are starting at sector 2048 and not 64... I'm going to try to preclear the drive to see if that helps...

1 minute ago, drgambit said:

sector 2048 and not 64

Thanks...  I was actually wondering what the 64 vs 2048 meant in those lines...

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.