Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

unRAID Server Release 5.0-beta7 Available

Featured Replies

Tom -

 

Another small defect has to do with the spindown value being "" rather than "-1" in disk.cfg.  Both madburg and I both experienced this with beta7 which prevented disk spindown from working properly.

 

See HERE for more details.

  • Replies 333
  • Views 140.6k
  • Created
  • Last Reply
  • Author

Tom -

 

Another small defect has to do with the spindown value being "" rather than "-1" in disk.cfg.  Both madburg and I both experienced this with beta7 which prevented disk spindown from working properly.

 

See HERE for more details.

I saw that but I have not looked into where/how the field is getting set to ""... can you make this happen?  (If so, let me know, it would save some time).  thanks.

Tom -

 

Another small defect has to do with the spindown value being "" rather than "-1" in disk.cfg.  Both madburg and I both experienced this with beta7 which prevented disk spindown from working properly.

 

See HERE for more details.

I saw that but I have not looked into where/how the field is getting set to ""... can you make this happen?  (If so, let me know, it would save some time).  thanks.

 

I witnessed this as of 5.0Beta6d which was the first version I was able to test my sas controllers with unRAID natively spinning down/up my drives when manually clicking the button.

 

If I started from scratch (wipe USB stick) and took a copy of what the disk.cfg file was, then added a few disks to the array, again take a copy of the disk.cfg file, then set the global disk settings to 15mins, once again take a copy of the disk.cfg then wait 15 mins it will not spin any of them down automatically, select one disk and just click apply (it will now spin this one disk automatically), once again take a copy of the disk.cfg. Add an additonal disk to the array (it will not be automatically spun down)and once again take a copy of the disk.cfg file and email them over to you with what disks I did hat with (details) would that work or is there something else you would like with this?

Tom -

 

Another small defect has to do with the spindown value being "" rather than "-1" in disk.cfg.  Both madburg and I both experienced this with beta7 which prevented disk spindown from working properly.

 

See HERE for more details.

I saw that but I have not looked into where/how the field is getting set to ""... can you make this happen?  (If so, let me know, it would save some time).  thanks.

 

Steps to reproduce:

 

Stop array

Backup your disk.cfg and super.dat files (and delete them from /boot/config)

Copy default disk.cfg from distribution .zip file to /boot/config

Reboot

Assign parity disk to parity slot

Click hyperlink "parity" under Device column heading

Click apply

 

Look at the disk.cfg.  The "diskSpinDownDelay.0 is "-1".  But every other diskSpinDownDelay.x is "".

 

Now unassign parity

 

Assign an array disk to disk1 slot.

 

Start the 1 disk "array".

 

Look at disk.cfg.  No change.  Disk.1 will never go to sleep, unless you click the "disk1" device and click apply.  You have to do same for every slot to fix all of the disks.

 

Stop the array

Restore your disk.cfg / super.dat files

Reboot

 

Hope this help!

Jeez, I'd better look into this.

 

I disabled spin-up groups, and just use the "cache_dirs" script, and have a disk spin up when it's needed.

 

But I'm not sure what makes them spin down--I guess whatever we configured initially is how it'll be, right? I believe I set that to "spin down after 1 hour of inactivity"

I bit the bullet and updated. I thought I was prepared but I had overlooked the one time permision reset and the PHP could not be installed by unmenu.

 

I do see the bug where unmenu does not show the unraid main but if you go directly it works... It does work some times I just dont know why.

 

the rest looks really good I am using my UPS and Twonky media with no problems.

 

Here are a few lines in my syslog I dont understand. syslog attached.

Jun 12 13:54:24 Dragon-Tower kernel:     ide0: BM-DMA at 0xff00-0xff07

Jun 12 13:54:24 Dragon-Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled (Errors)

Jun 12 13:54:24 Dragon-Tower kernel: ide1: DMA disabled (Errors)

Jun 12 13:54:24 Dragon-Tower kernel: Probing IDE interface ide0...

