May 28, 20224 yr After I switched from Supermicro server to Cisco USC dual server Unraid does not show drives in Unassigned devices but they are shown in System devices. Don't know how to fix this & preserve data on the drives. Diagnostic file is attached. Any help is appreciated. chia0-diagnostics-20220527-2318.zip
May 28, 20224 yr You're using a RAID controller, those are not recommended, but if you want to use you might need to pass-through each device to the OS, some controllers require creating JBOD/RAID0 volume for each device.
May 28, 20224 yr Author Each drive is set to JBOD in server settings. I can not change the RAID controller as its part of chassis unfortunately.
May 28, 20224 yr May 27 23:02:53 CHIA0 kernel: megaraid_sas 0000:0d:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009 May 27 23:02:53 CHIA0 kernel: megaraid_sas 0000:0d:00.0: FW in FAULT state Fault code:0x10000 subcode:0x0 func:megasas_wait_for_outstanding_fusion May 27 23:02:53 CHIA0 kernel: megaraid_sas 0000:0d:00.0: resetting fusion adapter scsi1. May 27 23:02:53 CHIA0 kernel: megaraid_sas 0000:0d:00.0: Outstanding fastpath IOs: 0 May 27 23:02:53 CHIA0 kernel: megaraid_sas 0000:0d:00.0: Reset not supported, killing adapter scsi1. Looks like a firmware fault in the controller resulted in it killing itself off which then resulted in a ton of errors on each drive May 27 23:02:53 CHIA0 kernel: sd 1:0:79:0: [sde] tag#505 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s May 27 23:02:53 CHIA0 kernel: sd 1:0:88:0: [sdn] tag#58 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s May 27 23:02:53 CHIA0 kernel: sd 1:0:88:0: [sdn] tag#58 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00 May 27 23:02:53 CHIA0 kernel: sd 1:0:84:0: [sdj] tag#506 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s May 27 23:02:53 CHIA0 kernel: sd 1:0:84:0: [sdj] tag#506 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00 May 27 23:02:53 CHIA0 kernel: blk_update_request: I/O error, dev sdj, sector 27344764800 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Which ultimately led to the OS not being able to utilize the drives May 27 23:03:06 CHIA0 emhttpd: device /dev/sdq problem getting id Complete shot in the dark, but update / reflash the firmware on the controller.
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.