Ok, I am in trouble!

 

I have a 10 disk array + parity. Parity used to be 3TB, I wanted to expand the file system. I then replaced the parity drive, had it rebuild parity, worked fine. I then replaced a random 1TB drive with the original 3TB drive. The WEBGUI noticed the disk, said "rebuild disk & expand" I clicked yes. It rand for an hour, then said there were disk errors and stopped. I thought maybe it's down to bad cabling, so I powered down the server, checked cabling, turned it back on.

Now it said parity valid (!!!!) next to the 3TB disk with a red ball. (I did not click on "start")

I then switched it back off, tried unplugged the 3TB drive and plugged back in the 1TB drive (I haven't overwritten it just in case). It came up with a blue ball saying the original drive should be the 3TB one and the new drive is too small. OK so what now?

 

EDIT: Running 5b10

Ok, my 3TB disk which replaced the original 1TB still has its red ball. Here's the thing:

If i disable it, it says that it is looking for exactly that disk. If I select that 3TB disk it stays red balled. What am I to do? It doesn't report temperature or anyhting, but if I run a SMART test it says test passed.

 

I can start the array unprotected and mount disk9 (the faulty one) and I can see all my data ist still there (I am thankful for that!) but I don't know how to get unraid to rebuild parity to the 3 TB drive. I want my array protected again!

Could it be that my 3TB drive which used to be a parity drive is "recorded" by UNRaid somewhere and thereby does not let me reuse it as a normal drive?

during the rebuild I had these errors:

/usr/bin/tail -f /var/log/syslog

Apr 11 17:56:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1

Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck?

Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD]

Apr 11 17:56:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1

Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck?

Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD]

Apr 11 17:56:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1

Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck?

Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD]

Apr 11 17:56:26 Tower emhttp: title not found

Apr 11 17:56:27 Tower emhttp: title not found

Apr 11 17:56:49 Tower shfs/user: shfs_setxattr: setxattr: user.org.netatalk.supports-eas.CESAHN /mnt/disk8/Backups (30) Read-only file system

Apr 11 17:56:49 Tower afpd[24664]: volume "Backups" does not support Extended Attributes, using ea:ad instead

http://lime-technology.com/wiki/index.php/FAQ#How_do_I_re-enable_a_failed_disk.3F

Also, Disk 8 has a corrupted Reiser file system.  See Check Disk File systems.  (This is completely unrelated to your other issues.)