CellDweller

After some more searching and trying i did give up, bit disappointing but it is what it is. Did go for ZFS in mirror with the 2 MX500 ssd's, and setup my backups better this time. Thanks @JorgeB for your answer

After some years of stable unraid usage i ran into trouble last week. Some docker containers stopped responding and were acting weird. Did check to log and saw the cache ssd was giving errors. In this configuration i had a Samsung 850 Evo as cache drive on btrfs After this i turned the server down, reconnected the sata cable and did try again. Unraid was giving no smart errors so i thought lets give it a try. I got the same errors, turned the system down, did place the sata cable in another port and turned it on with one last try. Disk was seen but could not even be mounted anymore... I went ahead and put the ssd in my computer to took a look at this with the Samsung Magician Software and Hard Disk Sentinel. Samsung Magician was saying the drive was "good", Hard Disk Sentinel however told me it was acceptable. Seeing how this drive got a 150TBW in it's official specs and had written +288TB i decided to replace the disk at once with a Crucial MX500 (and even bought 2 to place them in raid 1) I used "Macrium Reflect 8" on windows to clone the old Samsung SSD to a new Crucial, and started to work with this. This drive is also un-mountable, but i am hoping to learn something by trying to recover the data. Also some of the appdata i did not backup recently (stupid, i know), and i was wondering if i could recover this. The old SSD is not completely dead, so i have some hope. However, did some digging and trying, but i am stuck at this moment and could use some advice. I included some stuff i did try beneath. root@Tower:/dev# btrfs check --readonly --force sdf1 Opening filesystem to check... checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root ERROR: cannot open file system root@Tower:/dev# btrfs-find-root sdf1 WARNING: cannot read chunk root, continue anyway Superblock thinks the generation is 36640635 Superblock thinks the level is 1 root@Tower:/dev# btrfs rescue super-recover -v sdf1 All Devices: Device: id = 1, name = sdf1 Before Recovering: [All good supers]: device name = sdf1 superblock bytenr = 65536 device name = sdf1 superblock bytenr = 67108864 device name = sdf1 superblock bytenr = 274877906944 [All bad supers]: All supers are valid, no need to recover root@Tower:/dev# btrfs rescue chunk-recover sdf1 Scanning: DONE in dev0 corrupt node: root=1 block=1128005632 slot=0, corrupt node: root=1 block=1128005632, nritems too large, have 12 expect range [1,0] Couldn't read tree root open with broken chunk error root@Tower:/# btrfs restore --dry-run -d /dev/sdf1 /home checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root Could not open root, trying backup super checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root Could not open root, trying backup super checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root Could not open root, trying backup super Is this a totally lost cause, or is there some hope here? Many thanks in advance! tower-diagnostics-20230713-2006.zip

Already know Mopidy, trying to setup this container, and it is a little bit harder than normally. But i saw this commend, en saw i had the same "aadbbd6bbef9" in de config. This originates from github is you copy the mopidy.conf. Easly to be looked over. Can this be fixed for other users? https://github.com/maschhoff/docker/blob/master/mopidy/mopidy.conf

Fixed the problem. It appears rtorrent has a problem with adding labels through the api. It errors on special characters and spaces... So "nametracker - movies" gives these weird problems, "nametracker-movies" works fine. Little weird but ok, it's all working fine now. Very happy with all this! Last thing for me personally is to look into queuing torrents when multiple get added at the same time. Found out about pyrotorque, and pyrocore already to be in this docker. Will have to take a look into all this, but this whole docker package is awesome! Thanks for all the hard work Binhex! I will donate something, i think your packages are very nice, keep the good work up!

I did not bother making a other account for this, still using the default admin account. Although it is a good idea to change user i think. But being not really a "linux guy" i did not think about this yet. But using the default account, should i be affected by this, i think not? (Again, i am NOT a experienced Linux user)

I don't think so. I spend a couple of hours on this. Trying different settings and versions. I was trying to download something, let autotools do it's thing, try a reboot. I saw it failing, and did try again, and again, and again.... This changed last week when i downloaded something, but my girlfriend told me to come eat something. In early'er attempts there would not be more than ten or twenty minutes between the download and reboot. But i was away for a hour or so, did a reboot, and it worked like i should. For some reason i takes ages for rtorrent to update the session file. I did try the "rutorrent" container, that one looked like t was behaving better with this, although i did try that one for like 1 or 2 downloads. So not quite sure... Decided to just go with it, because it should only reboot on a update, so not as often, most torrents would be for hours of days in rtorrent before an update. I thrown all my torrents (650 torrents, just shy of 12TB) into rtorrent, did a recheck, en hoped to roll with it. For the most part it works awesome. System load is minimal, and uploading goes great. Upload averages on 31TB each day, very nice. However, i'm having troubles at this moment with sonarr/radarr. It can add torrents, but they "start" with error, without the configured "label", and no "added date". And when downloaded, sometimes they stop, and i cannot get them to start again... So i still have to check this manually en start the downloads them self... Going to investigate in the next couple of days, but i someone has some tips where to start looking, that would be great!

