View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006205 | Rocky-Linux-8 | kernel | public | 2024-03-31 10:18 | 2024-03-31 17:01 |
| Reporter | Giannis Economou | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0006205: aacraid problem on kernel 4.18.0-513.18.1 | ||||
| Description | After rebooting a server to the latest kernel, our Adaptec RAID controller started giving a lot or errors. Seems related to this: https://bugzilla.kernel.org/show_bug.cgi?id=217599 Before finding out that this is kernel related, we changed RAID controller (same model), cables etc. Problem was not resolved, but was immediately resolved after booting back to 4.18.0-425.13.1 Controller Model (from arcconf util) is: Adaptec ASR8405 From dmesg we where having many messages like those below. [28081.438826] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [28287.848651] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [31271.793465] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [34331.562419] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [36861.330001] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [37721.047053] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [38049.512860] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [38211.972057] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [40502.146839] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [42225.219737] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [42431.029251] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [43139.577598] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [43378.654203] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [50770.782297] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [50996.711065] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [51066.921025] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.924818] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.928570] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.932280] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.932282] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.935983] blk_update_request: I/O error, dev sda, sector 246629848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [51066.939742] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.943928] blk_update_request: I/O error, dev sda, sector 246629848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [51066.947333] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.959533] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.963643] sd 0:0:3:0: Device offlined - not ready after error recovery [51066.967699] sd 0:0:3:0: Device offlined - not ready after error recovery | ||||
| Steps To Reproduce | Just boot to | ||||
| Tags | No tags attached. | ||||
 |
You might want to do a test install of ELRepo's kernel to see if the latest kernel from upstream (kernel.org) fixes the issue. kernel-lt ( https://elrepo.org/wiki/doku.php?id=kernel-lt ) or kernel-ml ( https://elrepo.org/wiki/doku.php?id=kernel-ml ) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-31 10:18 | Giannis Economou | New Issue | |
| 2024-03-31 17:01 | Akemi Yagi | Note Added: 0006568 |
