-
Posts
49 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by ds679
-
-
At the behest of SimonF - here is an issue that I've found (and only corrected by reverting back to 6.9.1)
I recently got my first HBA (LSI 9305-16i) with SAS-to-4xSATA cables to be able to add more SATA drives to my rig...the drives are a mixture of:
- ST8000VN004
- ST4000VN008
- WDC_WD60EFAX
I did the hardware change AND the update to 6.9.2 at the same time and noticed that none of my drives would spin-down automatically (which they had earlier) and thought it was due to the change in hardware. I could force the drives and they would spin-down but not automatically after the set '15 minute' timeout (had 'Enable Spinup Groups' also set to 'No'). After looking at the logs - I would never see spindown requests?
Reverted back to 6.9.1 and it automagically worked with no additional changes.
HTH and looking forward to 6.9.3?
-dave
-
19 minutes ago, limetech said:
@CHBMB, @aptalca, @memphisto, everyone else who thinks I somehow disrespected anyone here,
Somehow this is being blown waaay out of proportion, largely due to misunderstanding I think.
@Tom - you and the team have worked hard and we all appreciate it! but the issue is Respect and Communication (which sounds like there was none given). THAT is a punch in the face! Would you want to work that way for someone/something?
- 3
-
Fair changes.....thanks!
-
7 minutes ago, ljm42 said:
So you're saying there is a bug in the Grammerly extension that causes it to modify the Unraid webgui even when it is whitelisted? That doesn't seem like an Unraid issue...
No...because the exact same extension worked BEFORE the update and all previous updates....
Say it with me:
Old Code worked....ok
New Code breaks on same setup.....that's a bug in the code-change
What is so hard about that? -
10 minutes ago, ds679 said:
narrowed it down to Grammerly and while even white-listing the site - it (the original issue of 'whiting out' after 10 seconds) still occurs.
-
Hi LJM42,
Thanks for the follow-up...and I understand what you're saying but that isn't the issue. All earlier versions worked on this same setup/extensions/pi-hole setups/etc.....once this new version came along; the issue began.
An earlier post narrowed it down to Grammerly and while even white-listing the site - it still occurs. The only 'hack workarounds' are to open incognito (which requires a new log-in)...or totally remove the extension (which worked fine in all previous versions). -
I guess I would consider that more of a 'hack work-around'...but there is still something different/new in this release that is a 'bug'
-
I appreciate all of the help - but this issue still is persistent & repeatable....and has not occurred with other releases. There is still an issue with the current codebase.
=-dave
-
Thanks for the thoughts/info. Both the IP and the DNS name of my server are whitelisted.
What is strange is that it worked pre-update; so it has to be some implemented changed. The only other thing is that it is contacting some AD server (and my Pi-Hole is catching it). I've also white-listed the server there - why would it be contacting some AD service?
Still searching for clarity,
=dave
-
Ahhh....good idea...and...drumroll...IT WORKS! I'm in the terminal window and no blanking/whiting out!
Were you able to go 'one by one' and see which one (or was it the whole 'shields' part) was causing the problem?Thanks for the idea!
=dave
-
Howdy - I listed the Chrome version in a response....but thought it worth trying in others. IE & Edge - didn't work. But why not Chrome? Worked great pre-6.8.0?
Appreciate all the hard/good work!=dave
-
Appreciate the 'sanity' check!
-
I've cleared site cookies (using Chrome Version 78.0.3904.108 (Official Build) (64-bit)....made sure of the Whitelist exception in AdBlock.
Tried in Microsoft Edge....the terminal window opens IN White (not even a chance to have a terminal like Chrome)
Is nobody else experiencing this?
Unraid OS version 6.10.0-rc3 available
-
-
-
-
-
in Prereleases
Posted
After updating, I received an error from 'Fix Common Problems'