Ok, so i did give it some more try's today, but failed just the same. I really don't know where i'm going wrong here. I am pretty new with unraid and containers. Today i read this topic from page 40 to 72 in hope to get some more information, and i did the following after multiple tries. - Deleted the container, image and the whole binhex-rtorrentvpn folder inside of appdata. - Shutdown Docker in Unraid Settings, and started it all again after a minute or so. Just to be sure - Did not start any other container while doing all of this - Installed binhex-rtorrentvpn - Started the container, open settings, only to change autotools. I did not do anything else! - Downloaded a torrent, first it gets in incomplete, moves to completed once done, great - Restarted the container trough Unraid Webgui - And rtorrent again expects the file to be in incomplete, its not there, shows 0,0% and in paused state Only setting i changed is the network type i guess in container settings. I have a Mullvad vpn setup on my pfSense, which filters some ip's and put them on vpn. But i did also try this whole process described above, and use the normal bridge mode. Also with the same result... Still having the same problem... I added the log, settings, screenshot of rutorrent after the restart. Anyone who has a idea how to solve this? Almost forgot, as frustrating as this has been for the last 3-4 hours. A friend who also has a unraid server @ home with rtorrentvpn looked at my config. We were not able to compare the settings exactly this after noon, but he also did not see anything weird, while he is supposed to have the same settings. But again, even "out of the box" i have this problem. The other "rutorrent" plugin is working, but i rather use this one... supervisord.log rtorrent.rc

Can someone give me some advice about how to handle rtorrent with use of the autotools move option? I changed rtorrent.rc with a folder to put new downloads in, and configured autotools to move torrents after they are completed. With the options "add torrent's label in path" and "add torrent's name to path" enabled. This is working fine, torrents are downloaded to /data/torrents/incoming. And after there are done they get moved to /data/torrents/completed/{label name}/{torrent name}. Just the way i want it to, nice! However, when i restart the rtorrentvpn docker, it "resets" all the save path's of all the torrents already done. While the data is still in the "completed" folder, rtorrent is looking in the "incomplete" folder and cannot find the data. This causes rtorrent to stop seeding which i do not want. I already did some search on google and here on the forums, but i'm not yet on the right path to fix this problem. Anyone?

Cool, than i will buy a LSI 8 port and start with the LSI and onboard controller, Thanks!

Hello People, New to Unraid and looking at it to replace my Proxmox installation, but I came up with some questions on which I cannot directly find an good answer. Currently I am running with the following hardware: Intel G4560 16GB ECC Memory Fujitsu D3417-B2 Intel P600 265GB SSD M2 NVME for Proxmox and VM's 2X HGST 8TB NAS 1x Toshiba 6TB X300 1x WD Red 6TB 1x Hitachi 2TB Areca 1280ML - 2x 8TB RAID1 on the Areca for data - 2TB Drive for Music library - 2X 6TB are also in RAID 1. 50% for my Nextcloud data, the other 50% for backups of my roommate. Running raid is forcing me to have them all spinning most of the day, which uses more power then I like to use. Same goes for ZFS, which also I not easy to expand as far as I know of? I want to switch to unraid because of this reason while I’m getting five new 8TB drives this week, also a 1TB SSD drive which I can use as cache. As awesome as this is. Already did read that an Areca card is probably not the most decent thing for unraid, it’s pretty overkill, and could make things more difficult. Now I am looking at buying a used LSI card, but am struggling to decide which one to buy. Most offers are 8 port versions, some support trim, some don’t. That forces me to buy or two LSI cards, of combine my onboard (Intel C236) and a LSI 9211-8I for example. This is where my main thoughts are now. How decent of a solution is this? Would you guys recommend this, or is it better to look for a 16 port version, or 2 8ports and skip the onboard controller completly? I would have seven 8TB drives, but next month I maybe getting 2 more, so that would be more than 8 for one controller, and I don’t know how unraid handles this performance wise. And how would unraid handle this if I would to switch to another motherboard? Also playing with the idea to put the ssd onboard for trim support. Can someone please give me some advice on this? Many thanks in advance!