kzisme

Members
  • Posts

    13
  • Joined

  • Last visited

kzisme's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Sweet - ended up ordering a new SAS breakout cable, swapped it for the old one, and rebuilt the drive (since I didn't realize there wasn't a different way to make a disk go from disabeled ---> Enabled) After the disk rebuild - all is well. I suppose those errors were specifically about the cable in this case. I appreciate the help and guidance!
  2. I have also swapped out my breakout cable for a brand new one and the disabled drive persists. Is there a way to "reset" the drive status? The previous rebuild on-top of itself also didn't fix it
  3. Here is the latest dig + smart test after a short+long test. HUH721008AL4200_7HK7269F_35000cca257b5f584-20231231-1424.txt tower-diagnostics-20231231-1425.zip
  4. Gotcha - I wasn't sure the amount that "should" take up. I re-seated the cables to the drive twice, and rebuilt the drive on-top of itself and the problem persists. I will try swapping cables with another drive tomorrow (I use breakout cables like this: https://www.amazon.com/gp/product/B013G4FEGG/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1), and also read somewhere that the crc errors that I am seeing are typically (almost always) cable related. I have attached a new diagnostics and SMART report from the rebuild as well - if this adds anything. I'm just trying to determine if it's a cable issue, a drive that needs replaced, or something else at this point. HUH721008AL4200_7HK7269F_35000cca257b5f584-20231225-2251.txt tower-diagnostics-20231225-2250.zip
  5. When verifying if a disk's contents are "ok" what is the best way to go about checking? The unRAID dashboard shows 55.8GB of storage is taken up on the disk, but when checking the web based file browser, and via the terminal I don't see any contents inside. Does unRAID take up disk space inherently (or in some non-standard way) that can't be seen via terminal commands or the dashboard file browser? EDIT: - It seems that is may just be the underlying filesystem, but just wanted to verify.
  6. Hello, just noticed that one of my array drives is showing a red "X" next to the drive and states that it is disabled and the contents are emulated. I have checked the cables (I only noticed it after installing another drive so thought it could be cables), and ran some SMART tests (main page says it is passing). Is there a certain way to tell if this device just got into an incorrect state, and needs formatted+parity rebuilt? I'd like to be able to know if I should remove+replace this drive. I have attached my current SMART report for the drive in question as well as my current system diagnostics. Please let me know if there is any other relevant information I could have missed. HUH721008AL4200_7HK7269F_35000cca257b5f584-20231223-0019.txt tower-diagnostics-20231223-0010.zip
  7. Thanks! That worked like a charm after spending some time with other settings. It did also prompt me for a login - which I used my Windows10 user account details (hosted on my unraid) and it worked.
  8. Thanks for the input! This was my issue as well...still not sure of the exact reason because I've only ever updated via GUI.
  9. Hello, After my last server reboot I am now unable to start my Windows 10 VM that was previously working. The current error when I attempt to start the VM is: Cannot access storage file '/mnt/user/domains/001 Windows 10/vdisk1.img': No such file or directory I don't think permissions have changed on a reboot, and vdisk1.img does exist at that path. Any ideas on what might be going on? I have attached my system diagnostics. tower-diagnostics-20190615-0110.zip
  10. Alright - so I've re-added both cache drives for a pool of 2 devices, removed newly added Plex servers, and tweaked a few things. Manually ran the mover and all seems to be well now. I do however have all of my paths set the same, but I have my appdata set to prefer cache. Still not 100% sure what happened, but it was a huge waste of time.
  11. Hello! I recently purchased 2 500GB SSDs to use as cache drives. I assigned them to a pool (is this the best option? I want to make the most use of the space that I have) I only wanted to use the cache for writes from SAB, Dockers, and VMs possibly. I then wanted to try to use one as a cache drive, and make one an unassigned device to see how that might work out...when doing this all of my dockers seem to have gotten reset (the existing configs are still somewhere because I can still see my previous Plex server (it's just unavailable) My default appdata storage for dockers is: /mnt/user/appdata/ After looking into my cache drives there are existing dockers found at /cache/appdata/ (I didn't move these files to the cache manually) What would be the best way to go back to having my working dockers, and having an optimal cache setup?
  12. Updated! Thanks for pointing it out! Cheers!
  13. Hello - I was curious if there is currently an issue with the CA feed. I noticed there is mention of some issues in the past few days, but not this one in particular. I do have my DNS settings pointed at 8.8.8.8 and 8.8.4.4. I've rebooted my server once as well. My server does have access to the internet, so is there a way I can determine if it is something on my end that changed (I don't think so) or if something elsewhere is currently down? EDIT: Currently (without any changes on my end) CA is now showing without error....