denizen

Just wondering if you had ever got around to testing this. Thanks in advance!

Resolved - Rebooted system and user shares reappeared. Noted that my cache drive was full. Hopefully that was the issue.

Not exactly sure what happened. Was trying to troubleshoot a mcmyadmin2 docker container when I noticed. Was also getting docker disk image becoming full errors. Attached is my diagnostics file. Stopped and restarted the array and now docker failed to start with it. Thanks in advance.

Have yet another 'call traces' error for someone to help me out with. Server seems to be working fine. Thanks in advance! tower-diagnostics-20180418-0946.zip

Yes. After doing the new config you are brought to the main page and all drives are unassigned - as if you were booting the server for the first time. You pick Disk 1 and then assign a drive by serial number, etc. When you get to Disk 4 you'll just pick a drive that remains in your system. Note that you need to refer to your drives by serial number, not sda/sdb, etc. The sda/sdb device names will change when you disconnect some of your disks, so you need to know the serial number of the parity drive in order to reassign it correctly under the new config. The other drive slots don't really matter, but it's critical to reassign parity correctly. Then my proposed steps would be: 1 - Take screenshot of current drive setup 2 - Take the array offline 3 - Unassign Disk4 and Disk5 4 - Shut down the server 5 - Remove Disk4 and Disk5 from the server and swap Disk11 and Disk12 into these positions 6 - Start up the server 7 - Click the "New Config" link 8 - Re-assign all previous drives to their previous positions (including parity and cache) except for the drives which had been Disk11 and Disk12 which will now be assigned to Disk4 and Disk5 9 - Take the array online 10 - Watch parity rebuild Does that sound reasonable? Do I need to do step 3 or just shut down the server and rearrange the drives? Also, I am assuming that invoking New Config will reset my previous share settings. Or am I incorrect in thinking this? Thanks in advance!

I am now in the process of removing some old 1.5 TB drives which are disks 4 and 5 in my array and am planning to use the New Config option for the first time. I am planning to use the method as referenced above, but then I imagine in my case disk4 and disk5 would be missing in the new array ie disk1, disk2, disk3, disk6, disk7, etc. So here is my follow up question: Once I activate the New Config option is it also possible to switch other data drives into the previously removed disk positions and keep the disk numbering contiguous? In other words, as long as I assign the correct drives for parity and cache, can I then rearrange any of the other data drives in any position I want since it is a "new config"?

It just so happens that I have not upgraded to 6.1 yet. Would you see any downsides to trying this out? or (another way to put it) IF Unassigned Devices plugin were verified for 6.1, would this be a way to use the plugin?

Thanks for the quick reply. Makes perfect sense. I would ultimately have to rebuild parity in the above scenario (no time saved ). I guess I have another question then. Would it be possible to use the Unassigned Devices Plugin for this purpose? I have never used this plugin before. Thanks again!

I apologize in advance if this has been covered, but I have not found an answer to a question I have in my brief search. Hopefully it will be an easy question to answer. I am currently preparing for the process of changing my cache drive format from reiserfs to btrfs. I currently have a reiserfs formatted cache drive with my app data and docker image on it and would like to migrate the data to a new btrfs formatted ssd cache drive. In my search of the forums it appears that the most common sense method of doing this would be to copy my cache drive data to the array and then reassign the ssd as the new cache drive and then copy the cache drive data back to the new cache drive. My question is whether I can save a copy step by simply reassigning my old cache drive as a new disk in the array and retain the data on it. Then I would be able to add the new ssd as a cache drive and copy the the data directly to it. Hope this makes sense. Thanks in advance.

It's in the Advanced View -> Environment Variables. Let me know if you get it working. Funny, I just updated to the latest version and I don't seem to have that option under my Environment Variables. I suppose I could just add it. Were there any examples listed under Variable Values?

kurterik, I have been attempting to do the same thing. Where did you see the LAN_RANGE option?

Has anyone set up a Pocketmine container for unRAID? or would be willing to help me set one up? There are already multiple Pocketmine containers on the official Docker site. I know nothing about making a container for unRAID but would be willing to learn. Thanks!

What happens when you open the docker page in unRAID, left click the container icon, and select WebGUI?

Jim and I worked on this quite a bit and could not resolve the CP communications with Deluge. He resorted to using the blackhole method and setting Deluge to a watch directory. While not as elegant of a solution (i.e. wont handle failed downloads, etc.) it does work. Not sure if you guys got this working or not, but here is what I did to get them talking to one another: 1. Open the 'auth' file in your deluge config folder to see what the deluge daemon username and password is. The format is <username>:<password>:10 where 10 represents the user level. Alternatively, you can edit this file to replace or add a <username>:<password>:<userlevel> as you see fit. You may need to restart the deluge container after your edits. 2. Open the couchpotato settings and enter the username and password from the auth file above. Change the Host section to the ip of your unRAID server. The port should already be defaulted to the deluge daemon port which is 58846. Set a label for deluge. 3. Press the Test button and hopefully it will give you 'Connection Successful' If I can remember correctly, that's all it took for me. Hope this helps. Binhex, wondering if you ever got around to allowing local domains ie 172.16.x.x through delugevpn? Still trying to find a good solution for RSS feeds.

the originial issue was to do with allowing the deluge daemon to talk to other dockers which is now resolved, i am using iptables to prevent ip leakage so i had to be very careful as to what to allow. currently i am only allowing docker to docker conversion to the deluge daemon and thus your having the issue when trying to use another host. i could revisit this and relax the restriction a little bit more to allow known private lan ranges, e.g. 192.168.*.* and 10.0.*.* so that you could also connect to the daemon from another host on your LAN, leave it with me. Binhex, that would be great! Thanks for the quick reply. If you are able to do this, could you add 172.16.*.* into the mix? Or...not sure if this would be able to be a user configurable option? Thanks again!

