nos0n3

Members
  • Posts

    10
  • Joined

  • Last visited

nos0n3's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Suffered form a power trip, now I need help with log in issues and qbit writing old completed files back into the cache (4.3.9-2-01) 1st - im running into issues login into the webgui, i have the login saved on the web browser so i know its right and hasnt changed since setting it up. every time i try it out, i get invalid username or password. Using the default admin login does let me in but the everything is cleared out, doesn't show any torrents or files at all. I have tried resetting the default log in but my config file looks very odd and might have been corrupted some how. 2nd - i somehow got the same problem that was occurring in 4.4.0 that was causing all files to be written to the cache drive instead of the disk. was a while since i found the solution that fixed it but idk why it happened as 4.3 was one of the fixes. should I just pull the latest and try out the fixes for 4.3 after?
  2. IS anyone else still having trouble after rolling back to 4.3.9-2-01 with files not moving from cache/appdata? Im pretty sure i have checked all folder paths and permissions and they all seem to be correct to the way I had it before. appdata share is set to "cache=prefer" but mover still doesn't transfer data to the disks. I even tried transferring some of it by hand but was only able to free up 30 GB. Setting appadata cache=yes does make mover transfer to disks but afterwards if I set it back to prefer the files are moved back to the cache. Is there a way to tell the docker to not associate the files with the appdata? Should i delete the docker image? im also not sure if that will delete some the files stuck in appdata folder. Have almost 1 TB of some old torrents that are pretty much dead. Heres the run command
  3. i have two previous diagnostics. One from when i first noticed the error, the other I believe is when i first rebuild disk 3 and before moving around the HDDs in the enclosure. Seems my memory is off. must been after both disks were rebuilt dlnqnt-diagnostics-20210810-0944.zip dlnqnt-diagnostics-20210702-0210.zip
  4. diagnostics attached. I had 2 disks become disabled in my array. I ran an extended smart tests on both disk 1 & 3 and both completed just fine. I bought two extra HDDs of the same size but i decided to reuse disk 3 and install one of the new HDDs for disk 1. I started with a rebuild of disk 3 by stopping the array, removing disk 3 from array and spinning it back up. Stopped the array again and added back in disk 3 to start a rebuild of the array. After Disk 3 completed. I stopped the array, removed disk 1 (1eg8sh27) and replaced with new HDD (vchwmjgp) Started back up the rebuilt with the new HDD but during this time i noticed Disk 3 was unmountable. I see the format button, but if im reading this right, this will reformat the disks and start everything over. I don't mind redoing the rebuild but I'm afraid of it reformatting both drives at the same time and then me loosing data in the process. i still have the old Disk 1 on hand, along with a new and precleared 10tb HDD replacement. I would love to know if there is a way to use them to rebuild everything safely or if just formatting and letting unraid rebuild everything is safe enough. also During the replacement i also noticed some of my disks were out of placed physically in my servers so i arranged them to the ordered that is shown in UnRaid GUI. Which i believe is why disk 7 is showing as not installed. I wanted to know how to fix this. I have also attached the smart tests for the original disk 1 and disk 3 if it helps. dlnqnt-diagnostics-20210811-1318.zip dlnqnt-smart-20210808-0159.zip dlnqnt-smart-20210808-0201.zip
  5. Alright. Rebuild is finished and everything seems to be running without issues. next step is just rebuilding the dockers. thank you so much for your help!
  6. ok replaced sata cables and restarted rebuild. seems to be holding at ~160 MB also how were you able to find which disks where the ones assigned to those ata slots? i think last time i had this error i spent a couple of hours trying to find where the ata matched with anything remote to a disk number/serial
  7. Even with parity rebuild running? also this error had come up before once with two separate HDDs i replaced about month ago, which i had already replaced the cables to. will have to check the box and match serials to confirm. I have a feeling it might be the actual SATA ports on my MB or on the enclosure.
  8. Weird, between my last post and now, it shot back up to 140 MB. according to syslog.last200 seems ata 2 & ata3 are the problem. dlnqnt-diagnostics-20200925-1300.zip
  9. I'm an idiot, this is the original thread i followed for the flash drive and parity rebuild. OK then. no other choice but to start the rebuild of parity I suppose. Though Ive noticed the speed of the rebuild fluctuates between 500KB - 1.5MB is this normal? i thought it would be faster, since at the beginning it said estimated finish to be ~16 hours (didn't pay attention to speed at the time) I don't think i do, i was hoping maybe I might have stored it on the server itself but I cant seem to find any evidence of it. I didnt have anything too complicated, so i think i should be fine.
  10. A few nights ago my server had started ruining slow and was getting bad bread errors on my sub flash drive and ended up with dead USB drive. I started following the steps in this thread : (EDIT: linked correct thread.) But in my situation I'm ruining dual parity and when trying to start the array with my correct parity drives and "parity is already valid" checked i get this warning Does this mean all data disks MUST be assigned in the original slots before the array went down? or just that all data and all parity disks be assigned accordingly? would be just safer to rebuild parity? also is there any way i am able to restore previous dockers and settings before my server went down? i believed i had closed to 100 GB of app data and other running services in my cache drive.