RAIDZ2 after disk replacment all disk degraded (need Help!)

[sretalla]

If we can manage to bring back my data I will buy this item: https://adaptec.com/de-de/products/hba1100/

It's really recommended to stay away from Adaptec and stick to LSI HBA cards if you don't want to face problems.

 

[MutoSan]

It's really recommended to stay away from Adaptec and stick to LSI HBA cards if you don't want to face problems.

Thanks for the imput. The adaptec was more ment as an example but I am willing to buy an LSI.

 

[sretalla]

I sent you a private message with some more locally specific suggestions about what to get.

 

[sretalla]

Not to put you down but the side to figure out my controller does not help. That is for a Linux system and not freebsd.

I wasn't actually intending for you to look at that link as the instructions for what to do, just an example of the syntax you need to find (actually I really only looked at this first bit... smartctl -a -d sat+megaraid,3 /dev/sda... for what you would need to figure out for your card in particular, obviously in TrueNAS/FreeBSD as that's what you're using.

 

[MutoSan]

For most disks its this:
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68EUZN0
Serial Number: WD-WCC4N0XHC2SJ
LU WWN Device Id: 5 0014ee 2b8f5cc67
Firmware Version: 82.00A82
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Oct 28 14:13:42 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (40500) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 406) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 403
3 Spin_Up_Time 0x0027 179 175 021 Pre-fail Always - 6033
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 23
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 056 056 000 Old_age Always - 32178
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 23
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3526
194 Temperature_Celsius 0x0022 117 101 000 Old_age Always - 33
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I think ada3-8 are on board and and 1-2 are on the Sata Controller. There is one or two disks where it looks like this:
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68EUZN0
Serial Number: WD-WCC4N3SRHKN6
LU WWN Device Id: 5 0014ee 2b963eeb8
Firmware Version: 82.00A82
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Oct 28 14:15:43 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (41040) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 412) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 182 178 021 Pre-fail Always - 5900
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 35
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 056 056 000 Old_age Always - 32207
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 35
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3592
194 Temperature_Celsius 0x0022 118 102 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 19200 -
# 2 Short offline Completed without error 00% 19030 -
# 3 Short offline Completed without error 00% 18863 -
# 4 Short offline Completed without error 00% 18695 -
# 5 Short offline Completed without error 00% 18527 -
# 6 Short offline Completed without error 00% 18359 -
# 7 Short offline Completed without error 00% 18192 -
# 8 Short offline Completed without error 00% 18024 -
# 9 Short offline Completed without error 00% 17857 -
#10 Short offline Completed without error 00% 17689 -
#11 Short offline Completed without error 00% 17521 -
#12 Short offline Completed without error 00% 17353 -
#13 Short offline Completed without error 00% 17185 -
#14 Short offline Completed without error 00% 17017 -
#15 Short offline Completed without error 00% 16850 -
#16 Short offline Completed without error 00% 16682 -
#17 Short offline Completed without error 00% 16514 -
#18 Short offline Completed without error 00% 16346 -
#19 Short offline Completed without error 00% 16178 -
#20 Short offline Completed without error 00% 16010 -
#21 Short offline Completed without error 00% 15843 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

 

[sretalla]

OK, so for whichever that first disk is, you have a problem:

1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 403

That's 403 read errors reported by the disk itself.

The second one is clean

 

[MutoSan]

OK, so for whichever that first disk is, you have a problem:

That's 403 read errors reported by the disk itself.

The second one is clean

Probably because I put in the faulty one again.

 

[sretalla]

It could be that, but are you sure that's the one from that report?

Seeing just that block of data for each of the disks in code tags would be really helpful... like this:

ada1

Code:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 182 178 021 Pre-fail Always - 5900
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 35
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 056 056 000 Old_age Always - 32207
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 35
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3592
194 Temperature_Celsius 0x0022 118 102 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

 

[MutoSan]

just a thought. If I put in the new LSI SAS controller do you think the resilvering will work better? As the resilvering is now up 1day and 2hrs. Or should I just wait 2-3 days until its finished?

 

[jgreco]

@Etorix, you are the reason why I stopped using community boards. Instead of helping you just criticize, judge, lecture and challenge things.

Moderator note: Please consider that community members are not paid support staff, and are graciously taking time out of their own lives to try to help others. I strongly suggest considering the forum equivalent of Postel's law, which is to be liberal in what you accept and conservative in what you write. If you want to run around trying to find reasons to be offended by everything, that's easy to do, but it only hurts YOU in the end. The people here have all sorts of personalities, but in my experience they will try to set you on the right path going forward.

We criticize design decisions we see that are known to be a problem. Use of random RAID controllers is a known problem. My criticism of this is a large post all by itself.

We judge situations by their own merits. Using a RAID controller, for example, works fine, until it doesn't. This can sometimes be recoverable, but sometimes not. Either way, I judge it tragic.

We lecture people on how to do things right, not because we like to lecture, but because we want to see your NAS be a safe and successful place to store data. Years of experience indicates that there are MANY ways for thing to go wrong, and only a small set of ways to do it correctly.

We challenge things because it often turns out that the "devil is in the details," as they say. Challenging things is often the way we discover the root causes of user issues.

