unRAID Server Release 6.0-rc3-x86_64 Available


Recommended Posts

search for sharesize in my graylog server, shows 104 instances.

 

all of which are on or after 20/5/15

 

or 5/20/15 in merikan style.

 

is that rc3 release date ?

I've always preferred 2015-05-20 because it's sortable, most significant digits first, etc. Also less ambiguous since I don't think anyone ever swaps month and day in that format.

 

I have them in my log too. No change to disk configuration in months.

 

i'm not getting in to the whole, we are right to write the date dd/mm/yy thing and anyone else who does it differently is just plain wrong, lol.

 

It's a good thing too, cause the correct format is the YYYY-MM-DD.

Link to comment
  • Replies 446
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

i'm not getting in to the whole, we are right to write the date dd/mm/yy thing and anyone else who does it differently is just plain wrong, lol.

 

Having moved to Philippines - everything is so 'American' here - dates always give me a problem every time I have to fill in ('accomplish' in Phil English) a form.  I've now adopted the habit of writing 29 May 2016.

Link to comment

i'm not getting in to the whole, we are right to write the date dd/mm/yy thing and anyone else who does it differently is just plain wrong, lol.

 

Having moved to Philippines - everything is so 'American' here - dates always give me a problem every time I have to fill in ('accomplish' in Phil English) a form.  I've now adopted the habit of writing 29 May 2016.

Peter. Did u see my pm?

Link to comment

search for sharesize in my graylog server, shows 104 instances.

 

all of which are on or after 20/5/15

 

or 5/20/15 in merikan style.

 

is that rc3 release date ?

I've always preferred 2015-05-20 because it's sortable, most significant digits first, etc. Also less ambiguous since I don't think anyone ever swaps month and day in that format.

 

I have them in my log too. No change to disk configuration in months.

 

i'm not getting in to the whole, we are right to write the date dd/mm/yy thing and anyone else who does it differently is just plain wrong, lol.

 

It's a good thing too, cause the correct format is the YYYY-MM-DD.

 

+1111-11-11 :)

Link to comment

search for sharesize in my graylog server, shows 104 instances.

 

all of which are on or after 20/5/15

 

or 5/20/15 in merikan style.

 

is that rc3 release date ?

I've always preferred 2015-05-20 because it's sortable, most significant digits first, etc. Also less ambiguous since I don't think anyone ever swaps month and day in that format.

 

I have them in my log too. No change to disk configuration in months.

 

i'm not getting in to the whole, we are right to write the date dd/mm/yy thing and anyone else who does it differently is just plain wrong, lol.

 

It's a good thing too, cause the correct format is the YYYY-MM-DD.

 

that's just crazy talk.

Link to comment

I think we're all going to have to agree to disagree on the fact that Sparkly is undoubtedly correct, so when's RC4 coming? Hehe, that never fails to generate some controversy, that question!

I'd rather we disagree to agree that sparkly is incorrect.
Link to comment

I think we're all going to have to agree to disagree on the fact that Sparkly is undoubtedly correct, so when's RC4 coming? Hehe, that never fails to generate some controversy, that question!

I'd rather we disagree to agree that sparkly is incorrect.

 

 

the only thing worse than being talked about is not being talked about

Link to comment

We were up late last night putting it through its paces. A few more tweaks before release. The DNS issue with containers is still going to be present for rc4, but we are still tracking that one down. Lots of other bug fixes though.

Link to comment

Working for a large Pharma company as long as I have, I have become accustomed to using GMP format for dates:  29MAY2015.  The FDA requires submissions use this format (and it leaves no room for misinterpretation since I am part of a global team).  :)

 

Of course...sorting is thrown out the window.

Link to comment

We had a 'funny' situation the other day.

 

Writing to our american counterparts the deadline for one of our projects is set to 12-06-2015. Their response: great, that gives us a couple of months to complete!

 

Eh not ...  :)

 

Link to comment

I cant wait for expiration dates when we get international mail order prescriptions...

 

I still realllllllly wish i could spin down my hot swap drives.  Its either run hdparm after boot, or unplug them till something redballs.  And no i dont have hot swap bays. 

Link to comment

I cant wait for expiration dates when we get international mail order prescriptions...

 

I still realllllllly wish i could spin down my hot swap drives.  Its either run hdparm after boot, or unplug them till something redballs.  And no i dont have hot swap bays.

 