I have recently moved over to unRAID V6 from V5 and am amazed with the new Docker system. Binhex, thanks for providing (and supporting) these awesome containers. I have gotten delugevpn up and running without too much of a hitch, but am interested in adding RSS functionality into it via deluge's plugin system. I have been trying to use the YaRSS2 plugin, however it requires a GTK UI setup for configuration. The deluge user guide to set this up seems pretty straight forward, but I am having trouble connecting to the delugevpn daemon via a thin client (tried from both mac and windows machine). I have tried adding a <user>:<password>:<access level> to the delugevpn auth file and am trying to connect via the daemon port 58846. I saw that you were trying to resolve this multiple pages back and was just wondering if I missed a resolution to this. Or is this still a work in progress? BTW, accessing the delugevpn daemon via the couchpotato container seems to be working fine. Thanks, -denizen

Here they are. smart_sdi_12.19.14.txt

Was having trouble accessing my iPhotos library on the Unraid server yesterday and decided to run a parity check. When I checked on the status this morning, Drive 8 was taken out of service (redballed) with all the other drives ok. The iPhoto library was on Drive 2. Just wanted to make sure that this is probably a drive failure before proceeding along those lines. Attached is a syslog. Thanks. syslog.txt

I am having the same issues. I see its many months since your post. Any solution to your issue?

Thanks for putting together this excellent guide. I have a question about section 8.2. :Migrate to cache only share model. In this section you suggest setting Included disk(s) to cache. On my system, even though I have a cache disk, I am not given the cache disk as an option to include. It only allows me to include my "disks". I am trying to troubleshoot some other issues and am wondering if my server is somehow set up wrong such that I am not able include the cache disk. Attached is a screenshot. Thanks

Looks like I am having a similar type of issue, also while preclearing a drive with AOC-MV8-SASLP. I am running unRAID 4.7. Was not aware of the issue at the time and preclearing the disk nearly finished with this output: ================================================================== 1.3 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Step 10 of 10 - Verifying the clear has been successful. = Elapsed Time: 5:09:03 ========================================================================1.3 == == SORRY: Disk /dev/sdb MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ dd: reading `/dev/sdb': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00160582 s, 0.0 kB/s 0000000 My syslog grew to 2 gigs. Looks like I got a similar message as betaman just after starting the preclear. Feb 2 04:46:24 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() Feb 2 04:46:24 Tower kernel: Hardware name: A760G M2+ Feb 2 04:46:24 Tower kernel: Modules linked in: md_mod xor atiixp ahci r8169 mvsas libsas scst scsi_transport_sas Feb 2 04:46:24 Tower kernel: Pid: 2047, comm: smartctl Not tainted 2.6.32.9-unRAID #8 Feb 2 04:46:24 Tower kernel: Call Trace: Feb 2 04:46:24 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Feb 2 04:46:24 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 Feb 2 04:46:24 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 Feb 2 04:46:24 Tower kernel: [<c11ac0ba>] ? scsi_init_sgtable+0x5b/0x76 Feb 2 04:46:24 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff Feb 2 04:46:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd Feb 2 04:46:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd Feb 2 04:46:24 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 Feb 2 04:46:24 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d Feb 2 04:46:24 Tower kernel: [<f843769a>] sas_queuecommand+0x65/0x20d [libsas] Feb 2 04:46:24 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd Feb 2 04:46:24 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 Feb 2 04:46:24 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 Feb 2 04:46:24 Tower kernel: [<c1126798>] __blk_run_queue+0x78/0x10c Feb 2 04:46:24 Tower kernel: [<c1124446>] elv_insert+0x67/0x153 Feb 2 04:46:24 Tower kernel: [<c11245b8>] __elv_add_request+0x86/0x8b Feb 2 04:46:24 Tower kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 Feb 2 04:46:24 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 Feb 2 04:46:24 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 Feb 2 04:46:24 Tower kernel: [<c11295fa>] ? blk_recount_segments+0x16/0x24 Feb 2 04:46:24 Tower kernel: [<c11250c6>] ? blk_rq_bio_prep+0x47/0x78 Feb 2 04:46:24 Tower kernel: [<c1128edb>] ? blk_rq_append_bio+0x14/0x3b Feb 2 04:46:24 Tower kernel: [<c1129121>] ? blk_rq_map_user+0x12c/0x1be Feb 2 04:46:24 Tower kernel: [<c112c2bf>] sg_io+0x22d/0x30a Feb 2 04:46:24 Tower kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc Feb 2 04:46:24 Tower kernel: [<c104cbfe>] ? get_page_from_freelist+0x2e4/0x344 Feb 2 04:46:24 Tower kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c Feb 2 04:46:24 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 Feb 2 04:46:24 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc Feb 2 04:46:24 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 Feb 2 04:46:24 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 Feb 2 04:46:24 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 Feb 2 04:46:24 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf Feb 2 04:46:24 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 Feb 2 04:46:24 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b Feb 2 04:46:24 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da Feb 2 04:46:24 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 Feb 2 04:46:24 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 Feb 2 04:46:24 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 Feb 2 04:46:24 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 Feb 2 04:46:24 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac Feb 2 04:46:24 Tower kernel: [<c105c983>] ? expand_downwards+0x109/0x136 Feb 2 04:46:24 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 Feb 2 04:46:24 Tower kernel: [<c1002935>] syscall_call+0x7/0xb Feb 2 04:46:24 Tower kernel: ---[ end trace cb967b7456a0ba22 ]--- Any help would be appreciated. Thanks