February 26, 20242 yr Hi all, I've just installed unRAID for the first time, so, please, be kind! 😁 When I create a new configuration (every time I create a new one), I see my 2 6TB HGST SAS drives (connected to a SAS9205-8i controller), but as soon as I select them, they disappears. In the logs I see this: Feb 26 05:06:00 Tower kernel: md: unRAID driver removed Feb 26 05:06:00 Tower emhttpd: shcmd (364106): /sbin/modprobe md-mod super=/boot/config/super.dat Feb 26 05:06:00 Tower kernel: md: unRAID driver 2.9.27 installed Feb 26 05:06:00 Tower emhttpd: Device inventory: Feb 26 05:06:00 Tower emhttpd: HUS726060AL5214_K1KD1THF_35000cca255bf06bc (sdb) 512 11721045168 Feb 26 05:06:00 Tower emhttpd: HUS726060AL5214_K1HM3B8F_35000cca2555b1cb8 (sdc) 512 11721045168 Feb 26 05:06:00 Tower emhttpd: SAMSUNG_MZVLQ256HBJD-00BH1_S672NS1T672837 (nvme1n1) 512 500118192 Feb 26 05:06:00 Tower emhttpd: SAMSUNG_MZVLQ256HBJD-00BH1_S672NS0T668130 (nvme0n1) 512 500118192 Feb 26 05:06:00 Tower emhttpd: SanDisk_Ultra_Fit_4C531001560408111345-0:0 (sda) 512 30031250 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#651 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#651 Sense Key : 0xb [current] [descriptor] Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#651 ASC=0x10 ASCQ=0x3 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#651 CDB: opcode=0x7f, sa=0x9 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#651 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#651 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 Feb 26 05:06:00 Tower kernel: protection error, dev sdc, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#652 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#652 Sense Key : 0xb [current] [descriptor] Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#652 ASC=0x10 ASCQ=0x3 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#652 CDB: opcode=0x7f, sa=0x9 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#652 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00 Feb 26 05:06:00 Tower kernel: sd 2:0:1:0: [sdc] tag#652 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 Feb 26 05:06:00 Tower kernel: protection error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 26 05:06:00 Tower kernel: Buffer I/O error on dev sdc, logical block 0, async page read Feb 26 05:06:00 Tower emhttpd: error: ckmbr, 2290: Input/output error (5): read: /dev/sdc Feb 26 05:06:00 Tower emhttpd: ckmbr error: -1 Feb 26 05:06:00 Tower kernel: mdcmd (1): import 0 Feb 26 05:06:00 Tower kernel: mdcmd (2): import 1 Feb 26 05:06:00 Tower kernel: mdcmd (3): import 2 Feb 26 05:06:00 Tower kernel: mdcmd (4): import 3 Feb 26 05:06:00 Tower kernel: mdcmd (5): import 4 Feb 26 05:06:00 Tower kernel: mdcmd (6): import 5 Feb 26 05:06:00 Tower kernel: mdcmd (7): import 6 Feb 26 05:06:00 Tower kernel: mdcmd (8): import 7 Feb 26 05:06:00 Tower kernel: mdcmd (9): import 8 Feb 26 05:06:00 Tower kernel: mdcmd (10): import 9 Feb 26 05:06:00 Tower kernel: mdcmd (11): import 10 Feb 26 05:06:00 Tower kernel: mdcmd (12): import 11 Feb 26 05:06:00 Tower kernel: mdcmd (13): import 12 Feb 26 05:06:00 Tower kernel: mdcmd (14): import 13 Feb 26 05:06:00 Tower kernel: mdcmd (15): import 14 Feb 26 05:06:00 Tower kernel: mdcmd (16): import 15 Feb 26 05:06:00 Tower kernel: mdcmd (17): import 16 Feb 26 05:06:00 Tower kernel: mdcmd (18): import 17 Feb 26 05:06:00 Tower kernel: mdcmd (19): import 18 Feb 26 05:06:00 Tower kernel: mdcmd (20): import 19 Feb 26 05:06:00 Tower kernel: mdcmd (21): import 20 Feb 26 05:06:00 Tower kernel: mdcmd (22): import 21 Feb 26 05:06:00 Tower kernel: mdcmd (23): import 22 Feb 26 05:06:00 Tower kernel: mdcmd (24): import 23 Feb 26 05:06:00 Tower kernel: mdcmd (25): import 24 Feb 26 05:06:00 Tower kernel: mdcmd (26): import 25 Feb 26 05:06:00 Tower kernel: mdcmd (27): import 26 Feb 26 05:06:00 Tower kernel: mdcmd (28): import 27 Feb 26 05:06:00 Tower kernel: mdcmd (29): import 28 Feb 26 05:06:00 Tower kernel: mdcmd (30): import 29 Feb 26 05:06:00 Tower emhttpd: import 30 cache device: no device Feb 26 05:06:00 Tower emhttpd: import 31 cache device: no device Feb 26 05:06:00 Tower emhttpd: import 32 cache device: no device Feb 26 05:06:00 Tower emhttpd: import flash device: sda Feb 26 05:06:00 Tower root: Submitting SysDrivers Build Feb 26 05:06:01 Tower emhttpd: read SMART /dev/sdb Feb 26 05:06:01 Tower emhttpd: read SMART /dev/sdc Feb 26 05:06:01 Tower emhttpd: read SMART /dev/nvme1n1 Feb 26 05:06:01 Tower emhttpd: read SMART /dev/nvme0n1 Feb 26 05:06:01 Tower emhttpd: read SMART /dev/sda Feb 26 05:06:01 Tower SysDrivers: SysDrivers Build Starting What could it be? Thanks!
February 26, 20242 yr Community Expert Solution 15 minutes ago, patrizius said: protection error You need to get rid of this, see below form more info: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/
February 27, 20242 yr Author 21 hours ago, JorgeB said: You need to get rid of this, see below form more info: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/ Thanks, that worked! sg_format --format --fmtpinfo=0 /dev/sdb
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.