I posted in the announcements forum and realized it is probably the wrong place. I just did an upgrade to 6.3.3 and it is telling me that all the data on Parity 1 will be erased. Id this normal?

It's not normal.

 

Are you sure that is your old parity disk?

I didnt move any around. I had a pending resierfs to xfs change on disk 4 which is a 2TB disk. But I haven't touched any of the 5tb disks

The log is strange too. It is calling that disk #29, but there are only 25 including the flash drive in the server:

 

Apr 1 13:20:54 Taranis kernel: md: import disk11: (sde) ST5000DM000-1FK178_W4J13BMJ size: 4883770532 
Apr 1 13:20:54 Taranis kernel: mdcmd (13): import 12 sdd 1953514552 0 WDC_WD20EARS-00MVWB0_WD-WMAZA3343353
Apr 1 13:20:54 Taranis kernel: md: import disk12: (sdd) WDC_WD20EARS-00MVWB0_WD-WMAZA3343353 size: 1953514552 
Apr 1 13:20:54 Taranis kernel: mdcmd (14): import 13 sdc 1953514552 0 WDC_WD20EARS-00MVWB0_WD-WMAZA2707168
Apr 1 13:20:54 Taranis kernel: md: import disk13: (sdc) WDC_WD20EARS-00MVWB0_WD-WMAZA2707168 size: 1953514552 
Apr 1 13:20:54 Taranis kernel: mdcmd (15): import 14 sdy 4883770532 0 ST5000DM000-1FK178_W4J0TA07
Apr 1 13:20:54 Taranis kernel: md: import disk14: (sdy) ST5000DM000-1FK178_W4J0TA07 size: 4883770532 
Apr 1 13:20:54 Taranis kernel: mdcmd (16): import 15 sdv 4883770532 0 ST5000DM000-1FK178_W4J1NBTT
Apr 1 13:20:54 Taranis kernel: md: import disk15: (sdv) ST5000DM000-1FK178_W4J1NBTT size: 4883770532 
Apr 1 13:20:54 Taranis kernel: mdcmd (17): import 16 sdu 3907018532 0 Hitachi_HDS724040ALE640_PK2331PAH1KH7T
Apr 1 13:20:54 Taranis kernel: md: import disk16: (sdu) Hitachi_HDS724040ALE640_PK2331PAH1KH7T size: 3907018532 
Apr 1 13:20:54 Taranis kernel: mdcmd (18): import 17 sdx 3907018532 0 ST4000DM000-1F2168_S3013ES8
Apr 1 13:20:54 Taranis kernel: md: import disk17: (sdx) ST4000DM000-1F2168_S3013ES8 size: 3907018532 
Apr 1 13:20:54 Taranis kernel: mdcmd (19): import 18 sds 3907018532 0 WDC_WD40EZRX-00SPEB0_WD-WCC4E2EC87LY
Apr 1 13:20:54 Taranis kernel: md: import disk18: (sds) WDC_WD40EZRX-00SPEB0_WD-WCC4E2EC87LY size: 3907018532 
Apr 1 13:20:54 Taranis kernel: mdcmd (20): import 19 sdb 4883770532 0 ST5000DM000-1FK178_W4J0Z1Y8
Apr 1 13:20:54 Taranis kernel: md: import disk19: (sdb) ST5000DM000-1FK178_W4J0Z1Y8 size: 4883770532 
Apr 1 13:20:54 Taranis kernel: mdcmd (21): import 20 sdl 3907018532 0 WDC_WD40EZRZ-00WN9B0_WD-WCC4E3KDEK0U
Apr 1 13:20:54 Taranis kernel: md: import disk20: (sdl) WDC_WD40EZRZ-00WN9B0_WD-WCC4E3KDEK0U size: 3907018532 
Apr 1 13:20:54 Taranis kernel: mdcmd (22): import 21
Apr 1 13:20:54 Taranis kernel: mdcmd (23): import 22
Apr 1 13:20:54 Taranis kernel: mdcmd (24): import 23
Apr 1 13:20:54 Taranis kernel: mdcmd (25): import 24
Apr 1 13:20:54 Taranis kernel: mdcmd (26): import 25
Apr 1 13:20:54 Taranis kernel: mdcmd (27): import 26
Apr 1 13:20:54 Taranis kernel: mdcmd (28): import 27
Apr 1 13:20:54 Taranis kernel: mdcmd (29): import 28
Apr 1 13:20:54 Taranis kernel: mdcmd (30): import 29 sdm 4883770532 0 ST5000DM000-1FK178_W4J13BNL
Apr 1 13:20:54 Taranis kernel: md: import disk29: (sdm) ST5000DM000-1FK178_W4J13BNL size: 4883770532 
Apr 1 13:20:54 Taranis emhttp: import 30 cache device: sdk
Apr 1 13:20:54 Taranis emhttp: import 31 cache device: sdj
Apr 1 13:20:54 Taranis emhttp: check_pool: /sbin/btrfs filesystem show f0914f41-d542-45ff-8007-190e8b288950 2>&1
Apr 1 13:20:54 Taranis emhttp: cacheUUID: f0914f41-d542-45ff-8007-190e8b288950
Apr 1 13:20:54 Taranis emhttp: cacheNumDevices: 2
Apr 1 13:20:54 Taranis emhttp: cacheTotDevices: 2
Apr 1 13:20:54 Taranis emhttp: cacheNumMissing: 0
Apr 1 13:20:54 Taranis emhttp: cacheNumMisplaced: 0
Apr 1 13:20:54 Taranis emhttp: cacheNumExtra: 0
Apr 1 13:20:54 Taranis emhttp: import flash device: sda

29 is parity2, post your diagnostics.

Here you go.

 

 

taranis-diagnostics-20170401-1335.zip

Parity got disabled before this reboot, do you have notifications enable?

 

You need a new parity disk:

 

197 Current_Pending_Sector  0x0012   092   092   000    Old_age   Always       -       2640
198 Offline_Uncorrectable   0x0010   092   092   000    Old_age   Offline      -       2640

 

That is strange it was fine before I rebooted otherwise I wouldn't have done it.

 

Is it getting mixed up with the drive I just witched from reiserfs to xfs?

I cant afford to replace it, so should I just start it and let it erase it as it says?

3 minutes ago, eaglepigjim said:

That is strange it was fine before I rebooted

 

Very unlikely if not impossible, disk was disable at boot time, disk is only disable if a writes fails, disk is very sick.