smartd 2688 - - Device: /dev/ciss0 [cciss_disk_06] [SCSI], SMART Failure: HARDWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS

Bnito Kmelas

Cadet
Joined
Dec 16, 2019
Messages
3
Greetings Everyone,

A couple of days ago i started getting this message:

smartd 2688 - - Device: /dev/ciss0 [cciss_disk_06] [SCSI], SMART Failure: HARDWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS but all my disks seem to be okey, i´ll appreciate some feed back on this error.

Thanks in Advance! (Y)
 

Alecmascot

Guru
Joined
Mar 18, 2014
Messages
1,177
Looks like errors from Hardware Raid.
You will need to supply full system details as per the Forum Rules.
 

Alecmascot

Guru
Joined
Mar 18, 2014
Messages
1,177
That's not enough detail.
How are the disks presented to TNAS ?
What is the output of 'zpool status'

Have you seen :

 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
That's not enough detail.

Respectfully disagree; the CISS driver is written from a RAID perspective with a goal of keeping "disk issues" hidden from the server to a large extent. You already quoted a great (imho!) resource on that topic:


but it is worth noting that CISS controller have provided endless headaches for some people. In this case, it is actually working close to as well as possible, by reporting the issue without being particularly disruptive. OP should replace disk 6.

I believe the Smart Array controller may be one of the controllers that places its own "header"/partition table on a disk, and if that's so, it's going to be a real problem to replace it with a real HBA. Best advice is to backup all the data off the pool, put in an LSI HBA running IT firmware 20.00.07.00, and then build a new pool (if it won't import the old one after the controller change).
 

Bnito Kmelas

Cadet
Joined
Dec 16, 2019
Messages
3
Posting my output:

root@freenas12:~ # zpool status
pool: ShareDrive
state: ONLINE
scan: resilvered 10.3M in 00:00:12 with 0 errors on Tue Sep 21 07:47:24 2021
config:

NAME STATE READ WRITE CKSUM
ShareDrive ONLINE 0 0 0
raidz3-0 ONLINE 0 0 0
gptid/331c32fc-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/36bd52ec-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/3a82b069-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/3e58c3a7-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/4228852c-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/45c311b1-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/49852449-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/4d136413-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/50c28f2d-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/547dbbcf-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
cache
gptid/5a02cce8-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0
gptid/5f32c214-8ca7-11ea-90c5-78e3b5100ef2 ONLINE 0 0 0

errors: No known data errors

pool: boot-pool
state: DEGRADED
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P
scan: scrub repaired 0B in 00:03:17 with 0 errors on Sun Sep 19 03:48:18 2021
config:
 

AlexGG

Contributor
Joined
Dec 13, 2018
Messages
171
I believe the Smart Array controller may be one of the controllers that places its own "header"/partition table on a disk, and if that's so, it's going to be a real problem to replace it with a real HBA.

This is correct. Most controllers using configuration-on-disks will put metadata at the end of the disk, but SmartArray does indeed put it at the start, thus offsetting the user-accessible area.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
SmartArray does indeed put it at the start

I was about 95% certain.

So, backup your pool, tear out the Smart Array controller, replace it with an HBA, create a new pool, and reload your data onto the pool.
 
Top