[Boot frozen after updating to 6.11.2]

Try recreating the flash drive as a new install with whatever version from the Download page, then copy config folder from your backup.

 

Boot from USB2 port.

[The update is not possible]

That will not be enough RAM to do the upgrade from the webUI. It is probably not enough RAM to run Unraid. What version were you using?

[Shouldn't be possible for log file to crash system]

Unless you have syslog server setup to mirror log to flash, log isn't on flash. It is in RAM just like the rest of the OS. And the amount of space it can take up in RAM is limited and can't cause crash.

 

Are you actually filling flash drive? That would be very unusual. Not recommended to write to flash drive. and the OS doesn't normally write to flash except to record settings you make in webUI so they can be reapplied at boot.

 

Even if mirroring with syslog server you should only do that for a limited time to capture log after crash.

 

Are you sure you don't have something filling rootfs?

 

When you have the problem, what do you get from command line with this?

df -h /

 

Also, please amend your report so it follows report guidelines. At the very least test in SAFE mode and include your diagnostics.

 

 

[Unraid 6.11.5 - SSHD says started in boot log but, doesn't actually start]

 

[6.11.5 docker icons come and go (page refresh)]

On 1/4/2023 at 12:13 AM, gmight said:

If I remember correctly

FAQ linked above already explains.

 

Also wiki:

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

[Wrong Detection of "protected" Share]

Did you originally create that pool as raid0? Or did you create it as default raid1 then convert it to raid0?

[Wrong Detection of "protected" Share]

4 minutes ago, Hexenhammer said:

share is empty

What happens if you put something in the share?

[Wrong Detection of "protected" Share]

14 minutes ago, Hexenhammer said:

This is cache Only Share

Which simply means write new files to the designated pool, and don't move any. Doesn't tell us anything about where current files are located.

[Wrong Detection of "protected" Share]

I can think of other scenarios, but instead of guessing what you have, post diagnostics as explained in the report guidelines I linked.

[Wrong Detection of "protected" Share]

How do you know that share isn't all on the array?

[Wrong Detection of "protected" Share]

 

[6.11.5 docker icons come and go (page refresh)]

df in diagnostics didn't work for some reason.

 

What do you get from command line with this?

df -h

 

[Duration time is wrong]

Diagnostics required for bug reports. Technically, testing in SAFE mode is also required.

 

 

 

[BTRFS Pool Disk Detection Problem]

Not clear this belongs in bug reports, and 6.11.5 is not a pre-release, so definitely in the wrong place. In any case, all bug reports require diagnostics. I may close this after copying it to General Support.

[[6.9.2] Parity Drive will not spin down via GUI or Schedule]

2 hours ago, Ralf. said:

I can report the same issue

 

On 9/22/2022 at 8:20 AM, trurl said:

Post diagnostics so we can see if there may be some other reason.

 

[Bug in 6.11.5]

 

[[Fixed 6.11.4] Upgrade failure to 6.11.5]

You still need to get to the bottom of how you filled rootfs. One possibility is a docker host path that doesn't specify a user share, disk, or pool. Any path not on mounted storage is a path in rootfs, the RAM reserved for the OS. If you fill rootfs, the OS won't have room to work in and lots of problems can happen.

[[Fixed 6.11.4] Upgrade failure to 6.11.5]

You seem to have filled rootfs somehow. Reboot and posts new diagnostics

[[6.10.3] Boot hangs and random freezes upgrading to 6.11.X]

The reason I was asking for those command line results is because I am wondering if you have something misconfigured that is filling rootfs. Actually, all we really need to see is the result of

df -h /

These latest diagnostics has a little more used than the result you posted, and those other diagnostics showed as much as 16% of rootfs used. Not necessarily a problem unless it gets close to 100%. The OS is in rootfs (which is in RAM) and if it fills the OS has no room to work in.

 

Quote

 created a new 6.10.3 from scratch and copied over the directories from my backup zip file

Which directories? All you need is the contents of config folder from flash to get your configuration back.

 

Disable Docker and VM Manager in Settings, reboot in SAFE mode, and see if it is stable like that.

 

[[6.11.0, 6.11.1, 6.11.2, 6.11.3] Diagnostics collection missing some (or all) shares]

Working for me on 6.11.5

[[6.10.3] Boot hangs and random freezes upgrading to 6.11.X]

What do you get from command line with this?

df -h

 

[[6.10.3] Boot hangs and random freezes upgrading to 6.11.X]

16 hours ago, apmiller said:

I'm 90% sure it was 6.10.3 from the start but there could be a chance I was 6.11.1.  

Whichever version it was, was it running OK before the upgrade?

[[6.10.3] Boot hangs and random freezes upgrading to 6.11.X]

You have appdata on 2 different pools. Is that intentional? Also, system share has files on the array.

 

[[6.10.3] Boot hangs and random freezes upgrading to 6.11.X]

Quote

In early October I upgraded to 6.11.3 and have nothing but issues since

What version were you running before that?

Quote

roll back to 6.10.3

This sounds as if you were running 6.10.3 before. Was 6.10.3 running OK before the upgrade?

[[6.11.0, 6.11.1, 6.11.2, 6.11.3] Diagnostics collection missing some (or all) shares]

And 6.11.3

 

unserver-diagnostics-20221108-2152.zip