Jump to content

[6.8.3] Server becomes completely unresponsive upon starting array at Opening encrypted volumes...


Recommended Posts

Hello!

 

I have recently begun running into a problem where upon restarting my server and entering the encrypted array password the system just immediately freezes. I have an array with 8 devices, 6 data(1x10tb,3x8tb,2x2tb), 1 parity (10tb), 1 cache (800gb), all of which are encrypted. All pIugins are up to date. I tailed the syslog as the array was being started and everything seems to go completely fine up until it just stops, the ssh connections die, the webui stops responding, the system stops responding to ping, etc with the only recourse being pressing the power button (which it seems to be responsive to) or a reset.

 

The unassigned devices section goes to a load anim and the status gets stuck on "Opening encrypted volumes..." shortly thereafter the system stops responding.

image.thumb.png.d9cea35a15d7324074d5ecaf820c2113.png

 

The log is:

Jul 17 09:51:50 ark emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
Jul 17 09:55:45 ark emhttpd: shcmd (950): echo 128 > /sys/block/sdb/queue/nr_requests
Jul 17 09:55:45 ark kernel: mdcmd (44): set md_num_stripes 1280
Jul 17 09:55:45 ark kernel: mdcmd (45): set md_queue_limit 80
Jul 17 09:55:45 ark kernel: mdcmd (46): set md_sync_limit 5
Jul 17 09:55:45 ark kernel: mdcmd (47): set md_write_method
Jul 17 09:55:45 ark kernel: mdcmd (48): set spinup_group 0 0
Jul 17 09:55:45 ark kernel: mdcmd (49): set spinup_group 1 0
Jul 17 09:55:45 ark kernel: mdcmd (50): set spinup_group 2 0
Jul 17 09:55:45 ark kernel: mdcmd (51): set spinup_group 3 0
Jul 17 09:55:45 ark kernel: mdcmd (52): set spinup_group 4 0
Jul 17 09:55:45 ark kernel: mdcmd (53): set spinup_group 5 0
Jul 17 09:55:45 ark kernel: mdcmd (54): set spinup_group 6 0
Jul 17 09:55:45 ark emhttpd: shcmd (951): echo 128 > /sys/block/sdc/queue/nr_requests
Jul 17 09:55:45 ark emhttpd: shcmd (952): echo 128 > /sys/block/sdg/queue/nr_requests
Jul 17 09:55:45 ark emhttpd: shcmd (953): echo 128 > /sys/block/sde/queue/nr_requests
Jul 17 09:55:45 ark emhttpd: shcmd (954): echo 128 > /sys/block/sdd/queue/nr_requests
Jul 17 09:55:45 ark emhttpd: shcmd (955): echo 128 > /sys/block/sdh/queue/nr_requests
Jul 17 09:55:45 ark emhttpd: shcmd (956): echo 128 > /sys/block/sdf/queue/nr_requests
Jul 17 09:55:45 ark kernel: mdcmd (55): start STOPPED
Jul 17 09:55:45 ark kernel: unraid: allocating 41350K for 1280 stripes (8 disks)
Jul 17 09:55:45 ark kernel: md1: running, size: 1953514552 blocks
Jul 17 09:55:45 ark kernel: md2: running, size: 1953514552 blocks
Jul 17 09:55:45 ark kernel: md3: running, size: 7814026532 blocks
Jul 17 09:55:45 ark kernel: md4: running, size: 7814026532 blocks
Jul 17 09:55:45 ark kernel: md5: running, size: 7814026532 blocks
Jul 17 09:55:45 ark kernel: md6: running, size: 9766436812 blocks
Jul 17 09:55:47 ark emhttpd: shcmd (957): udevadm settle
Jul 17 09:55:48 ark emhttpd: Opening encrypted volumes...
Jul 17 09:55:48 ark emhttpd: shcmd (960): /usr/sbin/cryptsetup luksOpen /dev/md1 md1 --allow-discards
Jul 17 09:55:48 ark kernel: device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: [email protected]
Jul 17 09:55:48 ark emhttpd: shcmd (963): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --allow-discards
Jul 17 09:55:49 ark emhttpd: shcmd (966): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --allow-discards
Jul 17 09:55:50 ark emhttpd: shcmd (969): /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --allow-discards
Jul 17 09:55:51 ark emhttpd: shcmd (972): /usr/sbin/cryptsetup luksOpen /dev/md5 md5 --allow-discards
Jul 17 09:55:52 ark emhttpd: shcmd (975): /usr/sbin/cryptsetup luksOpen /dev/md6 md6 --allow-discards
Jul 17 09:55:52 ark emhttpd: shcmd (978): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --allow-discards
Jul 17 09:55:54 ark kernel: BTRFS: device fsid bc8556eb-4f8a-4d7e-9403-3b2f94d5e6ec devid 1 transid 100067 /dev/dm-6
Jul 17 09:55:54 ark root: Starting diskload

Any help would be immensely appreciated.

Link to comment
23 minutes ago, MattDahEpic said:

Second safe mode works just fine. Is there a list of plugins to try removing or is it just spray and pray? I also have the diagnostics bundle if needed.

Are all your plugins up-to-date?

 

One of the plugins I was trying to avoid with SAFE mode is Unassigned Devices since it looked like something might have hung there. Did you have any Unassigned Device set to Auto-mount?

Link to comment
9 minutes ago, trurl said:

Are all your plugins up-to-date?

 

One of the plugins I was trying to avoid with SAFE mode is Unassigned Devices since it looked like something might have hung there. Did you have any Unassigned Device set to Auto-mount?

Plugins are up to date. I do have one drive auto mounted (the vm one). Turning off auto mount seems to let the array mount. Why would that be?

Edited by MattDahEpic
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.

×
×
  • Create New...