Everything posted by FlamongOle
-
[PLUGIN] Disk Location
Update 2020.03.04 Commit #139 - FEATURE: Added the ability to turn off scanning of device during a plugin update. If it's disabled it will rely on manual updates (Force Scan All) and S.M.A.R.T update schedules. (This will make updates and reboots faster though) Commit #138 - FEATURE: Added possibility to adjust the size of the preview/dashboard layout. @CorneliousJD something for you 😛
-
[PLUGIN] Disk Location
I might add an adjustable factor in the future, I'll list it on github meanwhile.
-
[PLUGIN] Disk Location
They are directly related by a factor of 10x the size. The idea is that you should adjust the size of the "Devices" page, and not the "Layout" display.
-
[PLUGIN] Disk Location
Update 2020.03.03 (probably 3rd somewhere in the world already) Commit #136 - IMPROVEMENT: Added help text for the "System" tab (also renamed the tab from "System Files"). Commit #135 - FEATURE: Added an "Undelete" button under "System" tab for undeleting manually deleted devices. @mistah ..or you can use this new function when you update the plugin 😛 The buttons under "System" are only available when it's possible to use them, otherwise hidden if there's nothing to do.
-
[PLUGIN] Disk Location
If you are sure you have flagged it for deletion earlier, then yes it is possible. But you should rather know some SQL basics. Make sure you have ran the "Force Scan All" button first, I don't remember if that will re-add it if it is found or if it's completely ignored because of the flag. SQL: First, backup the entire database: cp /boot/config/plugins/disklocation/disklocation.sqlite /boot/config/plugins/disklocation/disklocation.bak To check for the deletion flag (if nothing is listed the flag does not exist and there's nothing more you can do here): sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select device,devicenode,model_family,model_name,status,hash from disks where status='d';" To undelete a specific device, type this and copypaste the HASH from the list to be undeleted (do not include < >), this will put the device under "Devices not found or removed" under the "Drives" tab, where you can add or delete it manually from the list: sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "update disks set status='r' where hash='<INSERT HASH HERE>';" Option 2) To undelete all devices (I might add this to a function later) Button added under "System" Finally you wanna run "Force Scan All" to make sure it detects the devices.
-
[PLUGIN] Disk Location
Update 2020.03.02 Commit #133 - IMPROVEMENT: Removed the "Reset" buttons as they make people confused about its function. They only resetted the changed input in forms, pure html reset.
-
[PLUGIN] Disk Location
Guess you reached pulling the new update
-
[PLUGIN] Disk Location
Update 2020.02.28 Commit #131 - BUG: A php comment section was accidentally pasted into an SQL creation variable, causing an update to fail (affected version: 2020.02.23). Commit #127 - MAJOR ISSUE: Disk Location uses a cronjob for storing data in a database file located at the flash device, and an hourly cronjob might have exhausted some flash devices. A new setting is available where the default is now set as "Disabled", however, "Daily" (and longer periods) should still be quite safe to use. It's stored on the flash device because the database contain information about old devices as well, which is neat in case of a major device failure and you just wanna know how long it lasted. Everybody is strongly encourage to upgrade ASAP! Also: please use the inline Help function for more information - it works! People with Unraid earlier than 6.7.1 should upgrade using the development branch (or simply update your Unraid altogether). I hope it's none.
-
[PLUGIN] Disk Location
Looks like a php comment section was accidentally pasted into a SQL creation variable. Will fix asap.
-
[PLUGIN] Disk Location
-
[PLUGIN] Disk Location
Update 2020.02.23 Commit #127 - MAJOR ISSUE: Disk Location uses a cronjob for storing data in a database file located at the flash device, and an hourly cronjob might have exhausted some flash devices. A new setting is available where the default is now set as "Disabled", however, "Daily" (and longer periods) should still be quite safe to use. It's stored on the flash device because the database contain information about old devices as well, which is neat in case of a major device failure and you just wanna know how long it lasted. Everybody is strongly encourage to upgrade ASAP! Also: please use the inline Help function for more information - it works! People with Unraid earlier than 6.7.1 should upgrade using the development branch (or simply update your Unraid altogether). I hope it's none.
-
[PLUGIN] Disk Location
I for sure won't do the RAM approach, but the other options I gave should eliminate the problem. I have myself ran this without issue since the cronjob was added, I run on a Kingston USB 3.0 DataTraveler 50 32GB. I expect you might have a device with less storage? For curiosity only, I will still fix the problem one way or the other.
-
[PLUGIN] Disk Location
Alright, I'll make two additional features for the future: 1) Adjustable cron times, will probably keep it at disabled, 1 hour, 24 hours, weekly, and monthly. 2) Movable database to another device Or I might consider digging through Unraids lack of documentation to implement their own SMART data into the plugin, meaning less writes to the database (maybe even none during normal operation). Never thought about how much it can actually write, really. Temporary workaround to disable it: rm /etc/cron.hourly/disklocation.sh NB! This WILL leave SMART data for the plugin static/old and all changes for the system must be run by "Force scan all"
-
[PLUGIN] Disk Location
It updates the SMART data so you'll get the feedback if it reports a SMART error, and also simply updates the "power on hours" etc. The writes are so minor that I wouldn't worry about the flash device. Earlier it was only accessed when you entered the plugin, but that made it quite slow to load and would've been a pain for the dashboard plugin as well. I can of course consider make an option to disable update writes, but then features will be lost, or simply add a custom update time.
-
[PLUGIN] Disk Location
Where? Under "Configuration" you should, under "Tray Allocation" you shouldn't. The point is that it shouldn't mix up Unraid assigned devices with unassigned, but you can still manually force a custom color. Unless you choose the default colors specified under "Configuration". If you choose any color specified under "Configuration" in "custom color" it will reset like choosing "Gray/Empty" color.
-
[PLUGIN] Disk Location
Update 2020.02.19 Commit #124 - MINOR ISSUE/IMPROVEMENT: Added a "Reset All Color" button with following informative text to clarify the coloring of devices.
-
[PLUGIN] Disk Location
You have the same colour for unassigned and data drives. The colour picker always list the chosen colours first and in this row from the left: parity, data, cache, unassigned, empty. The extra two added ones are the default colours for data and cache (which is replaced by your custom colour). The behavior is expected
-
[PLUGIN] Disk Location
Update 2020.01.27 Commit #122 - IMPROVEMENT: "Force scan all" should check all drives in the database except manually deleted (hidden) ones. Earlier scanned just assigned devices, leaving some removed devices in the assignment list instead of "not found" list. Commit #121 - IMPROVEMENT: Better use of FontAwesome, PNG icon files removed.
-
Corsair RMi, HXi, AXi PSU Statistics - CyanLabs's fork
Oh sweet! I was thinking about creating a plugin/dashboard thing for this tool as well. Glad I didn't have to do it! My Corsair HX1200i is satisfied Looks good!
-
Anonymize diagnostics is not anonym
I decided to just look through the entire diagnostics file to check if it really is anonymous. It is not: if the "mover" logging is enabled, it will write the entire move with path and filename into the syslog and the diagnostic does NOT anonymize this data. Quoted from the diagnostic page: Yes, it says it will backup the syslog - but I expected it to run through an anonymize filter first. This is a serious security flaw for the users, not good!
-
NFS is about useless in Unraid 6.8.0
Every time I move a file from one location to another (from eg. shared scratch location (nvme) to a cached location (mec. disk)) within shared locations in NFS I constantly get stale file handles and the client drops out. This can be critical as some VM's uses the same mounted shares as I have in general bad luck with write permissions with 9p over VM's. But it's quite annoying for my regular workstation as well as I suddenly looses access due to stale handle when a "Mover" has been running. I dunno if this is only related to cache shares (but it might look like), or if it happens when things have changed on one of the disks in general. The problem did not happen under 6.7.x or earlier. I have tried fuse_remember values of standard 330 (which I used with success in earlier versions), 900 to just try a higher number, and also -1 as I have plenty of memory - though I'm not sure if I want that kind of cache to last that long. Honestly can't find any proper answer for what this actually does anyway. It makes Unraid almost entirely unusable for me, and I can't figure out why this suddenly happens. I hope it's something wrong on my end, but I haven't really changed anything the last 4-5 years (even before my Unraid time). odin-diagnostics-20200101-2012.zip
-
[PLUGIN] Disk Location
Update 2019.12.30 Happy new year! Commit #119 - MINOR ISSUE/BUG: Fixed dropdown list in "Tray Allocations" to show all custom colors. Only "Empty color" can be now chosen for resetting to default colors, for simplicity. @ICDeadPpl: this should simplify it for you
-
[PLUGIN] Disk Location
The default colors are added, just choose one of the first 4 colors (1=parity/2=data/3=cache/4=unassigned) and it should reset to default (even if you choose the wrong one). Else bug discovered as not all colors are added to the list on that page, but a reset should already be possible.
-
[PLUGIN] Disk Location
Update 2019.12.24 Happy holidays (for real this time)! Commit #117 - MINOR ISSUE: Fixed LED for empty tray which was misaligned.
-
[PLUGIN] Disk Location
Update 2019.12.23 Happy holidays! Commit #114 - IMPROVEMENT: Changed the color to use the default Unraid class instead of regular "green" and "red" Commit #113 - IMPROVEMENT: Added minor tweak to the LEDs, mouse over and design should work better in vertical mode. Commit #112 - MINOR ISSUE: Added forgotten stripslashes and htmlspecialchars for the group name, quotes etc. should now work.