01111000

Would I be able to use a cloudflare tunnel or do I need to utilize a reverse proxy setup to access? Thanks in advance

My current server turned 9 years old last week (lol) and I decided to upgrade it to 10gbe. I bought a 2.5gbe switch with 2x 10gbe ports and purchased two intel based 10gbe cards (x540 x2, one for Desktop, the other for the server). It’s all installed, and I can see all interfaces in Settings > Network however they are offline. This build does have IPMI. How would you go about setting up the 10gbe network now? If I just run one Ethernet cable to the 10gb card, I lose IPMI, correct?. If I run two cables, how should I handle that from a DHCP perspective and what are the cons?

Any special concerns going from 6.9.2 to this release? I know, I’m very behind…

LAN IP

I must be overlooking something simple but I’d like to access my server while on the go via IP Address when I’m using the VPN. While Tailscale does connect, I cannot access any of the local services running on my server via IP. Where do I configure local access?

Great, thanks again. The cables are very old at this point so hopefully it works either way.

Gotcha. Time to buy new cables for that backplane.

Parity, SDZ and SDY are the problem disks right now. There are no smart warnings that I can see, only indication of something being wrong is the parity disk being disabled. Scrutiny doesn’t indicate anything either but I don’t know how it polls its data. This is a server running at my parents house, I no longer live with them and am usually not around due to my job. That’s also why it hasn’t been updated, I haven’t been around and have not had time to really sit down and work through any potential issues after the upgrade. This build has been particularly bulletproof throughout the years. Here’s the weird part of this, maybe related? The server is physically located on top of a cabinet, 6 feet or so above the ground. On the same day of this issue, the basement bathroom flooded this area. I’m thinking it’s possible that they bumped that cabinet a few times while dealing with this aftermath. I can’t tell for sure though. That’s why I’m asking for help, I was thinking about trying to reseat the cables but what would be the best way to determine this potentially fixed an issue? Or am I crazy for thinking this could be a cause? Thanks again for your help

Well, duh. Sorry about that server-diagnostics-20240127-1604.zip

Hey, it's been some time. Recently, I have a 3 drives, including a parity drive, report errors. How should I proceed at this point?

AKR- with the new 6.4 release, Unraid’s GUI is utilizing 443. You will need to change that to 442 or something similar and forward the ports as needed.

I had the same issue. I tried rebooting but it did not work, so I ended up rebooting via IPMI. The next restart it was stuck on Mounting Drives. Still stuck trying to shut down.

I believe that a few plugins auto installed these packages. I'm using peter sm's OpenVPN plugin, for example. Ive fixed the deluge error as well. I'll give it a try and report back. edit- nope. Same issue. Unmounted unassigned drives, stopped OpenVPN, stopped all dockers and VMs and use Open Files plugin to kill any remaining processes.

server-diagnostics-20171009-2011.zip See attached. Thanks

I've had this issue as long as I remember, literally years. I'm on 6.3.5 I am trying to either Stop my array or reboot/shut down. It ALWAYS gets stuck with "Unmounting disks...Retry unmounting disk share(s)..." and I am forced to use IPMI to force a reboot. I want to fix this once and for all. I'm trying to add a new disk but cannot because of this. I stop ALL of my dockers and VMs before hitting stop in the webui. How can I troubleshoot this and resolve it? I'm so sick and tired of this issue rearing its head every few years. I really appreciate any help with this; I'll provide whatever is needed- I'm extremely frustrated right now.

Is there at least a slightly more detailed guide on migrating from the LT plex docker to the LS Unraid docker? Thanks for the dockers guys, appreciate all that your team does for the community.

I think it needs a new package that isn’t in 6.1 Peter, how can I ensure that the plugin doesn’t auto update and kill itself? Thanks

Version 6.1 should be fine for latest plugin Do we need to rebuild anything? I have the same issue even with the latest update. Rolling back to the version that was linked two pages or do ago allows me to connect right away. I appreciate the help

Has this been fixed or do I need to use the old plugin on 6.1? How can I disable the auto updates that break it? Thanks

Just wanted to say thanks. Was able to use this plugin to easily mount drives from my old unraid server to transfer the data to the new server. Will also put it to use for a deluge docker as my ssd is relatively small compared to my old, now unused, cache drive.

My Cache Drive failed last week after a good 7 years or so of use. I bought a new WD Blue 1TB drive, and started the preclear process... Except that, it doesn't seem to be moving. The first preclear I attempted started fine. The pre read was going around 150 megabytes before I left for work. When I came back, it dropped to less than 3 megabytes. I stopped the preclear and changed the drive's location within the server and attempted another preclear. Same issue. Here is what I see on the 3rd attempt after moving the drive again: Here's a Smart test smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Blue (SATA 6Gb/s) Device Model: WDC WD10EZEX-00BN5A0 Serial Number: WD-WCC3F4XHKHY7 LU WWN Device Id: 5 0014ee 2b5e1c237 Firmware Version: 01.01A01 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Feb 22 14:19:25 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 241) Self-test routine in progress... 10% of test remaining. Total time to complete Offline data collection: (12360) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 128) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 20 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 23 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 5 194 Temperature_Celsius 0x0022 108 108 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 172 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Bad drive, I'm guessing?

+1 +1

Care to do a quick write up? I'd like to do something similar.