April 9, 20233 yr UnRAID Version: 6.11.2 Plugins: Unassigned Devices, CA Auto Update Applications, CA Backup/Restore Appdata, CA Cleanup Appdata, Community Applications, Dynamix S3 Sleep, Dynamix System Information, Fix Common Problems, Nerd Tools, Open Files, User Scripts Dockers: binhex-Radarr, binhex-sabnzbd, mylar3, radarr, binhex-sonarr, EmbyServer Hardware: Case: Lian-Li PC-A77F Motherboard: SuperMicro X9SCM-F Processor: Intel Core i3-2120 Sandy Bridge Dual-Core 3.3 GHz LGA 1155 RAM: Kingston 8GB SATA Extender: Supermicro AOC-SASLP-MV8 SATA Extender Hot-swap Bays: SuperMicro CSE-M35T-1B (x 2) Power Supply: CORSAIR Enthusiast Series TX750M USB (unRAID): Lexar JD Firefly 8GB Hard Drives: Parity WDC_WD80EFAX-68KNBN0_VDHBX7VD - 8 TB (sdb) Disk 1 WDC_WD20EADS-00R6B0_WD-WCAVY5374796 - 2 TB (sdf) Disk 2 WDC_WD30EZRX-19D8PB0_WD-WMC4N0J7D8TT - 3 TB (sdd) Disk 3 WDC_WD20EARS-00MVWB0_WD-WCAZA9034298 - 2 TB (sde) Disk 4 WDC_WD80EFAX-68KNBN0_VDH2MGVD - 8 TB (sdh) Disk 5 ST4000DM005-2DP166_WGY0E53A - 4 TB (sdj) Disk 6 ST3000DM001-1CH166_W1F23145 - 3 TB (sdm) Disk 7 WDC_WD30EZRX-00SPEB0_WD-WCC4E0NP7NLR - 3 TB (sdl) Disk 8 ST8000DM004-2CX188_ZR128XVM - 8 TB (sdk) Disk 9 ST4000DM005-2DP166_WDH2S61F - 4 TB (sdg) Disk 10 ST4000DM004-2CV104_ZFN0BNMN - 4 TB (sdi) Disk 11 ST8000DM004-2CX188_ZCT3VH40 - 8 TB (sdc) Cache INTEL_SSDPEKNW512G8_PHNH929303YD512A - 512 GB (nvme0n1) Flash JD_FireFly - 8 GB (sda) Issue: Last night, my internet became very flaky; dropping out every 5 minutes or so. So for the evening, I unplugged my router and just worked off of my cellular hotspot (just Netflix, not unRAID). Before I went to bed, I plugged the router back in. Overnight, the issue with the internet connection was resolved, however, when I tried to access unRAID through the GUI, I was getting "This site can't be reached". I would leave it for a few minutes, and unRAID would then load properly, then it would lock up again with "This site can't be reached". This is also happening with all dockers and when I try to SSH into the server; intermittent responses. So I set the system up to ping the server for a few minutes. There was only one packet lost in that time, however, during that time, I was continuing to experience the intermittent error of being unable to reach it. I did a clean shutdown and restart from the tower itself (shutdown -r now). It boots properly, but the problem persists. What is the next thing I can look at to try to figure out what is going on? Thanks. tower-syslog-20230409-1359.zip tower-diagnostics-20230409-1332.zip Edited April 9, 20233 yr by Netbug typo
April 9, 20233 yr 3 hours ago, Netbug said: What is the next thing I can look at to try to figure out what is going on? Perhaps post diagnostics so someone can look into details
April 9, 20233 yr Author 3 minutes ago, apandey said: Perhaps post diagnostics so someone can look into details Sorry. I didn't realize that was separate from the system log. Attached. tower-diagnostics-20230409-1332.zip
April 9, 20233 yr Community Expert Try booting in safe mode, if that doesn't help create a new Unraid stock flash drive, no key needed, and see if you can access the GUI booting that.
April 9, 20233 yr Community Expert Also make sure you update, that release has a major bug formatting new disks.
April 10, 20233 yr Author 3 hours ago, JorgeB said: Try booting in safe mode, if that doesn't help create a new Unraid stock flash drive, no key needed, and see if you can access the GUI booting that. I've successfully updated to 6.11.5. If booting into safe mode works, what would be the next step? Also, do you have a link to instructions on how to create an unRAID stock flash drive? Thanks.
April 10, 20233 yr Author Safe mode did not help. Issue persists. How does one create an unRAID stock flash drive?
April 10, 20233 yr Author Ordered a new USB drive. Hopefully arriving today. Will update once transferred.
April 10, 20233 yr Author Solution Oh FFS. I figured it out. I set up a constant ping to the unraid system and had it running in a window. Then when I went to mess around with the cables, I happened to glance up and see that I was still getting no packet loss. Long story short, somehow the DHCP reserved range on my router was wiped so two devices (unraid and a chromecast) had the same IP address. Fixed the reserved range and it seems to be working (fingers crossed).
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.