kobayashi

Thanks all. Got it resolved.

Oh damn lol. Can I just drop in a new drive and assign that as parity then? Edit: apologies for being flippant. If I had the system running for some unknown amount of time without parity, can I reassign 1 of my 3 (2 of my 6 TB) drives to now be parity or do I need to add a new drive now identified as the parity drive? I feel as though I remember maxing my mobo out at 4 drives though including cache...

OK. I followed this advice and determined device sdd was the parity drive as it would not mount. However when I try to assign drives appropriately, unraid os says its an 'invalid configuration'. Am I taking a wrong step somewhere?

I was using single parity. I made a mistake in my post. Where I said a drive was recognized on boot up - it was my cache, not my parity drive.

I moved recently, the server was off line for about 3 months. I had lost the usb stick with the OS so got that resolved with a new stick and got the GUID recognized. I boot up the server and it recognizes my parity drive but wants me to assign one of my other 3 drives as parity and the other 2 as storage. But I have no idea which is which. In the interface, whether I choose 1, 2 or 3 as parity and any combination of the other 2 as storage, I see the " All existing data on this device will be OVERWRITTEN when array is Started " message. Not sure what my next step is. I have attached my diagnostic log. Any advice would be much appreciated. tower-diagnostics-20180711-1734.zip

Thank you, will look into it.

About a week ago, I got an error message when trying to move a file from my Win7 unit to the Tower. The problem is with copying or writing to one of 2 discs - I can copy/write to the other disc and read from all discs, including the problematic one. None of this was a problem before. The Tower has been rebooted since and things work normally for some time but the problem has re-occurred. Below is a log where I believe the problem re-occurs. Any insight? 3222: Oct 26 08:01:14 Tower shfs/user: shfs_unlink: unlink: /mnt/disk2/Kids/Kids movies/Fantasia/extrafanart/uPfTzosj965rFg8AtEikSr2BR7b.jpg (30) Read-only file system 3221: Oct 26 08:01:03 Tower mountd[23157]: authenticated mount request from 192.168.1.107:720 for /mnt/user/Kids (/mnt/user/Kids) 3220: Oct 26 07:55:03 Tower mountd[23157]: authenticated mount request from 192.168.1.107:708 for /mnt/user/Kids (/mnt/user/Kids) 3219: Oct 26 07:51:39 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1082 1332 0x0 SD] 3218: Oct 26 07:51:39 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 460939808. Fsck? 3217: Oct 26 07:51:39 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 5989 does not match to the expected one 1 3216: Oct 26 07:51:39 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1082 1723 0x0 SD] 3215: Oct 26 07:51:39 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 460940812. Fsck? 3214: Oct 26 07:51:39 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 36974 does not match to the expected one 1 3213: Oct 26 07:51:37 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1083 1085 0x0 SD] 3212: Oct 26 07:51:37 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 460940812. Fsck? 3211: Oct 26 07:51:37 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 36974 does not match to the expected one 1 3210: Oct 26 07:51:36 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1082 1332 0x0 SD] 3209: Oct 26 07:51:36 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 460939808. Fsck? 3208: Oct 26 07:51:36 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 5989 does not match to the expected one 1 3207: Oct 26 07:51:36 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1082 1723 0x0 SD] 3206: Oct 26 07:51:36 Tower kernel: REISERFS (device md2): Remounting filesystem read-only 3205: Oct 26 07:51:36 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 460940812. Fsck? 3204: Oct 26 07:51:36 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 36974 does not match to the expected one 1 3203: Oct 26 07:50:14 Tower mountd[23157]: authenticated mount request from 192.168.1.107:708 for /mnt/user/Kids (/mnt/user/Kids)

I resolved the problem with the following command, >emhttp >nohup /usr/local/sbin/emhttp & via http://lime-technology.com/forum/index.php?topic=25720.msg224074#msg224074. Thanks scytherbladez. Still don't really understand the cause or solution.

SickBeard and SABnzbd were acting up so I rebooted. Afterwards, I cannot access UnRAID main or shares. The rest of UnMenu is fine, including the file browser. From Windows Explorer, only the flash drive is available. I have had this problem before and the solution (which I can no longer find) had something to do with deleting the plugins folder in the config directory - I believe the problem was summarized as plugins interfering with proper booting. I deleted the folder to no effect. Any suggestions?

I just had the same thing happen to me. Plugin installs were about 4 or 5 days old and were installed from the Influenced package. I've got all plugin data in a temp folder as directed. What is the best way to restore it?