Return to Level1Techs.com

Freenas and a bunch errors

Hey, hope someone can help me out.

Last week I got an error message saying bad sectors so replaced the drive. The resilvering process took over 100 hours. Then after a restart yesterday freenas started resilvering again. So I left it and this morning when I checked. There were now these error messages

  1. ada7 2 currently unreadable
    (pending) sectors
  2. ada5 2 currently unreadable
    (pending) sectors
  3. ada3 ATA error increased from 4 to
    10

Ada3 is the drive I’ve recently replaced.

This is the status log

[[email protected] ~]# zpool status -v 
pool: J****** 
state: ONLINE 
status: One or more devices is currently being resilvered. The pool will 
continue to function, possibly in a degraded state. 
action: Wait for the resilver to complete. 
scan: resilver in progress since Tue Jun 8 22:06:40 2021 
1.32T scanned out of 15.2T at 26.6M/s, 151h48m to go 
166G resilvered, 8.72% done 
config: 

NAME STATE READ WRITE CKSUM 
Jarvis ONLINE 0 0 0 
raidz2-0 ONLINE 0 0 0 
gptid/4fd0edac-5eb8-11e5-8317-d050996490b6 ONLINE 0 0 0 
gptid/e0cc7676-18ed-11ea-b434-d050996490b6 ONLINE 0 0 0 
gptid/50aecb0b-5eb8-11e5-8317-d050996490b6 ONLINE 0 0 0 
gptid/934bee96-c498-11eb-b843-d050996490b6 ONLINE 0 0 0 (resilvering) 
gptid/51904b0f-5eb8-11e5-8317-d050996490b6 ONLINE 0 0 0 
gptid/5202b9d8-5eb8-11e5-8317-d050996490b6 ONLINE 0 0 0 
gptid/5275d7e4-5eb8-11e5-8317-d050996490b6 ONLINE 0 0 0 
gptid/52ee6b39-5eb8-11e5-8317-d050996490b6 ONLINE 0 0 0 

errors: Permanent errors have been detected in the following files: 

/mnt/J*******/Media/Movies/E********/E********.mkv 

pool: freenas-boot 
state: ONLINE 
scan: scrub repaired 0 in 0h3m with 0 errors on Fri Jun 4 03:48:35 2021 
config: 

NAME STATE READ WRITE CKSUM 
freenas-boot ONLINE 0 0 0 
gptid/a6612988-8d5e-11e6-aa3b-d050996490b6 ONLINE 0 0 0 

errors: No known data errors 

System spec
Freenas 9.10.2-U6 (booting from usb stick)
CPU intel atom c2750 2.4GHz
ECC Ram 32711MB
8 WD Red 3TB HDD

Any help would be greatly appreciated and sorry if I’ve posted this in the wrong neck of the woods
Thanks in advance

Based on what I could find out, there are no 3TB SMR drives from Western Digital, so this should not be an issue. The CPU is a bit weak, but given that you only have 3TB drives I am wondering why the resilvering process is so slow.

1 Like

FreeNAS shouldn’t try to resilver again unless maybe the drive dropped out of the array or failed during the first resilver task. What are you using for a hard drive controller? SATA ports on the motherboard or HBA or something else? Using a backplane? If the drive drops out of the array, that would explain the unexpected resilver. It might cause weird drive issues as well such as the unreadable errors… if you haven’t backed up your data from your pool yet, I strongly recommend you do so. At least until you figure out what is going on.

1 Like

Hey thanks for replying.

After a lot of digging around I think the problem is the new drive. The majority of the 3TB drives are 6 years old with the EFRX model number and are CMR drives. The new one is a EFAX drive which is an SMR.

As for the connections all the drives are connected to the motherboard. Via the caddy holders.

The resilver time was never as bad as this when I’ve replaced drives before, today it topped out at 150 hours

The server it’s self is only used to feed media and store back ups of work. Everything is already backed up off site on HDD drives if the worst happens

1 Like

ZFS does not work with SMR drives, I suggest you pull it immediately and use a CMR drive instead.

Thanks, everything is shut down and disconnected now. Going to get it swapped out for a CMR drive

Thanks once again for everyone’s help it’s greatly appreciated

1 Like

Just a thought, but i use caddy/trayless drives too, i had an issue and it turned out to be the caddy itself.

Will bare that in mind if it continues after getting the drive sorted, cause I wouldn’t have thought of the whole caddie being faulty

Glad it might help - I didn’t think of it either, moved a drive to another caddy, then created a pool on the potentially faulty caddy and voila, errors. Before that I changed the sata cable .