Connor Zook

Server was running fine, up for several weeks with no issue, then one day it just stopped working without shutting down. I reboot today and am getting this error on repeat: Monolith login: XFS (nd3) : Internal error xfs_trans_cancel at line 1041 of file fs/xfs/xfs_trans.c. Caller xfs_inactive_truncate+0x9/0xca [xifs] XFS (md3): Corruption of in-memory data detected. Shutting down filesystem XFS (md3): Please unount the filesysten and rectify the problem(s) Any recommendations on how to proceed from here? I have discovered that my insanely important backups are not on a functioning drive, as the one I was working with went down.

I have a charter spectrum router (shit, yes, but it allows me to set up port forwarding rules.) I have an unraid server with a built in 1G port (eth0). I have added to the server a 10G port,(eth1) which I then connect to my desktop to provide fast access to the internet (through my server) as well as media on the server. As things were set up, I had eth0 and eth1 bridged, which provided me with internet. Now I would like to port forward to a docker container from my router. To add a forwarding rule (on the router) I have to assign a device's mac address and IP to a specific port I'd like to forward. This would not be an issue if it were not for the bridge. When the bridge is active, my server's eth0 MAC address disappears and is replaced by the eth1 MAC address. Which means it's trying to see JUST my eth1? I'm not sure. I would like the mac address for my server, as it appears on my router, to stay constant, even when providing internet to my desktop. Every time I try to set up the bridge after setting the port forwarding rule, the mac address of my server eth0 port disappears and the eth1 takes over. I don't know how to do this. Any help would be amazingly appreciated.

Additionally, I have attached here the smart reports for both the new disk, and the disk that has been disabled but reports good on smart test. Additionally I need to get the re-enable drive procedure, as I know my original disk (disabled) to be good and working, but the wiki page for re-enabling has been wiped. https://wiki.unraid.net/index.php?title=Troubleshooting&action=edit&redlink=1 thanks tower-smart-20210413-0408 (BAD SMART NEW DISK).zip tower-smart-20210413-0413 (DRIVE WORKING UNTIL NEW DISK ADDED).zip

I have a disk with Spin_Retry_Count at 720,000, even though it has been working perfectly up until now, and has no issues accepting files currently.

What would you recommend I do from here then?

this is NOT the disk that I recently added. The newly added disk is unrelated to the one experiencing issues.

I wake up today and see that my second disk is down. I recently (<48 hrs ago) upgraded my rig with a new disk, and reconfigured my sata cabling and power cabling. I have had no issues with the disk up until now, no smart errors or warnings, and disk health is still very good (been used less than 2 years. Today it's down completely. I have the disk log as well for the disk as of the last time it was spun up. I'm not sure if it's intact from the original error state, as I did start and stop the array. Additionally, I was having some issues previously with a couple of things that I can't explain and suspect have nothing to do with this problem, but are worth mentioning anyways. 1. I was downloading a very large (1.7TB) torrent on my windows machine over the network connection to my storage server, but I was having issues with either the name of a certain file containing an illegal character for windows filesystem namespace (?) or a file name being too long for the address bar. Anyways, thanks for any help you can lend me. Diagnostics are attached. tower-diagnostics-20210413-0059.zip

I'm sorry could you explain this in simpler terms for me? I'm not sure what the differences between shares and disks are honestly.

I am using qbittorrent to download a large file (1.7TB) and my cache drive is only 256GB. How do I force the qbittorrent docker to bypass the cache drive and instead write directly to disk? Thanks.

the drive is mapped to my media share, simply a folder on my array named Media.

tower-diagnostics-20210411-0655.zip

Hello, I have my unraid box running a fileserver over a 10GbE line to the back of my desktop and have had it doing so successfully for almost 2 years. I recently added 4TB to my 16TB array as I was running out of space, only to find that my capacity upgrade has not been reflected on my windows desktop. I have tried: 1. Restarting both devices 2. Mounting and unmounting my mapped network drive, and restarting windows explorer during the interim 3. Changing the share letter from the original to an alternative one in an attempt to have windows treat it as a new device It is worth noting that even after all these troubleshooting steps have been taken, the device still shows up under the same network location name, even though it has been reset or changed to a different letter. I am thinking this failure to update storage space is reflected in windows being unable to recognize the device has changed, though I am at a loss for next steps to take. Thank you.