If you can knock the chip off your shoulder and and try to work with folks, you are much more likely to have a successful resolution, and you'll undoubtedly also get a lot of information on how you can improve your setup for the future. Criticizing, lecturing, judging, and challenging is part of the process of helping. Don't take it as some sort of personal affront.

 

[MutoSan]

It could be that, but are you sure that's the one from that report?

Seeing just that block of data for each of the disks in code tags would be really helpful... like this:

ada1

Code:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 182 178 021 Pre-fail Always - 5900
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 35
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 056 056 000 Old_age Always - 32207
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 35
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3592
194 Temperature_Celsius 0x0022 118 102 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

no its a different serial nummber. Just checked. So there is another disk failing. Thats bad. I ordered 2 new 4TB disks they just literately arrived.

 

[MutoSan]

Moderator note: Please consider that community members are not paid support staff, and are graciously taking time out of their own lives to try to help others. I strongly suggest considering the forum equivalent of Postel's law, which is to be liberal in what you accept and conservative in what you write. If you want to run around trying to find reasons to be offended by everything, that's easy to do, but it only hurts YOU in the end. The people here have all sorts of personalities, but in my experience they will try to set you on the right path going forward.

We criticize design decisions we see that are known to be a problem. Use of random RAID controllers is a known problem. My criticism of this is a large post all by itself.

We judge situations by their own merits. Using a RAID controller, for example, works fine, until it doesn't. This can sometimes be recoverable, but sometimes not. Either way, I judge it tragic.

We lecture people on how to do things right, not because we like to lecture, but because we want to see your NAS be a safe and successful place to store data. Years of experience indicates that there are MANY ways for thing to go wrong, and only a small set of ways to do it correctly.

We challenge things because it often turns out that the "devil is in the details," as they say. Challenging things is often the way we discover the root causes of user issues.

If you can knock the chip off your shoulder and and try to work with folks, you are much more likely to have a successful resolution, and you'll undoubtedly also get a lot of information on how you can improve your setup for the future. Criticizing, lecturing, judging, and challenging is part of the process of helping. Don't take it as some sort of personal affront.

Still is not the way to ask for such things. As you can see it can be misunderstood pretty fast. And he did not lecture me about how todo things better he lecture me about oh this is wrong and that is wrong and that is also wrong. Which at the end does not solve the problem and does not help anyone.

And the challange was on my signature which has nothing todo with what I asked for. And a moderator which does not see that should not be a moderator.

First fix a problem then go for things that have to be changed. This is the professional way and I can speak out of over 10 years of IT support experience. Never ever have we said to customers first ah that has to be changed this needs to be changed and thats totaly wrong. First you fix a problem and then you tell the customer what was wrong what needs to be done and what has to change.

 

[sretalla]

just a thought. If I put in the new LSI SAS controller do you think the resilvering will work better? As the resilvering is now up 1day and 2hrs. Or should I just wait 2-3 days until its finished?

If we're able to get smartctl data from all disks I think that's the first priority as resilvering is only going to help if we don't have any bad disks in the mix.

Make very sure that any new disks aren't EFAX models.

 

[MutoSan]

If we're able to get smartctl data from all disks I think that's the first priority as resilvering is only going to help if we don't have any bad disks in the mix.

Make very sure that any new disks aren't EFAX models.

So then the problem is at least with ada7 and ada8
root@freenas[/]# smartctl -a /dev/ada8
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68N32N0
Serial Number: WD-WCC7K1KCA16V
LU WWN Device Id: 5 0014ee 2b9d867bd
Firmware Version: 82.00A82
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Oct 28 14:46:18 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (32640) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 347) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 194 168 021 Pre-fail Always - 5258
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 15466
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 20
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 15
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 515
194 Temperature_Celsius 0x0022 119 102 000 Old_age Always - 31
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Still need to find out how I can read the ones on the Sata Adapter on PCI-E

 

[sretalla]

Still need to find out how I can read the ones on the Sata Adapter on PCI-E

maybe have a look at this:

smartctl --scan

 

[MutoSan]

as far as I read now the WD Red Plus are not SMR and in the same article the mention other HDs as EFAX so I believe they are not.

 

[MutoSan]

maybe have a look at this:

smartctl --scan

Thats the outcome:
root@freenas[/]# smartctl --scan
/dev/pass3 -d atacam # /dev/pass3, ATA device
/dev/ada3 -d atacam # /dev/ada3, ATA device
/dev/ada4 -d atacam # /dev/ada4, ATA device
/dev/ada5 -d atacam # /dev/ada5, ATA device
/dev/ada6 -d atacam # /dev/ada6, ATA device
/dev/ada7 -d atacam # /dev/ada7, ATA device
/dev/ada8 -d atacam # /dev/ada8, ATA device
/dev/ses0 -d atacam # /dev/ses0, ATA device

I think /dev/pass3 is the passthrough from the sata controller?

 

[sretalla]

I think you can ignore the first and last entries.

Can you get smartctl data from all the others (ada3-ada8) using the commands as suggested there?

like:
smartctl -a -d atacam /dev/ada3

 

[MutoSan]

I did already ada7 and ada8 but ill do all again

 

[sretalla]

I did already ada7 and ada8 but ill do all again

If we can see them all laid out clearly, we should be able to get a good picture of what's really wrong.