steini84 Posted September 13, 2016 Share Posted September 13, 2016 Hey guys Currently on 6.2 RC5 (but this is probably happening on other version). I attached a USB 3.0 USB drive to my server for backups, but smartctl does not work unless I manually tell it that the drive is sata (smartctl -d sat -a /dev/sda) I guess that is the reason Something is causing spam in my syslog (when any page that shows disk info in the webgui is open) Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:17:52 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Sep 13 13:20:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:20:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:20:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:20:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:23:00 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 13:23:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 My question is: Is either a way to force "-d sat" in the lookup for that drive, or even for every smartctl lookup? (Solution in the answer below) Maybe the solution would be to remove the drive from Unassigned devices? Thanks Quote Link to comment
bonienl Posted September 13, 2016 Share Posted September 13, 2016 The current controller selection is missing a SATA option, made a correction for that. A workaround you can try: 1. Select as controller type 'ATA' (you can do this per disk -> goto Main -> diskname -> SMART settings) 2. After Apply the file /config/smart-one.cfg is created on your flash device 3. Edit the above file using a Linux editor and change "-d ata" to "-d sat" I am not using Unassigned Devices myself and can't verify if this works, but it's worth a try. Quote Link to comment
steini84 Posted September 13, 2016 Author Share Posted September 13, 2016 The current controller selection is missing a SATA option, made a correction for that. A workaround you can try: 1. Select as controller type 'ATA' (you can do this per disk -> goto Main -> diskname -> SMART settings) 2. After Apply the file /config/smart-one.cfg is created on your flash device 3. Edit the above file using a Linux editor and change "-d ata" to "-d sat" I am not using Unassigned Devices myself and can't verify if this works, but it's worth a try. Thanks for the quick reply! That worked... however, it does not seem to be the cause of the syslog spamming. Still getting these in some menus: Sep 13 15:16:57 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 15:16:57 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 15:16:57 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 15:16:57 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 I need to figure out if I can disable Unassigned Devices or remove the drive from that list. Is there a option to no use Unassigned Devices? I think it´s built into unraid 6.2 Quote Link to comment
bonienl Posted September 13, 2016 Share Posted September 13, 2016 Some confusion... are you using the plugin "Unassigned Devices" or do you refer to the native page "Unassigned Devices" ? Quote Link to comment
steini84 Posted September 13, 2016 Author Share Posted September 13, 2016 Just the native site - not using any plugins for unassigned devices Quote Link to comment
bonienl Posted September 13, 2016 Share Posted September 13, 2016 ok, clear. unRAID will not use any unassigned devices, but they are monitored in the background to create SMART reports. The monitor process uses the controller type in the file you have edited to read the device with the correct options. This happens every minute. At what interval do you see the error messages in the syslog (after you made the change) ? Quote Link to comment
steini84 Posted September 13, 2016 Author Share Posted September 13, 2016 Every thirty minutes since the change Sep 13 15:48:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 15:48:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 15:48:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 15:48:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00 Sep 13 15:48:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 15:48:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 15:48:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 15:48:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Sep 13 16:18:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 16:18:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 16:18:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 16:18:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00 Sep 13 16:18:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 16:18:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 16:18:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 16:18:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Sep 13 16:49:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 16:49:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 16:49:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 16:49:01 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00 Sep 13 16:49:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 16:49:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 16:49:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 16:49:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00 Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 17:19:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Sep 13 17:50:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 17:50:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 17:50:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 17:50:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00 Sep 13 17:50:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 17:50:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 17:50:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 17:50:03 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Sep 13 18:03:03 Unraid kernel: mdcmd (85): spindown 2 Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00 Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 Sep 13 18:21:02 Unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Then every time the unRAID webgui is opened on pages that show any disk info. Quote Link to comment
bonienl Posted September 13, 2016 Share Posted September 13, 2016 30 minutes is the standard interval for emhttp to read SMART information, see Settings -> Disk Settings -> Tunable (poll_attributes) = 1800 emhttp does not use the extra settings when reading SMART information, hence the errors when opening the main page and at the interval times. It requires a change (you may want to make a feature request) in emhttp to get this corrected / supported. Quote Link to comment
steini84 Posted September 13, 2016 Author Share Posted September 13, 2016 Thanks for the awesome help, but instead of hacking something together I have 4 choices: 1 - dont let the log errors bug me (not a chance 2- Passtrough the USB disk to a VM 3- Connect the drive internally via sata 4- Connect the USB disk to my pfsense Quote Link to comment
steini84 Posted September 14, 2016 Author Share Posted September 14, 2016 Well, there was a easy workaround for this. Just dont have the usb drive plugged in while the array is starting. If I connect it after the array is up there are no problems and the drive does not show up in Unassigned Devices Quote Link to comment
bonienl Posted September 14, 2016 Share Posted September 14, 2016 Well, there was a easy workaround for this. Just dont have the usb drive plugged in while the array is starting. If I connect it after the array is up there are no problems and the drive does not show up in Unassigned Devices Yeah you are right. unRAID won't have it added once the array is started, but it is still 'discovered' by linux. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.