philippneistat

Sorry for the double posting, I just edited this thread, I must've posted it again by accident. I deleted the other one.

Hello, here is the tower diagnostics zip attached. Just tried the corrected syntax you mentioned: xfs_repair -v /dev/sdd1 and suddenly the drive mounted again. Really weird because I ran the xfs-repair in gui multiple time to no avail. Currently everything is working, could you guys still look at the diagnostics if there is anything else weird going on with the drive? Thanks tower-diagnostics-20210830-2110.zip

Hello! Im running a Unraid server with the following specs: x570 Aorus Master Ryzen 3900x RTX 3070 4x 8TB WD Red 1x Wd-black sn750 cache Yesterday I tried starting my Unraid array, it did start but the first disk is listed as 'unmountable: not mounted'. After that I ran xfs-repair -v from the gui, which finished without problems but the disk remained unmountable. Running that same command in an command line results in this output: root@Tower:~# xfs_repair -v /dev/sdd Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ this is then running forever. Then I ran a s.m.a.r.t extended self test which completed without error despite taking the whole night. Am I out of luck? Or are there other possible solutions which I should try? Thank you for your help

Hello! Im running a Unraid server with the following specs: x570 Aorus Master Ryzen 3900x RTX 3070 4x 8TB WD Red 1x Wd-black sn750 cache Yesterday I tried starting my Unraid array, it did start but the first disk is listed as 'unmountable: not mounted'. After that I ran xfs-repair -v from the gui, which finished without problems but the disk remained unmountable. Running that same command in an command line results in this output: root@Tower:~# xfs_repair -v /dev/sdd Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ this is then running forever. Then I ran a s.m.a.r.t extended self test which completed without error despite taking the whole night. Am I out of luck? Or are there other possible solutions which I should try? Thank you for your help

Hello Guys, I have a problem with the mover. The Situation is as follows: I have a programm downloading mutlipart rar archives to a folder named *incomplete", this porgramm then unpacks the rar archives into a folder in the same directory named *extracted* and deletes the rar archives after succesful unpacking. These two Folders are Subfolders of a Folder in a Downloading Share, this Downloading Share has cache set to *yes*. So everything downloads to my cache and unpacks on it. However my problem is, that mover when running (mover is scheduled to run every 6 hours) also puts the contents of the *incomplete* Folder on to the array which makes unpackingtimes of these moved Rar archives really slow. So is there a way to tell the mover to ignore the *incomplete* Folder or any other workaround you can think of? And am i right to assume that mover doesn't touch single files being use i.e. a one file download or a multiple rar archive being unpack into a file (The file). Help would really be appreciated.

Thank you, this worked Perfectly

Hello Guys, I thought you could maybe help me with a problem i can't seem to solve myself. I have binhex-qbittorrentvpn installed with a pia vpn, that so far works flawlessly. However, i tried to map another container's network to that of the binhex-qbittorrentvpn, Jdownloader2, with --network=container:binhex-qbittorrentvpn. But with Jdownloader i can't access the web-gui and it doesnt recieve any ports or ip. If someone has a solution for this it would be much appreciated. My Settings are in the Pictures attached. Thank you for your help