dgaschk

A red ball will not go away unless the disk is rebuilt or New Configuration is selected.

It does. Unformatted is not the current issue. The array first needs to have all good/green disks. Then the lack of formatting can be addressed. The color indicating that data is on the cache drive only makes sense in the context of the shares page and we agree that an orange/yellow indicator on the shares page means that data is on the cache drive. On unRAID main the wiki is correct in that the color on unRAID main indicates a partially rebuilt disk. A disk share cannot use the cache drive. Since disk 5 went red during the rebuild of disk2 we now have 2 disks that are not green. Do you have the original disk2? Is the disk OK? Otherwise, follow the instructions in Reply 22.

This is incorrect. See here: http://lime-technology.com/wiki/index.php/Un-Official_UnRAID_Manual#Colored_status_indicator No. What I posted is correct. That wiki page is not correct. Let me dig up the exact quote from Limetech. Orange on the shares page is what you say. On unRAID main it is a partially rebuilt disk.

Disk 5 appears to be responding correctly. You'll need to set a new config and then rebuild disk2. See here: http://lime-technology.com/forum/index.php?topic=32491.msg298738#msg298738

What does unRAID main show?

This is incorrect. See here: http://lime-technology.com/wiki/index.php/Un-Official_UnRAID_Manual#Colored_status_indicator

Okay great! I hate to be a pain, but I just want to make sure that i'm doing everything okay. So right now I have the 3TB drive with the backup image hooked up to my computer, which is currently booted up with SystemRescueCd. The image I made onto the 3TB drive is on the partition "/dev/sdb1". Should I run "reiserfsck --rebuild-tree --scan-whole-partition against this partition to perform recovery? Absolutely not. reiserfsck --rebuild-tree --scan-whole-partition image.file. See here: http://www.cgsecurity.org/wiki/ReiserFS_File_Undelete_HOWTO Parity was trashed at this point. Parity is still trashed. You can pretend that the parity is is not present for the rest of this discussion.

See SYSTEM LOG in my sig.

Looks like /usr/local/emhttp/mnt is a link to /mnt. Are you trying to access the files through the web interface maybe? This is correct. I missed it.

Disk 5 has a bad or loose SATA cable. Replace the disk5 SATA cable and reboot. Wait 20 minutes then copy and attach a new syslog.

The path is wrong. /usr/local/emhttp/mnt... does not exist. It should be /mnt/user...

Run Memtest overnight. Any add-ons? Prepare the free version on a new Flash drive and try to boot.

See SYSTEM LOG in my sig.

Paste a SMART report for the new drive.

Attach the drives to different SATA ports.

Thanks for the response!!! So you are suggesting using reiserfsck or something equivalent on /dev/md4 (virtual device in UnRAID) as opposed to /dev/sdb1 (The partition on the new 3TB backup drive where the block level copy of my troubled 2TB drive is)? The only reason I ask is I wasn't sure if the backup partition I made of the troubled disk on the new 3TB would be known as /dev/md4 as It only shows as /dev/sdb1 in Partimage. On the server use /dev/md4 whenever possible. Reading from /dev/sdb1 is also ok but make writes to /dev/md4 if possible. The image can be worked on in unRAID but using a Windows or Linux system will be easier and allow more options. This is an image. NP.

Leave it blank.

Check for BIOS and firmware updates.

I do not understand the problem. Paste a terminal session that shows the issue.

See here: http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F Aslo see the link I provided earlier.

Ask in the VM forum.

Use /dev/md4 to keep parity in sync. You can run reiserfsck or an equivalent recovery utility on the image file. rieserfsck requires the image be mounted first.

See Check Disk Filesystems in my sig.

The procedure in the link is much safer. If all disks save one, e.g., disk3, are working then the procedure will safely rebuild disk 3 when the array is started.

All drives save the new one must be green.