There's a feature called power up in standby.

 

The drive will stay in standby until polled or examined by the kernel.

http://en.wikipedia.org/wiki/Power-up_in_standby

 

I'm not sure of the hdparm -S### spindown timer settings are remembered over a power cycles.

I vaguely recollect there was some option to enable it to be remembered.

 

There is also the possibility of using udev rules, which could possibly be set from the unassigned devices plugin.

 

excerpt from https://wiki.archlinux.org/index.php/Hdparm

Persistent configuration using udev rule
To make the setting persistent, adapt the following udev rule for your values:
/etc/udev/rules.d/50-hdparm.rules
ACTION=="add", SUBSYSTEM=="block", KERNEL=="sda", RUN+="/usr/bin/hdparm -B 254 -S 0 /dev/sda"
If you have more than one hard drive you could make the rule more flexible. For example, to apply power-saving settings for all external drives (assuming there is only one internal drive, /dev/sda):
/etc/udev/rules.d/50-hdparm.rules
ACTION=="add|change", KERNEL=="sd[b-z]", ATTR{queue/rotational}=="1", RUN+="/usr/bin/hdparm -B 127 -S 12 /dev/%k"
Tips and tricks

 

I used to have a scriptlet in my config/go file that would set the power up in standby and -S### standby timers using the /dev/disk/by-id devices. This enabled them to move around from sd{whatever} and still be set accordingly.

 

https://wiki.archlinux.org/index.php/Hdparm

Link to comment

 

We had a 'funny' situation the other day.

 

Writing to our american counterparts the deadline for one of our projects is set to 12-06-2015. Their response: great, that gives us a couple of months to complete!

 

Eh not ...  :)

Haha that's awesome!

Link to comment

Anyone figure out what this could be?

 

May 28 17:27:22 SUN avahi-dnsconfd[6314]: Successfully connected to Avahi daemon.

May 28 17:27:22 SUN emhttp: shareColor.0 not found

May 28 17:27:22 SUN emhttp: shareFree.0 not found

May 28 17:27:22 SUN emhttp: shareSize.0 not found

May 28 17:27:22 SUN emhttp: shareColor.1 not found

May 28 17:27:22 SUN emhttp: shareFree.1 not found

May 28 17:27:22 SUN emhttp: shareSize.1 not found

May 28 17:27:22 SUN emhttp: shareColor.2 not found

May 28 17:27:22 SUN emhttp: shareFree.2 not found

May 28 17:27:22 SUN emhttp: shareSize.2 not found

May 28 17:27:22 SUN emhttp: shareColor.3 not found

May 28 17:27:22 SUN emhttp: shareFree.3 not found

May 28 17:27:22 SUN emhttp: shareSize.3 not found

May 28 17:27:22 SUN emhttp: shareColor.4 not found

May 28 17:27:22 SUN emhttp: shareFree.4 not found

May 28 17:27:22 SUN emhttp: shareSize.4 not found

May 28 17:27:22 SUN emhttp: shareColor.5 not found

May 28 17:27:22 SUN emhttp: shareFree.5 not found

May 28 17:27:22 SUN emhttp: shareSize.5 not found

May 28 17:27:22 SUN emhttp: shareColor.6 not found

May 28 17:27:22 SUN emhttp: shareFree.6 not found

May 28 17:27:22 SUN emhttp: shareSize.6 not found

May 28 17:27:22 SUN emhttp: shareColor.0 not found

May 28 17:27:22 SUN emhttp: shareFree.0 not found

May 28 17:27:22 SUN emhttp: shareSize.0 not found

May 28 17:27:22 SUN emhttp: shareColor.1 not found

May 28 17:27:22 SUN emhttp: shareFree.1 not found

May 28 17:27:22 SUN emhttp: shareSize.1 not found

May 28 17:27:22 SUN emhttp: shareColor.2 not found

May 28 17:27:22 SUN emhttp: shareFree.2 not found

May 28 17:27:22 SUN emhttp: shareSize.2 not found

May 28 17:27:22 SUN emhttp: shareColor.3 not found

May 28 17:27:22 SUN emhttp: shareFree.3 not found

May 28 17:27:22 SUN emhttp: shareSize.3 not found

May 28 17:27:22 SUN emhttp: shareColor.4 not found

