By default, how often will unRAID perform a parity check?

 

By default, only when the array isn't properly shut-down.

 

Peter

 

Hi!

 

Thanks for the input. Originally I switched to 5.0 to use AFP. My Mac is gone and I only have a Windows 7 machine here. So...no need to upgrade. Until the next Beta I will keep 4.7.

 

Bye.

Hi!

 

No. The LOGROTATE error is still there and all drives are spinning.:-(

 

Bye.

The "logrotate" errors are there for everybody. here are some of mine...

Apr 22 04:40:01 Tower2 logrotate: ALERT - exited abnormally.

Apr 23 04:40:01 Tower2 logrotate: ALERT - exited abnormally.

Apr 24 04:40:01 Tower2 logrotate: ALERT - exited abnormally.

Just updated to beta6a, and all in all its been a smooth transition. 

 

One question I have relates to the user shares screen.  Why would some of my user shares have orange/red dots next to them, instead of the pleasant looking green dots?

Just updated to beta6a, and all in all its been a smooth transition. 

 

One question I have relates to the user shares screen.  Why would some of my user shares have orange/red dots next to them, instead of the pleasant looking green dots?

Orange indicates a file is on the cache drive.  (not sure about red)

hi folks, i just tried upgrading from 4.7 so i could try out the new plex media server, but 2 drives came up missing (which i now realise means i just needed to re-assign them on the devices page) and all but the parity drive showed as mbr unknown, syslog attached, not sure what i need to do to be able to bring it back online?

thanks

syslog-2011-05-15.txt

WngmanNZ - Did the system come up with all green indicators after the parity build completed? If so, then I doubt it clearing the drives again but look in the syslog because there should be a percent complete logged in there if it is clearing. And if you find it, then this is an issue with the OS to report.

 

It sounds to me that the OS is having trouble formatting that many drives at once. You may have to manually format some or all of them. I believe the formatting can be done like so;

 

mkreiserfs -q /dev/mdX  where X is the drive number.

 

Hopefully, someone else will confirm.

 

The thing is probably hung-up trying to format so you would either have to try and kill any format processes and emhttp and then restart emhttp (/usr/local/sbin/emhttp &) or just hard reset and endure another parity check. You can do the manual formats and such during the new parity check though - the mdX devices refer to the parity protected disks so any command line operation to an mdX device maintains parity.

 

You could do a small array and then adding a few drives at a time but that would require you to preclear again or let the server clear the disks. There is a preclear option to just zero the drives which makes it quicker but still, it's 6 or 8 hours per drive you shouldn't have to spend.

 

You could also simply add a few data disks with an initconfig and format them, then add a few more and format them, continuing until all the data disks are in place. Then, assign the parity and build the initial parity. unRAID won't clear the data disks when there is no parity disk assigned.

 

Peter

 

 

 

Turns out it was the format tasks failing due to the parity sync eating up all the IO, I repeated my process again but this time waited for the parity to sync 100% then hit format., about 10min later all drvies were formatted nicely

 

I have since added 4x 2TB drives so I now have 20TB of protected storage and still room for another 7x 2TB Drives

 

I am using unRAID without Cache and getting really good write speed. about 39-45MB/sec (depending on file size)

So, overall what's the status on 5.0 beta 6a? Is it stable enough for production boxes? I think I'd love to have the AFP, SMB works on my mac, but it's not quite as seamless as I'd like. From my understanding I could have AFP drives automagically mount on boot, where with SMB I have to either run a script or select them from the finder (which is you know, a pain. Hey, what can I say, I'm lazy!)

 

Or would I be better off waiting like a child on christmas eve? FYI My unraid box is a supermicro ion board w/ too many harddrives to count and data that I'd prefer to to be molested in any shape or form.

 

Crap, I think I just answered my own question. I'll wait.

 

So, overall what's the status on 5.0 beta 6a? Is it stable enough for production boxes? I think I'd love to have the AFP, SMB works on my mac, but it's not quite as seamless as I'd like. From my understanding I could have AFP drives automagically mount on boot, where with SMB I have to either run a script or select them from the finder (which is you know, a pain. Hey, what can I say, I'm lazy!)

 

Or would I be better off waiting like a child on christmas eve? FYI My unraid box is a supermicro ion board w/ too many harddrives to count and data that I'd prefer to to be molested in any shape or form.

 

Crap, I think I just answered my own question. I'll wait.

 

 

You can use my script on the previous version too, mounts either SMB or AFP shares automatically. OS X will automatically mount any drive you want as a login item, but it's pretty useless at times. My script will keep the drives mounted at all times, so I still use it even on the latest 5 beta.

 

http://lime-technology.com/forum/index.php?topic=10274.0

Has anybody seen this after upgrade from 4.7?

I've followed the instructions in Release Notes.

Basically, the GUI is broken after the upgrade as shown in the attachment.

So, overall what's the status on 5.0 beta 6a? Is it stable enough for production boxes?

 

Other than the problem with drives which have been 'tampered' with by forces outside of unRAID, I don't think anyone has had any problems with corruption of data.  I've been using 5.0 beta6 since March 1, and have had no problems. As far as I'm concerned, it's as stable as any production release.

Has anybody seen this after upgrade from 4.7?

I've followed the instructions in Release Notes.

Basically, the GUI is broken after the upgrade as shown in the attachment.

 

 

Do you have any 3rd party utlities/php servers installed? Essentially the PHP server you're running isn't recognising php short tags.

 

Thanks! It was unraidweb package.

 

Has anybody seen this after upgrade from 4.7?

I've followed the instructions in Release Notes.

Basically, the GUI is broken after the upgrade as shown in the attachment.

 

 

Do you have any 3rd party utlities/php servers installed? Essentially the PHP server you're running isn't recognising php short tags.

 

Thanks! It was unraidweb package.

 

Has anybody seen this after upgrade from 4.7?

I've followed the instructions in Release Notes.

Basically, the GUI is broken after the upgrade as shown in the attachment.

 

 

Do you have any 3rd party utlities/php servers installed? Essentially the PHP server you're running isn't recognising php short tags.

Yes, you yourself broke it with the installation of one of the add-ons that also install "php"

 

The fix is simple, you need to add a line in your "go" script to enable the use of the short-tags in the version of php you installed.

 

see here:

http://lime-technology.com/forum/index.php?topic=10925.msg103866#msg103866

 

 

Yes, you yourself broke it with the installation of one of the add-ons that also install "php"

 

 

Just upgraded from Beta4. All of my MBR's were correct. assigned all the disks, started the array and its forcing a parity check, which I am good with but its telling me my parity disk in invalid.

 

Does it say INVALID_DISK just because it needs to check the parity?

Just upgraded from Beta4. All of my MBR's were correct. assigned all the disks, started the array and its forcing a parity check, which I am good with but its telling me my parity disk in invalid.

 

Does it say INVALID_DISK just because it needs to check the parity?

Yes.

Thanks for quick response!

 

Just upgraded from Beta4. All of my MBR's were correct. assigned all the disks, started the array and its forcing a parity check, which I am good with but its telling me my parity disk in invalid.

 

Does it say INVALID_DISK just because it needs to check the parity?

Yes.

Since I upgraded from 4.7 my server locks up during backup of a few VMs on my ESXi NFS store epxorted from the unraid server.

It happened now 2 times in a row. The backup job runs nightly and I have been using same setup (ghettobackup2.pl script running on vMA appliance) for long time and it never had problems before the upgrade. There is nothing in the syslog at the time, but I can observe tons (150+) smbd processes in "D" state (from "man ps": Uninterruptible sleep (usually IO)). The problem is unlikely related to samba since there is 0 windows related traffic at the time - only NFS.

It looks like the system locks during intensive NFS I/O. Though there was one or two nights when the backups completed with no problems.

Does any of you use unraid 5.0b6a as NFS server intensively? Have you ever seen what I described? Is there any known problems with NFS in the current version?

 

 

 

 

So, overall what's the status on 5.0 beta 6a? Is it stable enough for production boxes?

 

Other than the problem with drives which have been 'tampered' with by forces outside of unRAID, I don't think anyone has had any problems with corruption of data.  I've been using 5.0 beta6 since March 1, and have had no problems. As far as I'm concerned, it's as stable as any production release.

 

Well, decided to take the plunge. So far so good, waiting for the new permissions script to continue, but looks good so far.

Yup, seems to be working well. All disks showed up, array started nicely, permissions took a while however. Up and running, and it's accepting my time machine backups.

 

---- edit

I should mention stats I suppose

 

7x1.5 TB Samsung HD154UI

2x.5 tb Hitachi hd72505

1x.5 tb seagate st3500

 

Supermicro MBD_X7SPA-H-O

SuperMicro AOC-SASLP-MV8 PCIE

2gb corsair

Is there some trick to getting the setting to have the array auto start to stick?  I keep setting it and the array keeps not starting automatically.

Try setting Autostart to "No".  Apply the settings, and restart.

 

Then set Autostart to "Yes", apply, and restart again.

 

It should autostart now, but let us know if it doesn't.  I had the same problem too, and I think that's what resolved it.

 

dimaestro: Are you using AFP, SMB, or NFS?  What version of OS X are you using? I'm having lots of problems mounting and/or keeping shares mounted (user shares, at least) on my Mac.

Is there some trick to getting the setting to have the array auto start to stick?  I keep setting it and the array keeps not starting automatically.

 

Make sure you don't have any parity issues or drive misplacement issues... if you do the array needs confirmation that the configuration is ok before it starts.

Try setting Autostart to "No".  Apply the settings, and restart.

 

Then set Autostart to "Yes", apply, and restart again.

 

It should autostart now, but let us know if it doesn't.  I had the same problem too, and I think that's what resolved it.

 

 

Thanks,  I will try it.