Good day fellow Unraiders! 

 

I have been having some problems with unraid recently, I noticed issues after the latest update to 6.12.3, I am not able to cleanly shutdown my instance of Unraid and it is not due to the docker.img not unmounting, I have tried looking through all of the issues that have been posted here before but I cannot seem to figure it out. 

 

The symptoms: when I want to reboot or shutdown, I manually stop the array, it is stuck in "Array Stopping - Unmounting Disks" and I usually run out of patience after about 30 minutes of this and try to look for the issue. I checked the /loopX mounts which /boot/bzmodules and /boot/bzfirmware are mounted and docker.img is not mounted. I do not know if that is normal.

 

Also, after I power on unraid, the normal parity check starts and passes without fault. However 2 reboots ago, I did have a drive that I needed to fix using maintenance mode and "Check file system" option. This was due to having a SMB connection to that drive in the array.

 

On another note, I am not sure if it is related, but after unraid boots, I have an error related to vfio bindings which prevents VMs from auto starting, I do not have any VMs that auto start. Not sure what that is about and I do not have any bindings, I used to but I do not anymore.

 

The Diag logs I pulled now, which is a long time after the unclean shutdown, the shutdown occured on the 18 Aug @ 17:00.

 

Any advice is welcome, thank you!!

corvax-diagnostics-20230822-0732.zip

Syslog in the diags starts over after every reboot, you can look in the flash drive /logs folder for the previous shutdown diags, they should be saved there if it was an unclean shutdown.

Hello! 

 

The only other 2 are from december of last year and not the latest dirty shutdown. I do not know if they will help but I have attached them below.

 

I did check the first attachment and it does seem that the logs are there for the latest dirty shutdown.

 

Thank you!

corvax-diagnostics-20221227-1120.zip corvax-diagnostics-20221227-1242.zip

15 minutes ago, Aidzer0 said:

the logs are there for the latest dirty shutdown.

That log covers Aug 18th to 22th, but there's no shutdown attempt logged, if you just stop the array now, does it stop?

Just now, JorgeB said:

That log covers Aug 18th to 22th, but there's no shutdown attempt logged, if you just stop the array now, does it stop?

I am trying now. Do I need to be monitoring anything specific?

Post the diags if it does'n stop, before rebooting.

It just stopped... So quickly... no problems...

I am very confused as to why this would happen.

 

For more information, I checked Open Files add-on, there was nothing open on any drive besides the regular System files. I also checked the losetup command and only the /boot/bzmodules and /boot/bzfirmware were mounted. I had no terminal sessions open or anything like that. So I am very lost as to why this would happen.

 

Sorry to open a post for nothing and wasting time... And thank you for the help!

I just started the array and this error popped up again: 

The logs show this:

Error: Vendor:Device 1b73:1100 not found at 0000:02:00.0, unable to bind device

 

That device ID is not listed in the system devices. So I am not sure what it is.

Edited August 22, 20232 yr by Aidzer0

Delete that entry from /boot/vfio-pci.cfg.

34 minutes ago, JorgeB said:

Delete that entry from /boot/vfio-pci.cfg.

Legend, thank you, that worked. Also, I just rebooted the system 3 times in a row without failure. 

 

I do not know what was causing the issue but it is resolved now. (It was not the bind because it successfully rebooted before I removed the binding)

 

Thank you so much!