Strange freenas behavior after installing a new HDD.

[baglio]

Hello everybody.
Today I added a new HDD to my freenas box, until now, I just had a 40Gb old HDD which I rescued from his final destiny ; )

Anyway, the new disk is connected by USB, because I have no other SATA port.
The problem is that now, there's some command running in loop in the freenas background activity which seems to return some errors though the disk works properly.

Here is the log; I hope that someone of you which understand more can help me figuring out what's wrong.

Code:

Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)

And it keeps acting like this.

I thank you in advance!

 

[iGeeKy]

Hi there baglio, just wondering have you figured out what this issue was? I'm having the same issues here after I replaced a drive that was sending out errors. After I swapped the drive everything seemed to run perfect with zero errors until the above started. Everything seems be be running ok except for the errors over and over... sigh :(

--

Hello everybody.
Today I added a new HDD to my freenas box, until now, I just had a 40Gb old HDD which I rescued from his final destiny ; )

Anyway, the new disk is connected by USB, because I have no other SATA port.
The problem is that now, there's some command running in loop in the freenas background activity which seems to return some errors though the disk works properly.

Here is the log; I hope that someone of you which understand more can help me figuring out what's wrong.

Code:

Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:14:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:14:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:23 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
Apr 22 21:15:53 baglionas kernel: (da0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)

And it keeps acting like this.

I thank you in advance!

 

[iGeeKy]

These are the exact errors - any information you might that might help... anyone! Please

Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 85 96 99 b0 0 0 8 0 length 4096 SMID 205 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 a4 41 fa a8 0 0 8 0 length 4096 SMID 861 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 85 96 99 a8 0 0 8 0 length 4096 SMID 444 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 a4 41 fa a0 0 0 8 0
Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): CAM status: SCSI Status Error
Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): SCSI status: Check Condition
Jan 11 21:21:12 Aurora kernel: (da4:mps0:0:4:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 0 40 1 c0 0 0 8 0 length 4096 SMID 327 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 0 40 3 c0 0 0 8 0 length 4096 SMID 208 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 e8 e0 85 c0 0 0 8 0 length 4096 SMID 271 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 e8 e0 87 c0 0 0 8 0
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): CAM status: SCSI Status Error
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): SCSI status: Check Condition
Jan 11 21:55:29 Aurora kernel: (da4:mps0:0:4:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 85 96 ea 8 0 0 8 0 length 4096 SMID 827 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 a4 42 61 b0 0 0 8 0 length 4096 SMID 200 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 85 96 ea 0 0 0 8 0 length 4096 SMID 935 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 a4 42 61 a8 0 0 8 0
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): CAM status: SCSI Status Error
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): SCSI status: Check Condition
Jan 11 22:01:51 Aurora kernel: (da4:mps0:0:4:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 0 40 2 10 0 0 8 0 length 4096 SMID 681 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 0 40 4 10 0 0 8 0 length 4096 SMID 151 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 e8 e0 86 10 0 0 8 0 length 4096 SMID 145 terminated ioc 804b scsi 0 state 0 xfer 0
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): WRITE(10). CDB: 2a 0 e8 e0 88 10 0 0 8 0
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): CAM status: SCSI Status Error
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): SCSI status: Check Condition
Jan 11 22:07:04 Aurora kernel: (da4:mps0:0:4:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)

 

[ben]

http://forums.freebsd.org/showthread.php?t=31884 This was the answer to this question on FreeBSD. However, I do not know how that condition interacts with FreeNAS, so proceed with caution.

 

[baglio]

Hi there baglio, just wondering have you figured out what this issue was? I'm having the same issues here after I replaced a drive that was sending out errors. After I swapped the drive everything seemed to run perfect with zero errors until the above started. Everything seems be be running ok except for the errors over and over... sigh

Hi iGeeky,

No, unfortunately i didn't solve the question, nevertheless this isn't a problem anymore since I've detached that HDD from the USB connection and connect it via SATA port.
So I'm sorry I can't help you...though I'm sore some expert here can! ;)

 

[jgreco]

Check to make sure your drive and controller firmware are up-to-date.

If it were a USB disk, and the disk were maybe larger than 2TB, I'd be tempted to say that baglio's problem suggested a USB SATA controller that didn't support such capacities. I don't actually recall the specific error generated in such a case, but it seems a little familiar.

 

[baglio]

Hi jgreco, the HDD that were connected via usb had a capacity of 80GB.

I think that the problem was the fact that this HDD was an internal HDD, designed to be connected via SATA.
Due to space problem, I had to connect it via USB using a "converting box"... You know... is that kind of metal box where you connect the internal HDD to act it as an external USB...

It's only a suggestion... but maybe this could be the problem...

 

[jgreco]

Most of those magic chips that convert USB to SATA are less-than-ideal. I'm not shocked if it was causing problems.