May 28 17:27:22 SUN emhttp: shareFree.4 not found

May 28 17:27:22 SUN emhttp: shareSize.4 not found

May 28 17:27:22 SUN emhttp: shareColor.5 not found

May 28 17:27:22 SUN emhttp: shareFree.5 not found

May 28 17:27:22 SUN emhttp: shareSize.5 not found

May 28 17:27:22 SUN emhttp: shareColor.6 not found

May 28 17:27:22 SUN emhttp: shareFree.6 not found

May 28 17:27:22 SUN emhttp: shareSize.6 not found

May 28 17:27:22 SUN emhttp: Starting Docker...

May 28 17:27:22 SUN logger: /usr/bin/docker not enabled

 

Link to comment

Trying to setup a KVM for the first time...

 

I downloaded Linux Mint (both 64 and 32 bits just to see if that was the issue), but regardless of what I try, I get the following error:

 

Error creating VM: internal error: process exited while connecting to monitor: 2015-05-28T19:18:12.791976Z qemu-system-x86_64: -drive file=/mnt/user/VMs/LinuxMint/vdisk1.img,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native: Could not find working O_DIRECT alignment. Try cache.direct=off.

 

Nothing Fancy in the setup:

- I've defined br0 under network settings

- I've created a share for the ISOs and a Share for the VMs

- I've assigned br0 in the VM Manager page

- Click "Add VM" and:

--- OS = Linux

--- Passthrough CPU

--- Using Core 0 and Core 1  (out of 4 cores)

--- Init Ram 512MB (out of 4GB)

--- Graphics Card = VNC  (it's a headless computer)

--- Soundcard None

--- USB devices None checked (option being UPS)

--- BIOS = SeaBIOS

--- Machine --> Tried both i440 and q35

 

Any tips?

This is a bug that will be fixed in an upcoming release that only affects users creating vdisks on non-btrfs formatted devices and when traversing through user shares. See this to fix:

 

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

 

Perfect thank you!  Indeed that fixed the issue...  Even my old VM ran!

Link to comment

We were up late last night putting it through its paces. A few more tweaks before release. The DNS issue with containers is still going to be present for rc4, but we are still tracking that one down. Lots of other bug fixes though.

 

Thanks Jon.

 

Is there more information about what the DNS issue is? I don't seem to have any issues with my docker containers (currently on RC3), so just curious what the issue is and if it might show up for me when I do upgrade to RC4.

Link to comment

We were up late last night putting it through its paces. A few more tweaks before release. The DNS issue with containers is still going to be present for rc4, but we are still tracking that one down. Lots of other bug fixes though.

 

Thanks Jon.

 

Is there more information about what the DNS issue is? I don't seem to have any issues with my docker containers (currently on RC3), so just curious what the issue is and if it might show up for me when I do upgrade to RC4.

 

Hopefully, if this is still a known issue, the details you requested will be posted in the Change Notes.  That way it is not buried somewhere in a thread of some 400+ posts.

Link to comment

Just a quick question, but with the 6.0-rc3 version of UnRaid, do you have to go in and restart the ACUPSD manually anytime the server has to be restarted?  I just noticed that I can go into the UPS Settings and even though "Start APC UPS daemon" is set to "Yes" it doesn't start up on boot.  I have to change any one of the settings and hit "Apply" and it starts and runs until a restart.  I know it said with rc3 that you had to go in and turn it back on and apply settings because of changes, but didn't think you had to do that every time the server had to restart (such as after a power outage etc).

 

Thanks,

 

Pete

Link to comment

Just a quick question, but with the 6.0-rc3 version of UnRaid, do you have to go in and restart the ACUPSD manually anytime the server has to be restarted?  I just noticed that I can go into the UPS Settings and even though "Start APC UPS daemon" is set to "Yes" it doesn't start up on boot.  I have to change any one of the settings and hit "Apply" and it starts and runs until a restart.  I know it said with rc3 that you had to go in and turn it back on and apply settings because of changes, but didn't think you had to do that every time the server had to restart (such as after a power outage etc).

There is an issue in rc3 where the 'executable' bit is not set on one of the ACUPSD related files.  Until rc4 is available a workaround is to add

chmod 744 /usr/local/emhttp/plugins/dynamix.apcupsd/event/driver_loaded

to the top of the 'go' file.

Link to comment
Guest
This topic is now closed to further replies.