System boots and runs but in the logs "Error 22, Unretryable error"

slayer99199

Dabbler
Joined
Oct 5, 2017
Messages
17
I should note that despite this error, my system boots and is otherwise running normally. Should I just ignore this or is this a problem?

OS Version:
FreeNAS-11.2-U4.1
(Build Date: May 10, 2019 21:33)
Processor:
Intel(R) Core(TM) i3-6300 CPU @ 3.80GHz (4 cores)
Memory:
16 GiB
Motherboard:
ASRock C236 WSI

I have 8 disks in 2 pools connected to 8 SATA slots on my motherboard (I don't have an external SATA card...yet). So my boot drive is actually a 256GB SSD connected via a SATA-to-USB connector and from there to the on board internal USB (you can see it to the right of the SATA ports in this image):

C236%20WSI-1(M).jpg




The error:

Code:
VT(efifb): resolution 800x600
CPU: Intel(R) Core(TM) i3-6300 CPU @ 3.80GHz (3792.15-MHz K8-class CPU)
Structured Extended Features3=0xc000000<IBPB,STIBP>
avail memory = 16226922496 (15475 MB)
Timecounter "TSC-low" frequency 1896073183 Hz quality 1000
pcib0: _OSC returned error 0x10
orm0: <ISA Option ROM> at iomem 0xc0000-0xcffff on isa0
ugen0.2: <SanDisk Ultra Fit> at usbus0
umass0: <SanDisk Ultra Fit, class 0/0, rev 2.10/1.00, addr 1> on usbus0
ugen0.3: <SABRENT SABRENT> at usbus0
umass1: <SABRENT SABRENT, class 0/0, rev 3.10/a0.00, addr 2> on usbus0
(probe0:umass-sim1:1:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00
(probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI status: Check Condition
(probe0:umass-sim1:1:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
(probe0:umass-sim1:1:0:0): Error 22, Unretryable error
da1 at umass-sim1 bus 1 scbus10 target 0 lun 0
da1: < SABRENT 2210> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 000000123AD2
da1: 400.000MB/s transfers
da1: 238475MB (488397168 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
epair0a: Ethernet address: 02:e4:d0:00:05:0a
epair0b: Ethernet address: 02:e4:d0:00:06:0b 


SanDisk is where I store my configuration backups.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Code:
ugen0.2: <SanDisk Ultra Fit> at usbus0
umass0: <SanDisk Ultra Fit, class 0/0, rev 2.10/1.00, addr 1> on usbus0
I was wondering about that... Thanks for clarifying.
SanDisk is where I store my configuration backups.
All the errors you are having are related back to the "SABRENT":
Code:
ugen0.3: <SABRENT SABRENT> at usbus0
umass1: <SABRENT SABRENT, class 0/0, rev 3.10/a0.00, addr 2> on usbus0
What is made by SABRENT? Is that the SSD or the USB enclosure for the SSD? It could be that the enclosure is going bad. I have had that happen to me. I have one sitting on my desk right now that I was contemplating throwing in the garbage because I just don't know if it is worth the effort to attempt to exercise the warranty. For me, the SSD is fine but the enclosure it junk. I replaced the enclosure and I am still using the SSD.
I have 8 disks in 2 pools
PS. Not related to your problem, but this is probably not the best configuration. Still, it may be fine for what you are doing.
 

slayer99199

Dabbler
Joined
Oct 5, 2017
Messages
17
I was wondering about that... Thanks for clarifying.

All the errors you are having are related back to the "SABRENT":

What is made by SABRENT? Is that the SSD or the USB enclosure for the SSD? It could be that the enclosure is going bad. I have had that happen to me. I have one sitting on my desk right now that I was contemplating throwing in the garbage because I just don't know if it is worth the effort to attempt to exercise the warranty. For me, the SSD is fine but the enclosure it junk. I replaced the enclosure and I am still using the SSD.

It's a Samsung SSD. I'm not using an enclosure (the SSD actually resides internally to my server in my drive cages with my other disks), I'm using a SATA-to-USB adapter. But thanks for pointing it out. I went back to the online store and confirmed....the adapter is a Sabrent.

https://www.microcenter.com/product/487040/usb-31-to-ssd-25-sata-hard-drive-adapter

The reason I chose this configuration is that I'm using all 8 of my motherboard's SATA connections and I didn't want to purchase another SATA card. Now I know USB drives (as in thumb drives) are not recommended or supported by FreeNAS....but I didn't think that would necessarily apply to this configuration (using a SSD drive connected via USB).

PS. Not related to your problem, but this is probably not the best configuration. Still, it may be fine for what you are doing.

I have one pool with 5 disks and the other with 3. I added the other 3 disks a few weeks ago as I was running out of space and I had 4 HGST 4TB disks lying around for another project (so I have one spare).

I found some additional information on the error in relation to protected formatting so I ran the following:

Code:
root@freenas:~ # smartctl -d sat -i /dev/da1
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.2-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 850 EVO 250GB
Serial Number:    S21NNSAG526920D
LU WWN Device Id: 5 002538 da02d99a4
Firmware Version: EMT01B6Q
User Capacity:    250,059,350,016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Aug 11 17:17:56 2019 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled



At this point I'm not prepared to go through a major upgrade as I have a new PC purchase scheduled this year (waiting for the next AMD Threadrippers). I bought myself some time by adding the 2nd pool (giving me 32TB RAW). I figure when it's time to upgrade, I"ll replace the mobo, CPU, memory, and add a couple of SATA cards (my Rosewill case supports 15 disks). If this is not "bad" for my system, I'd like to let it ride as long as I can until I need to upgrade my entire system.
 
Last edited:
Top