MandicReally

Members
  • Posts

    17
  • Joined

  • Last visited

MandicReally's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I honestly cannot remember if I've swapped cables. I'll make up a fresh CAT7 cable for it and see if that changes anything, thanks. An obvious thing that totally slipped my mind.
  2. Currently I have 2 Unraid boxes that are both using the same NIC, a "NICGIGA 2.5g" card that uses the Realtek RTL8125B chipset. I also have this exact same NIC in my workstation PC on Windows 10. One of my Unraid boxes disconnects randomly for no apparent reason. The other one, using the same NIC, is rock solid (as is my Windows PC). I've tried replacing the NIC in the unstable box, and it improved but has still had a few random disconnects. Searching here I've found some mentions of issues with this specific Realtek chipset on Unraid, but like I said, my other machine is rock solid with the exact same NIC. The unstable box is running an AMD Ryzen 5 3400G on an AsRock X570 Phantom 4 Gaming motherboard. The stable box is running an Intel I7-9700 on a Gigabyte UD Z390 board. I was able to switch the cable to my motherboard's onboard port and access the system to retrieve a log. It looks like I rebooted about 4 days ago from the last time this issue occurred. At this point I'm heavily considering swapping out the Motherboard for one that has an onboard 2.5GB port, but I'm concerned there would be a chipset issue with that then leaving me with no backup port to use... Any help is appreciated. syslog
  3. That’s kind of what I figured. Just didn’t feel like moving stuff around just to prove the theory only to delete it after. Thanks, ill try and figure out some file sizes to set limits.
  4. So I've just setup another Unraid box for my partner and have run into various issues I never remember having with my other builds. Right now I've run into an issue where the created Shares are limited in size to the size of the Cache Drive. The box has 5 - WD 4TB HDDs in it setup with 1 in Parity and the other 4 are the Array. There is also a 500GB NVMe SSD for Caching. All of the shares are set to "All" for the disks they have access to, and Cache set to either "Prefer" or "Yes". The "Media Library" one was stuck at the Cache size as well, I changed the Cache configuration of it, and wrote some data to it. That is all I did and it now sees the full 16TB of space it should be seeing. Am I missing something? Is it because the shares are largely empty (or darn near it)? Will this iron out over time? When I look at them via Windows Explorer or Mac Finder they show as only 500GB of Free space (or however much space is on the Cache drive at the time). Screenshots to show that the settings are the same between the Media Library and the "Ruby's Vault" Share but they show different spaces.
  5. So I'm setting up a second Unraid box on our network. I've got it all running and think it should be ready to roll. I can easily login by using a browser and accessing the GUI. Login and Password work just fine via that. However if I try to use Windows File Explorer, or MacOS Finder, I cannot login. Both get to a point where they provide me the login prompts. I enter the Username and Password, and fail to login. I've gone into the GUI and added new login & passwords for both myself and my partner. Those still don't work. I try the root login, no dice. The odd thing is I have the Log open and it shows no login attempts. I tried logging out of the GUI and purposely entered the wrong login. Then I properly logged in, and the log shows that failed and proper login. But the File Explorer login that failed? Doesn't appear in the log at all. Log file attached. The last entries are the Logins I just did, but within that time I tried to login via File Explorer and that isn't showing up. Am I missing something? All of my shares show as "Public", but I cannot get passed the login to the server to access any of the file directories. rubymine-syslog-20220822-1814.zip
  6. Yea I’m feeling like it’s gonna be my safest bet to just let it ride out the Parity-Check. Thank you for the input. If I can provide any more (or clearer) details, let me know.
  7. Here are some screenshots demonstrating what I'm seeing. As for the "new config" thing, I hadn't seen reference to that when looking up assigning new drives, so I didn't look at it until just now. Seems like maybe the way I should have gone. The Disk 5 that is in "error" has been that way since day 1 (well over a year now). I know I should have addressed it, but never have. It is a shucked 10TB WD drive so I never wanted to hassle with warranty replacement. I know, shame on me, but it has never hiccuped so far and clearly its getting used.
  8. I didn’t do a Parity Swap, I just unassigned my old Parity drive and assigned the new larger drive. Unraid rebuilt parity just fine. That’s exactly as the documentation on Parity Swap said to do it. At least how I read it. My Parity Check is scheduled for Sundays at 10pm. So I guess maybe Unraid got confused on the date? I specifically double checked before I posted here, it’s still set to Sundays at 10pm, weekly. I’ve refreshed the GUI a couple times on the machine itself (hooked up to a screen with a keyboard) and on multiple of my computers on my network. There is no Stop button that I can find. Main just shows “Reboot” / “Shutdown” at the bottom of the array list. On the Dashboard it just tells me the progress of the Parity-Check but gives me no options.
  9. Yea I was trying to simplify the explanation and maybe I overcorrected. - I swapped my 10TB Parity drive for a new 14TB Parity drive and let Unraid Rebuild Parity. That took approximately 24 hours. - I then assigned a handful of new drives to my Array. One of which was that previous 10Tb Parity drive. Unraid then went through the Clearing Process. That took about 24 hours as well. - As soon as the "Clear" Process completed, Unraid immediately started a Parity Check. That has been going for 13 hours now and has another 13 left (by Unraid's estimate). I'm confused as to why the Parity Check began when the drives were cleared. Also there doesn't seem to be any way to stop the Parity Check that is currently running. On the "Main" page I only have the option to "Reboot" or "Shutdown" nothing else. Does the system need to immediately Rebuild Parity again because I added new drives? I can kind of get that, it is just frustrating as I'm now 3 days into just trying to get some more storage in my NAS. Diagnostic ZIP added. hrh-unraid-diagnostics-20220610-1131.zip
  10. So I just made some configuration changes and I don't remember this behavior I'm currently encountering. Just checking if it is normal or if there is a way I can move forward and stop it. I added new drives to my array and Cleared them. As soon as the Clear process was complete, Unraid started an unscheduled Parity Check. Is this normal behavior? I also replaced my Parity drive with a larger one before I assigned those new drives to the array. So I'm on day 3 of Unraid just running painfully long processes and there is no end in sight. There is no button to Cancel the Parity Check that is currently happening, and I don't fully understand why it is running. I don't remember this happening last time I reconfigured my Array, but it has been a while since then.
  11. Gotcha, sorry I missed that. Attached. hrh-unraid-diagnostics-20201025-1835.zip
  12. So I've been using UNRAID for a few years and loving it. However this week a new issue has popped up. I recently replaced all of the Hardware in my UNRAID box and Reinstalled Windows 10 on my Workstation (at about the same time). Ever since, I cannot offload anything from my Workstation to my UNRAID box. Any time I try to copy a folder from my Workstation to my Unraid File System I get a "The disk is write-protected." error. If I check my folders on my Windows system they seem to say they are Read-Only (and no amount of unchecking that box does anything). However if I transfer files from one drive of my Workstation to another drive in it, it works fine. Even USB attached External drives work. It is only when I try to send files across the network to my UNRAID system that this error happens. I do see one error in the log: But I ran a SMART test on Disc 1 and it came back clean. Log file attached. I'm quickly filling up External and Internal Storage with files that should be on my UNRAID box out of the way. It seems like maybe I have a bad disc? But I cannot see any way to confirm that and I can't afford to throw hardware at a problem that may not exist. hrh-unraid-syslog-20201025-1459.zip
  13. I had to go back 3 BIOS revisions to find one that actually had the CSM menu in it. That worked. Thank you!
  14. I was worried you would say that. I cannot do that. CMS Support is listed but just says "Disabled" and gives me NO OPTION to turn it on. I'll have to try rolling back a couple BIOS versions and see if the Option was recently removed or contact Asrock.
  15. I just dug out the Linux Mint install stick I used last week on an old laptop. That worked. So it seems it is just UNRAID sticks that won't work... I'm confused and haven't found any BIOS settings to make any real change.