Persistent Problem UPGRADING 6.9.2 to 6.11.2 (Same issue for 6.10)


Recommended Posts

Evening! I've put off upgrading my Unraid server for a long time but I don't want to fall so behind that eventually I will be out of range for docker updates and unraid features in the future.

 

It's been an entire year plus! :(

I restored my system back to 6.9.2 after a failures of my Array to start. I let the system sit idle for 2-3 hours and nothing still. I had access to my plugins but my Docker programs wouldn't start and my "Array Status" bar in the bottom left of Unraid just stayed saying "Array Starting". I'm not good at reading errors but these are my conclusions and I hope to get some help from Moderators or other Unraid experts.

1 ) The Errors I'm see state that the Hard Drives of my array were an ID (Example: sdm) and are being changed to another (Example: sdam).

 


Nov 23 15:08:08 XXXXXX  emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device N0008-2JJ101_SM_ZPW0LXZ5_3500605ba008bdc44 was (sdau) is now (sdw)

Nov 23 15:08:08 XXXXXX  emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device WD100EMAZ-00WJSM_JEGKN5EN_3500605ba000a7138 was (sdab) is now (sdd)


These hard drives are working just fine and are healthy. I'm not sure why this is happening. When reverting back to 6.9.2 the array starts up within 4-5 seconds of clicking on the button.

2 ) I have Errors stating they have problem getting the id. (May correlate to the error above)
 

Nov 23 15:08:08 Khaleesi  emhttpd: device /dev/sdi problem getting id
Nov 23 15:08:08 Khaleesi  emhttpd: device /dev/sdam problem getting id
Nov 23 15:08:08 Khaleesi  emhttpd: device /dev/sdp problem getting id
Nov 23 15:08:08 Khaleesi  emhttpd: device /dev/sdad problem getting id


Again everything is working just fine on 6.9.2.

3) I have no clue what a segfault is but this is the last Error. 

 


Nov 23 15:08:08 Khaleesi kernel: emhttpd[11587]: segfault at 674 ip 00005584e01539d4 sp 00007fffadd01270 error 4 in emhttpd[5584e0141000+21000]



I would appreciate as much help as possible. I attached the syslog file and diagnostic file from the 6.11.2 update to the post.

khaleesi-diagnostics-20221123-1622.zip khaleesi-syslog-20221123-2120.zip

Link to comment
Nov 23 15:07:27 Khaleesi  emhttpd: device /dev/sdk problem getting id
Nov 23 15:07:27 Khaleesi  emhttpd: device /dev/sdy problem getting id

These usually mean the same devices are being detected twice, do you have more than on cable connecting the HBA to the NetApp enclosure?

Link to comment

The NetApp does. I have a cable for the bottom half of the NetApp connected to the HBA and a cable for the Top half connected to the 2nd port of the HBA. When I saw the enclosure had two separate sections on the whole enclosure, I assumed I had to do it that way. It's been working since 2020.

 

Is there a reason for it stopping with the new update???

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.