Fuggin
-
Posts
273 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Fuggin
-
Eventually 2.0 USB keys won't exist so what will be the solution for 3.0/3.1 drives?
-
Based on what I have seen on discord alone, there has been a rash of USB drives dying prematurely. Few users have suggested allowing the Unraid OS to load on a cache drive or dedicated OS SSD thus removing the read/write frequency on the USB drive and just access it to verify license upon boot. Perhaps do a randomly timed license check to verify that someone doesn't try to move it onto another system.
-
Mover progress indicator and what files are being moved and a mover summary log (if enabled).
-
FYI....changing CPU Scaling Governor from Performance to On Demand caused kernel panics. At first I thought it was hardware issues but I swapped new hardware with older and known working hardware and was still getting kernel panics within a day of resetting the server. Changed it back to Performance and it hasn't crashed since. Using Supermicro mobo with E5-2600 V2 series CPUs and running 6.10.RC2.
-
Solved it on my own. Moved a backup of my flash drive super.dat and super.old to the unraid flash drive, did a new config again. All previous array drives showed up and the shrunk drives became unassigned. Odd...but a learning experience.
-
I wanted to shrink my array and preserved my array/cache pools (I did double check I had both selected). Removed my drives I wanted to shrink, booted into unraid and only my cache pool was preserved. I do have a backup of my disk assignments. If I assign the disks that were originally assigned, how do I know the data would still be there?
-
Ok...most of my drives are HGST and it still happens, so it appears to be kernel related then.
-
I am having the same issue. It's a known issue. Fixes are probably coming, either with the plugin or unraid kernel.
-
Got it working but I can't see any of the sensors. Using Supermicro X9DRL-3F/iF board. I have Supermicro X9 board selected but won't show anything.
-
I keep getting connection fail in the IPMI IP address field. I can log in through the browser no problem, but won't connect in unraid. Please advise.
-
Just using unbalance to move files around...keeps saying there isn't enough space even though I have 50TB of free space available.
-
As title says, for some reason I can't write files to the following disks: 9, 14, 16, 17, 18, 19, 21, 22, 23 10,11 are on the excluded list...gonna pull them soon. I have moved the disks to other slots in the server, checked all connections, check global shares, etc...diskspeed benchmarks the drives fine still can't write to them. Looking for ideas and where else to look. tower-diagnostics-20211117-1901.zip
-
Yeah then I am really confused...I know I didn't assign a data drive to a parity slot...I've done this before...it just doesn't make sense what happened. All my drives showed up...I assigned my new parity drives first because their serial numbers were unique and similar enough, then the rest were the data drives that were in the system already...I just when down the line and re-assigned them. I started the array, it asked to rebuild the parity drives and it went ahead and did so. It finished rebuilding overnight, I woke up and 48TB was gone.
-
So...I know what I did wrong...and I thought I have done this many times and never had problems. I hit new config in tools, added the larger, new parity drives, rearranged the physical locations of the data disks AND their order in the array..... Pretty sure that did the damage. Lesson learned...
-
Thank you. I am going to look into Sonarr logs and see if there was something there that caused the files to get deleted since it was mostly TV media files.
-
yes...
-
I am absolutely certain...My array was 97% full while it was rebuilding....it was almost done rebuilding when I went to bed. Woke up and blammo....array was only 60% full...it's just bizarre.
-
I never move them manually....it's all handled by sabnzbd/radarr/sonarr.... All I know is that all I did was install new larger parity drives and this happened. I am not worried about the data loss but I just need help knowing where to look and seeing what happened so I don't do it again. This is the first time since I started using Unraid (2012-2013-ish) that I have lost this much data. As for the img sizes...I don't know.....did that so long ago...
-
TV_Shows share...odd thing though, not everything in that share was lost...just about 10-20 files still remained. I looked through the files and can't find anything that would have caused their deletion...
-
I had it in maintenance mode in case I need to check disk integrities. Sorry...I started the array and redid the diags. tower-diagnostics-20211102-1322.zip
-
Well...crap...I didn't know that...ok...gonna leave it off from here on out... Anyways...any insight on what caused the data loss would be helpful...if the data drives are fine, can I still put my old parity drives back and rebuild the array?
-
Yes...my corrections were set on (I have always had it on, assuming the whole point was to write corrections on the array if there was a problem)....the timing of the upgrading the parity drives with my monthly parity scheduler messed it up I think....I've uprgraded parity drives before but this is the first time I have ever lost data as a result. Diags attached...thanks for the help. tower-diagnostics-20211102-1238.zip
-
I updated my dual parity drives and the parity was rebuilding when the scheduler happened to take over and wrote corrections to the re-building parity causing me to lose about half of my array data. Can I put the old dual parity drives back in and rebuild the array from them?
-
[Deprecated] Linuxserver.io - Scrutiny
Fuggin replied to linuxserver.io's topic in Docker Containers
Hello. App won't update the harddrives in my array even with the run command in the docker console. Still has 2 older harddrives showing that I removed. -
I deleted my cache pools and reinstalled them...this time one of them went to btrfs and the other went to xfs and now they both work. I still don't understand why.
