John_M
-
Posts
4,727 -
Joined
-
Last visited
-
Days Won
12
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by John_M
-
-
On 3/4/2021 at 8:14 PM, SeeDrs said:
Those commands will strip out the microcode.
-
At least one person who reported a similar problem had success by switching from legacy to UEFI boot.
-
Fixed in 6.9.1
-
Changed Status to Solved
-
47 minutes ago, Helmonder said:
If I want to make it work again I have to recreate the thumbstick and copy back my 6.8.3 files, then I have a perfectly working system.
Instead of recreating your USB device from scratch, what happens if you run the appropriate "make-bootable" script for your OS?
-
10 minutes ago, Xutho said:
i have a different issue
I suggest you create a new thread in General Help and include your diagnostics.
-
20 minutes ago, TGP said:
Why is there even a Spin down Button for the cache pool?
Because pools can contain spinning disks.
-
"Spin-down" of SSDs was removed from Unraid 6.9. See here.
Quote- avoid sending spinup/spindown to non-rotational devices
-
Ha! It looks like I revisited this page in the minute before Squid posted. I'll use his patch file. Thanks, both.
-
8 minutes ago, ljm42 said:
Then view the Tools -> System Devices page.
Yes, that's fixed it. Thanks.
-
-
1
-
-
1 hour ago, Cyril83 said:
It works but I lose my SSD cache drive.
This is mentioned in the release notes: https://wiki.unraid.net/Unraid_OS_6.9.0#Multiple_Pools
QuoteNote: A pre-6.9.0 cache disk/pool is now simply a pool named "cache". When you upgrade a server which has a cache disk/pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of config/disk.cfg and into a new file, config/pools/cache.cfg. If later you revert back to a pre-6.9.0 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache. As long as you reassign the correct devices, data should remain intact.
-
Have you tried to disable it in the BIOS?
-
I've just re-tested with Unraid 6.9.0 and the situation is unchanged.
I'll open a report on the Stable page.
-
Agreed. I'm seeing the same, also with a Samsung NVMe device. Maybe there's some special character in the string that's causing the problem.
-
13 hours ago, Mathew R. said:
The issue seems to now be specific to FireFox
Agreed. I'm seeing the same with Firefox 85.0.2 (macOS). It also applies twhen setting custom SMART parameters, as well as temperature thresholds. Chrome 88.0.4324.192 works fine.
-
Bonding is enabled by default, even if you only have one NIC.
-
1
-
-
Post your diagnostics zip.
-
Agreed. The Main page is correct but on the Dashboard only green seems to be used. FWIW, I'm using the White theme.
-
20 minutes ago, elmetal said:
wouldn't libvirt.img also benefit from this change?
Since its contents are mostly static, probably not very much.
-
You ought to reboot into safe mode and see if the disks spin down. If they do then some plugin is the cause.
-
1
-
-
Are you using UEFI boot or legacy? Whichever one you're using, have you tried the other?
-
Probably the btrfs performance regression noted in the 5.10 kernel, which was recently fixed in 5.10.8. https://phoronix.com/scan.php?page=news_item&px=Linux-5.10.8-Released
-
34 minutes ago, TDD said:
I didn't manage to capture the logs
Without diagnostics to prove otherwise I'd assume it's a cable problem - either data or power to the drive.
Wrong free space reported in shares tab.
in Stable Releases
Posted
I'd say that you have an empty directory called "Work" in the root of Disk 3 and therefore the reported available free space is the sum of that on Disk 3 and Disk 5. I'm guessing that directory was created when you first created the Work share and that you later changed the share to include only Disk 5.