dnoyeb

Members
  • Posts

    136
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dnoyeb's Achievements

Apprentice

Apprentice (3/14)

10

Reputation

  1. Just wanted to chime in after running this release since it came out. I was crashing every few days and getting concerned I had issues with ram or cpu.. then this release came out and viola! No more crashes (knock on wood). I do remember seeing some macvlan errors from time to time, and now it's all gone. Thanks so much for this release and the fixes.
  2. btw few examples of people getting it claimed back in this other thread: I for one had issues since my laptop and the server were on different subnets; was able to get it claimed via the web login for the server itself after getting on the same subnet and removing the variables from the xml file in the data folder as outlined in that other thread.
  3. Ya I think the complexity for my setup was the different subnets and firewall rules between them. Was unable to do the curl command successfully. Anyways, looks like we have a few successes now in this thread with ideas for others to try!
  4. Ok, so just in case anyone has a similar issue to me... let me explain what I did. I followed the directions above and removed the 4 parameters/variables from the xml file from the app data folder. started up the docker and then was able to reclaim via the general settings. While you would THINK this would be easy, my laptop was on a different subnet than the server and I NEVER got the claim option in general. Once I thought about it and realized the laptop was not on the IOT network; I swapped over and now have the claim option. So, just in case anyone else is running multiple networks at their house, make sure you jump on the same subnet. Not sure why that made a difference but it did. Perhaps I didn't need to edit the xml file, so first try joining the same network just in case you run an IOT network like I do.
  5. I dont' have an option to do that.
  6. In the same boat... argh... anyone successfully get the claim token and stuff to work?
  7. lmao, ok, is that something that should / would have changed when upgrading? Thanks
  8. Upgraded my test machine to the latest rc1 to see how it would do; very basic system, only like 2 plugins. Just noticed docker failed to start; and when looking around; I see a cache mnt point and a disk1; but no actual "user" anymore... of which I have a feeling is keeping docker from running if I had to guess since it doesn't have a spot for its files now. Anyways, diag attached. tower-diagnostics-20210813-0950.zip
  9. thanks man. ok so then really there is only one drive that has any "real" errors to it, which are reallocated sectors. will keep an eye on things going forward and see if anything increases; pulled a diag from 2019 and that same drive had the same 8 reallocated sectors... so probably not leading to the issue. Thanks again so much for your help. Time will tell.
  10. ah, actually disk 7 has reallocated sectors. Sounds like candidate to replace... Now to figure out how to upgrade parity to 12tb (from 8tb) and not lose my parity; then use the 8tb parity drive to become disk 7.... also strange is just about every newer drive in my system show signs of "Raw read error rate" and "Hardware ECC recovered"... not really sure what to make of that (haven't really looked at that before to know if it's recently increased or not). Only that one disk 7 has reallocated sectors however.
  11. Guess I'll start with doing the file system check on that device... Other than that; at a bit of a loss since the pool's disks don't show any errors or smart flags. This thing has been such a rock for so many years!
  12. What's strange is that day, the system was just completely locked up. first time in the 10 year's I've had the system that it has happened.... That and it did a parity check on startup and didn't find anything.
  13. Needing a little help; got an email today about 3645 errors; ran it again since I realized my monthly check wasn't setup to auto correct. Same number, shows that it fixed it. This system has been running for almost 10 years at this point; migrated to new mobo/cpu years ago, but there are drives in there since 2012. Anyways, not sure what to make of it, since in the gui it doesn't show any drive specific errors... I did see in my log that the cache drive has some sort of metadata store error and recommends repairing; but don't see how / why that would result in parity errors. Can someone take a peak at the diag file and advise on how I can tell if there is a drive needing to be replaced? I've got 2 extra 12tb sitting in there just waiting to be swapped into the array (precleared already)... Thanks! unraid-diagnostics-20210517-1039.zip