May 8, 20251 yr What are my next steps? My diagnostics are attached. A parity check just finished with 0 errors a few hours ago. Right about the time I logged on, I had an error pop-up for these 3 disks. I have not made any changes since this error occurred. The main screen shows the 3 disks still active in the array, but also shows them in the unassigned devices section, flagged as "array" with new device name. While these 3 disks have very little information and loss would not be a problem, I have noticed that I only have 2 shares but there should be 6 (by memory) and the main share only has 2 folders in it, but there should be around 10 (again, by memory). FYI - I'll check back in the morning. I must go to sleep. Lesson to be learned - don't check the server right before bed time. Edit - Solution provided. Removed diagnostics. Edited May 9, 20251 yr by NAS-t_Hirsute post solved
May 8, 20251 yr Community Expert Solution May 7 06:22:01 hirsute-theater kernel: mpt2sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready May 7 06:22:01 hirsute-theater kernel: mpt2sas_cm0: fault_state(0x7e23)! HBA problem, make sure it's well seated and sufficiently cooled, you can also try a different PCIe slot.
May 8, 20251 yr Author 4 hours ago, JorgeB said: HBA problem, make sure it's well seated and sufficiently cooled, you can also try a different PCIe slot. Seems the HBA card was not seated well. I did some searching, but might be using the wrong search terms to guide me on next steps. On a past issue, I can remember having issue getting an array disk to be recognized as part of the array and ended up having to rebuild on top of it. Next steps are stop and start array or should a reboot be included?
May 9, 20251 yr Author On 5/8/2025 at 10:29 AM, JorgeB said: Reboot and post new diags after array start. I went through the process and everything seems to be back to normal. I'll keep an eye on the HBA and research the lines you pointed out from my diagnostics for my own betterment. Thank you for your help! Edit - Solution provided. Removed diagnostics. Edited May 9, 20251 yr by NAS-t_Hirsute post solved
May 9, 20251 yr Community Expert That looks good, except May 8 21:15:57 hirsute-theater root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array Do you know how to fix?
May 9, 20251 yr Author 8 hours ago, trurl said: Do you know how to fix? In the past I used MC or krusader. Since this has happened again and there's plenty of space on my cache drive, 'm thinking set secondary array and set up mover. Agree?
May 9, 20251 yr Community Expert 5 hours ago, NAS-t_Hirsute said: set secondary array and set up mover. Agree? yes, Mover action:array->cache. But... Nothing can move open files. Go to Settings - Docker and disable until all moved.
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.