kn0wt
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by kn0wt
-
-
On 8/23/2023 at 10:57 AM, ljm42 said:
Hmm, let's see what is going on:
- stop the array to reproduce the problem (don't do a full shutdown because you won't be able to grab diagnostics)
- show the output of `losetup` so we can see what /dev/loop2 points to on your system.
- run `umount /dev/loop2` to resolve the issue and let the array stop
- generate and upload your diagnostics.zip (from Tools -> Diagnostics) so we can see logs of the problem happening
- feel free to start the array again
having the same issue as @falkfyrebeard on 6.12.3, I attached my diagnostics and the output of `losetup`.. hopefully it'll help as well? ive had it happen to me the last 2 times ive stopped the array.. 1st time i waitied 20-30 min and then just hard rebooted the server. then just did it again and had the same issue..
root@Excalibur:~# losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/disk1/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 root@Excalibur:~# /etc/rc.d/rc.docker status status of dockerd: stopped root@Excalibur:~# umount /dev/loop2 root@Excalibur:~# -
On 7/6/2023 at 8:01 PM, ljm42 said:
UPDATE! please see my comment further down in this thread https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1283203
-------------------------------
Original message:
-------------------------------
I hit this today when stopping my array.
Here is what worked for me, would appreciate if someone hitting this would confirm it works for them too.
To get into this state, stop the array. If you are having this issue you will see "retry unmounting shares" in the lower left corner. Note: There are other reasons this message could happen (like if you left an SSH terminal open while cd'd into the array). This discussion assumes none of the usual suspects apply.
In a web terminal or SSH type 'losetup'. In my case it showed:
root@Tower:/etc/rc.d# losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/cache/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512The problem is that docker.img is still mounted. Note that in my case is it on /dev/loop2
Then run `/etc/rc.d/rc.docker status` to confirm that docker has stopped:
# /etc/rc.d/rc.docker status status of dockerd: stopped(It should be stopped, since you were in the process of stopping the array. But if Docker is still running, you can type `/etc/rc.d/rc.docker stop` and wait a bit, then run status again until it has stopped.)
Then to fix the problem, type:
umount /dev/loop2(use whatever /dev/loopX docker.img is on, as noted above)
Once that is unmounted, the array will automatically finish stopping.
We are looking into a fix for this, but it would help if we could reliably reproduce the problem (it has only happened to me once). If anyone is able to identify what it takes to make this happen I'd appreciate it.
sitting here tearing out my hair trying to figure out why i was stuck with the unmounting drives.... low and behold this solved the issue on 6.12.3...
-
I apologize for the delay in getting back to this. I drive truck and am gone from the house 2-4 weeks at a time.
I am starting to believe this is a motherboard or bios issue. Currently updating bios now, but I took the PCI card out and stuck it in an old pc and tossed unraid on a fresh usb drive and it booted just fine and detected the drive(s) attached to the PCI card. this lets me know its not the card or unraid issue. just gotta find out why my server doesn't like it... -
Thanks for the info, I'll look into getting the bios updated and trying a different slot
-
23 hours ago, JorgeB said:
Can't see the chipset but looks like an Asmedia card, it should be supported, you can post the diagnostics (tools -> diagnostics) to see if there are any clues on the problem.
Apologize for the delay, work had been hell this week..
Appreciate any help on figuring this out.
-
3 minutes ago, JorgeB said:
Can't see the chipset but looks like an Asmedia card, it should be supported, you can post the diagnostics (tools -> diagnostics) to see if there are any clues on the problem.
Yeah Amazon into said ASM1061
I'll get the diagnostic uploaded
-
Howdy fellow unraiders, just started using unraid (6.9.x) about a month ago and really enjoy the software. Just wondering what the best PCI-e card would be to increase disk count. I purchased two cards off Amazon as one of the questions on the item, asked if it worked in unraid and someone replied yes, but I can't seem to get unraid to detect they disks attached to it.. bios can see the drives attached, windows can see them, I can even boot windows from the card, but unraid doesn't see drives. Looking in tools>system devices, I can see the PCI card.. below is the card(s) I bought
I don't know if it's just limitations of the cards or unraid, hoping someone could point me in some direction. Thought about just doing a SAS card with SAS to Sata cables, just not sure which to go with.
System specs below;
Asus ROG Strix X470-F Gaming
AMD Ryzen 7 2700X Eight-Core
16Gb Corsair Vengeance
4x4TB HDD
1x500GB HDD
1x240HB SSD
[6.12.2] Array stop stuck on "Retry unmounting disk share(s)"
in General Support
Posted
i had a terminal window open, but it was on the default location ~: i'll try out the plugin and see if that helps..