Refer to this thread:

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

 

Jun 12 15:15:18 Dragon-Tower kernel: twonkymediaserv[1391]: segfault at 30d0 ip 0806db70 sp b76a8af0 error 4 in twonkymediaserver[8048000+69000] (Errors)

This one is not good, says that a twonkymediaserv process crashed (probably due to programming error).  Sorry can't help with this one.

 

Jun 12 15:40:01 Dragon-Tower crond[1232]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jun 12

This was fixed several releases back, should not occur with -beta7.  Can't explain it, perhaps an add-on?

 

most all the add-ons that add cron entries create this file because older releases of unRAID used it instead of re-reading the output of crontab -l.   Therefore, to fix it is easy, delete the file in

/var/spool/cron/crontabs/root-

or ignore the warning, it is harmless.

 

Thank you very much for your help Tom and Joe.

 

Do you have to delete root- every boot? or just once?

 

if it is every boot how would I put it in the go script?

 

Thank you again

add the following line at the end of the "go" script:

rm /var/spool/cron/crontabs/root-

1. Support of hard drives larger than 2TB.

 

 

lol, so true.

Ok, so this new version supports the use of 3TB hard drives. Yea!

 

 

Unanswered question... If I'm running the original Promise SATA300 TX4 SATA II cards

Can I just pop a 3.0Gb/s drive in, start up the new version and it'll work with UnRaid on this beta, or will 3TB drives require a hardware controller upgrade to work?

Like everything related to computers, you will need proper hardware support.

 

You'll need to find out if that controller supports drives > 2.2TB or not. Not all/many controllers do.

You'll need to find out if that controller supports drives > 2.2TB or not. Not all/many controllers do.

 

While other people are saying that most controllers do work with >2.2TB drives.  The suggestion is that the only thing which may not work is booting from a large drive - not something which will be a problem in an unRAID server

Yeah-

I asked here because the Promise SATA300 TX4 SATA II cards were standard spec for many years on the unraid builds, so I figured others here may have tried on these controllers by now.

 

May be worth a try...

This announcement thread is for use to discuss issues with the 5.0beta7. 

 

I have answered this question in THIS THREAD over in the "Hard Drives and Controllers" sub-forum.

After upgrading, running the 'New Permissions' script, and recreating my shares they are all still 'blank'.

Any other thoughts how to get the shares which exist on the Drives to re-associate?

 

 

After upgrading, running the 'New Permissions' script, and recreating my shares they are all still 'blank'.

Any other thoughts how to get the shares which exist on the Drives to re-associate?

 

 

stop and re-start the array.

just a heads up, currently have one 3TB Hitachi successfully pre-cleared and running in the server, second 3TB pre-clear is 12 hours away from finishing (knock on wood, power keeps going out due to storms, don't have UPS on new machine) and will start updating parity tomorrow if all goes as planned.  Running off of new motherboard http://www.newegg.com/Product/Product.aspx?Item=N82E16813138308

 

Josh

Heads up... we will have cake in 3 weeks !!! :)

 

The cake is a lie!

Heads up... we will have cake in 3 weeks !!! :)

 

Does it come,

 

"I scream" with cake; or do i get served cake and Ice-cream.  ;D

 

hoping its the latter part.

Is there any reason I should update to this given I don't use >2TB drives and use SATA?

 

Any improvements in AFP?

ok I must be stupid but I can't figure out how to get my flash drive to show up with my other drives.  Where do I do this at, I think I have set to hidden

Heh, i even replied to that. In that case, I'll be staying with 5b6!

ok I must be stupid but I can't figure out how to get my flash drive to show up with my other drives.  Where do I do this at, I think I have set to hidden

 

Click on the flash drive on the Main page of webGUI, and you can set the export/share settings there.

 

Also, if you're trying through AFP, it won't show up there--only through Samba.

Thank you, it was the samba setting

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.