https://bugzilla.kernel.org/show_bug.cgi?id=187221 vsudo (vsudoblog@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vsudoblog@xxxxxxxxx --- Comment #2 from vsudo (vsudoblog@xxxxxxxxx) --- I have a HPE Gen9 using RAI5, I get this error and distributed on this server is resynced and I don't understand the reason why OS doesn't accept and failure disk in RAID5 is normal. [Sun Mar 28 09:47:04 2021] hpsa 0000:03:00.0: device is ready. [Sun Mar 28 09:47:04 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical completed successfully Direct-Access HP LOGICAL VO LUME RAID-5 SSDSmartPathCap- En- Exp=1 [Sun Mar 28 09:54:54 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm artPathCap- En- Exp=1 [Sun Mar 28 09:55:50 2021] hpsa 0000:03:00.0: device is ready. [Sun Mar 28 09:55:50 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical completed successfully Direct-Access HP LOGICAL VO LUME RAID-5 SSDSmartPathCap- En- Exp=1 [Sun Mar 28 09:56:35 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm artPathCap- En- Exp=1 [Sun Mar 28 09:57:01 2021] hpsa 0000:03:00.0: device is ready. [Sun Mar 28 09:57:01 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical completed successfully Direct-Access HP LOGICAL VO LUME RAID-5 SSDSmartPathCap- En- Exp=1 [Sun Mar 28 10:00:56 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm artPathCap- En- Exp=1 [Sun Mar 28 10:00:57 2021] hpsa 0000:03:00.0: device is ready. [Sun Mar 28 10:00:57 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical completed successfully Direct-Access HP LOGICAL VO LUME RAID-5 SSDSmartPathCap- En- Exp=1 [Sun Mar 28 10:05:13 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm artPathCap- En- Exp=1 [Sun Mar 28 10:07:16 2021] INFO: task scsi_eh_0:473 blocked for more than 120 seconds. [Sun Mar 28 10:07:16 2021] Not tainted 4.15.0-55-generic #60-Ubuntu [Sun Mar 28 10:07:16 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Sun Mar 28 10:07:16 2021] scsi_eh_0 D 0 473 2 0x80000000 [Sun Mar 28 10:07:16 2021] Call Trace: [Sun Mar 28 10:07:16 2021] __schedule+0x291/0x8a0 [Sun Mar 28 10:07:16 2021] ? dev_printk_emit+0x4a/0x70 [Sun Mar 28 10:07:16 2021] schedule+0x2c/0x80 [Sun Mar 28 10:07:16 2021] schedule_timeout+0x1cf/0x350 [Sun Mar 28 10:07:16 2021] ? __dev_printk+0x3c/0x80 [Sun Mar 28 10:07:16 2021] ? dev_printk+0x56/0x80 [Sun Mar 28 10:07:16 2021] io_schedule_timeout+0x1e/0x50 [Sun Mar 28 10:07:16 2021] wait_for_completion_io+0xba/0x140 [Sun Mar 28 10:07:16 2021] ? wake_up_q+0x80/0x80 [Sun Mar 28 10:07:16 2021] hpsa_scsi_do_simple_cmd.isra.60+0xb3/0xf0 [hpsa] [Sun Mar 28 10:07:16 2021] hpsa_eh_device_reset_handler+0x3e4/0x7b0 [hpsa] [Sun Mar 28 10:07:16 2021] ? __switch_to_asm+0x40/0x70 [Sun Mar 28 10:07:16 2021] ? __switch_to_asm+0x34/0x70 [Sun Mar 28 10:07:16 2021] ? scsi_device_put+0x2b/0x30 [Sun Mar 28 10:07:16 2021] scsi_eh_ready_devs+0x333/0xbf0 [Sun Mar 28 10:07:16 2021] ? __pm_runtime_resume+0x5b/0x80 [Sun Mar 28 10:07:16 2021] ? scsi_try_target_reset+0x90/0x90 [Sun Mar 28 10:07:16 2021] scsi_error_handler+0x4c3/0x5b0 [Sun Mar 28 10:07:16 2021] kthread+0x121/0x140 [Sun Mar 28 10:07:16 2021] ? scsi_eh_get_sense+0x200/0x200 [Sun Mar 28 10:07:16 2021] ? kthread_create_worker_on_cpu+0x70/0x70 [Sun Mar 28 10:07:16 2021] ret_from_fork+0x35/0x40 [Sun Mar 28 10:07:16 2021] INFO: task systemd-journal:109135 blocked for more than 120 seconds. [Sun Mar 28 10:07:16 2021] Not tainted 4.15.0-55-generic #60-Ubuntu [Sun Mar 28 10:07:16 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Sun Mar 28 10:07:16 2021] systemd-journal D 0 109135 1 0x00000320 [Sun Mar 28 10:07:16 2021] Call Trace: [Sun Mar 28 10:07:16 2021] __schedule+0x291/0x8a0 [Sun Mar 28 10:07:16 2021] ? intel_pstate_update_pstate+0x40/0x40 My website: https://vsudo.blog -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
