I just finished pre-clearing a new Seagate 1TB drive, added it to my array, restarted & everything looked fine. While I'm fighting issues with preclearing a 3TB drive (intended to be the new parity disk), I figured I'd start moving a few items back to the server (since my first 7 drives have between 11 & 15GB free, each, I'd moved a few files off to free up some room).  Using Windows, I copied a few movies to my 'Movies' share, and got an error indicating that I needed permission to continue.  Assuming that unRAID was going to put the data on the new drive, since I use high-water allocation, I clicked the disk ID in Main and double checked that SMB was set to export & security set to public for the drive. When I clicked Apply, then Done, Main was showing the new disk with a red ball. In the drop-down for disk 8, it showed my 'extra' disk that I mount with SNAP, and it showed the 3TB drive that is being pre-cleared, but it didn't show the 1TB that was part of the array. At this point, I shut down the array and rebooted the server, in the hopes that it would come back up OK. It didn't.

 

Knowing that there's nothing on this drive, I'm not worried about losing data, so I brought the array down, marked disk 8 as unassigned, and brought it back up. It's now showing disk 8 as not installed with a dark red ball (instead of the bright red it was before) and the array as started, but it has a yellow ball.

 

Since I'm not worried about losing any data on this disk - it's brand new and hasn't had anything written to it yet - what are my next steps to get the array status back to green, then to trouble shoot why the disk went red? At this point, since there is so little space left on my array, I'm not writing anything to it, either, just reading from it.

 

Here's a sys log from the reboot, what else would be of value to identify what's gone wrong? Too big to put it inline, I'll attach it. Crud, just over the limit to attach it... Here's a link to pastebin: http://pastebin.com/rx1Chf7t

 

The drive itself is recognized by unRAID, I've attached a screen shot with it highlighted for disk 8, it just won't come up at this point.

 

TIA!

FreeMan

What model PSU?

It's a Corsair 400W. I can't find a precise model number w/o removing the PSU from the machine. I can see 4 of the 6 sides, and there's no model # label visible.

 

I was wondering if I'd hit capacity of the PSU. I've got a 3TB drive that I just can't get to pre-clear, either - it keeps freezing. Info on that is in this post: http://lime-technology.com/forum/index.php?topic=4068.msg279521#msg279521, and a couple of posts up from there. I reseated the SATA cables, but that doesn't seem to have helped the preclear or the red ball.

 

If I unplug the red ball from the system, what impact will that have on the array? Will I be able to get it to forget that drive was there and give me a green "OK"?

I'm also getting out of space errors, which I've never had before.

 

As an example, here's the output from snap.sh -listDevInfo

unRAID=No  SNAP=No  3516  /dev/sdb  scsi-SATA_WDC_WD30EZRX-00_WD-WMC4N0533589
/boot/config/plugins/snap/snap.sh: line 233: echo: write error: No space left on device
/boot/config/plugins/snap/snap.sh: line 233: echo: write error: No space left on device
/boot/config/plugins/snap/snap.sh: line 233: echo: write error: No space left on device
/boot/config/plugins/snap/snap.sh: line 233: echo: write error: No space left on device
/boot/config/plugins/snap/snap.sh: line 233: echo: write error: No space left on device
unRAID=Yes SNAP=No  3571  /dev/sdd  usb-Sony_Storage_Media_9B2001206270002610-0:0

 

Main is showing that there's plenty of space on all devices for a few lines of text in a log file.

Use Utils->New Config and assign the drives as desired. Refer to the screen shot to identify the parity drive. The data drives can be assigned in any order.

 

The message appears to be referring to /dev/sdb  scsi-SATA_WDC_WD30EZRX-00_WD-WMC4N0533589, a device outside of the array.

Couple of points:

 

1) The disk full errors I listed were given for every drive in the box (including the empty cache drive and the nearly empty flash drive), I just happened to show a sample from the new 3TB that I'm trying to get pre-cleared (thus, outside the array).

 

2)  Reading the description in Utils -> New Config, I'm not sure that's what I want. Either that or I don't understand it properly. Since you're telling me to use it, this is what I think it must mean: Tell unRAID to ignore parity, assign all the drives as newly specified, then rebuild parity.  This is what I can use to remove disk 8 from the array. Is that the correct interpretation?

 

Thanks for your guidance!

Couple of points:

 

1) The disk full errors I listed were given for every drive in the box (including the empty cache drive and the nearly empty flash drive), I just happened to show a sample from the new 3TB that I'm trying to get pre-cleared (thus, outside the array).

This is a SNAP issue. Ask for guidance in the User Customizations forum.

2)  Reading the description in Utils -> New Config, I'm not sure that's what I want. Either that or I don't understand it properly. Since you're telling me to use it, this is what I think it must mean: Tell unRAID to ignore parity, assign all the drives as newly specified, then rebuild parity.  This is what I can use to remove disk 8 from the array. Is that the correct interpretation?

 

You can assign any number of drives after selecting New Config. Parity will rebuild using the selected set of drives.

Not really sure why this got moved here - it wasn't an issue with SNAP. I saw the errors in the syslog and on the console for all drives, too. SNAP was the easiest way to get a quick screen grab of the error message. Anyway...

 

It seems that a new power supply did solve the red ball issue.

 

9 green drives = 18 A

2 7200  drives =  6 A (or is it 4?)

1 PATA  drive  =  4 A (my estimate for an older drive)

1 Mobo, etc    =  5 A

 

33 Amps from a 30A power supply doesn't work well.  Just picked up a nice new Corsair TX650 with 54 A, so that should give me some growing room.

 

I'll continue to pursue the preclear issue I'm still having in the other thread I started, and I'll move on.  Thanks, dgaschk for your help!

OK, this didn't really seem to have solved the issue. Disk 8, my new 1TB drive keeps getting a red ball. 

 

I've done the Utils -> New Config trick twice, and rebuilt parity, but it keeps coming up red. This time, I restarted the server trying to resolve a different issue, and that's how it appeared.

 

Attached is a copy of the syslog from boot to the time of posting this plea.

 

EDIT: Also, this isn't related to SNAP, as I mentioned earlier, that was just an example. Would it make more sense to move it back to the main support thread? (Don't really care one way or the other, so long as I can get this resolved.)

syslog.txt

The syslog does not indicate any failures.

Leave it to me to find the difficult problems...  Could it be because of the controller card they're plugged into?

 

I just purchased this: http://www.newegg.com/Product/Product.aspx?Item=N82E16816124060 and have the 1TB that is in the array, but red balling, and the 3TB that I can't get to finish the Disk Pre-Read step of preclear_disk.sh both plugged into it. That seems to indicate a common failure point, however, my cache drive (250GB Samsung 2.5" drive) is also plugged into that card and not having any issues.

 

I've only got 3 drives plugged into the 4 ports of this card, and I did move one SATA cable from one port to another, and that coincided with the 1TB finishing the preclear. I've just swapped the 3TB and the Cache drive ports to see if that's going to have an impact. Upon re-boot, the Cache drive seems to be perfectly funtional, and I've kicked off another preclear attempt on the 3TB.

 

I know the controller is only an x2 card, and that will impact speed, however, for the once monthly parity check I'm not too concerned about speed. It just hit me that having the cache drive on the same controller that the new parity drive will be on (the 3TB, once it's functional) may not be the best bet, so I may do some rearranging in the future, once everything is functional.

Seems that this is a SATA card issue.

 

I pulled the new 4-port card, and put in the old 2-port card I had, and plugged the 3TB into the one remaining port I had. It's now into Step 2 of the pre-clear, having finshed the Pre-Clear-Read, something it's not been able to do with the other card.