unRAID Server Release 6.0-beta4-x86_64 Available

[gwl]

In addition if xenman finds an icon file in the directory that contains your xen configfile, it will copy it to "config/domains/archVM.png".  The name of the icon file in the domain directory can be either "icon.png" or "<domname>.png" ("archVM.png" in our example).

 

This is the icon that xenman shows in the Domain List, letting you assign a “custom” icon for the domain.  For example, say you download an appliance template with a generic icon.  If you download your own png file, name it after your domain, and then copy into /boot/config/domains/<domname>.png, you now have a custom icon.

 

I've found a reasonable image size of 52x52 pixels to be fair when resizing/customising images for the displayed domain icon.

Another one for that rainy day....for convenience (and laziness), is it possible to integrate the downsizing of icon images automatically within the webGUI code?

 

cheers,

gwl

 

cheers,

gwl

[pinion]

 

Hello All...

 

I hope this is not an out of line question.  Is anyone running this 6.0.4beta in their production servers or just on the test servers.

I was thinking of putting together another server box and starting from scratch with this beta. 

 

Best Regards,

Jim

 

I'm running in "production" but most of my data is stuff that would suck to lose but not the end of the world. I have backups of my important stuff (Pictures etc...) That said I haven't had any problems with beta 3 or this beta.

 

 

Sent from my iPhone using Tapatalk

[PeterB]

Is anyone running this 6.0.4beta in their production servers or just on the test servers.

 

I'm running on my one and only server without problem (so far!).  I'm having great fun with setting up many of my v5 plugins as applications running on a VM.

 

I moved to v5 with beta 4, too, and have never run unto any problems with data loss.

[binhex]

me too, im also running on my one and only "production system", no issues at all as far as core unraid platform goes, xen is also working well, ive had xen blow up once on me (did not cause instability with host) but apart from that its all been good.

 

be aware cache_dirs and also pre-clear do not currently work well with ver 6.

[jim7fl]

me too, im also running on my one and only "production system", no issues at all as far as core unraid platform goes, xen is also working well, ive had xen blow up once on me (did not cause instability with host) but apart from that its all been good.

 

be aware cache_dirs and also pre-clear do not currently work well with ver 6.

 

would it be possible to do the pre-clear with 5.05 and then put the drives in this beta?

[binhex]

me too, im also running on my one and only "production system", no issues at all as far as core unraid platform goes, xen is also working well, ive had xen blow up once on me (did not cause instability with host) but apart from that its all been good.

 

be aware cache_dirs and also pre-clear do not currently work well with ver 6.

 

would it be possible to do the pre-clear with 5.05 and then put the drives in this beta?

 

i cant see why you couldn't do that, in any case the pre-clear issue is being actively worked on and i think the guys know how to fix it so i dont think it will be long until it's resolved.

[Thornwood]

Thank you now I can understand that.

 

Thank you again.

 

 

Thornwood

[clowrym]

Hello All...

 

I hope this is not an out of line question.  Is anyone running this 6.0.4beta in their production servers or just on the test servers.

I was thinking of putting together another server box and starting from scratch with this beta. 

 

Best Regards,

Jim

 

Running it on my production server as well & I have been running it on my test server to learn VM's

[limetech]

Makes sense. Could we handle more than one release of the same plugin in one day with that scheme i.e. oh sh*t thats not right better fix that

 

Yes, add a suffix, eg, "2014.04.04a" which will compare as newer than "2014.04.04", though older than "2014.04.05".

 

It's using php's "strcmp()" function.

http://www.php.net/manual/en/function.strcmp.php

[limetech]

Hello All...

 

I hope this is not an out of line question.  Is anyone running this 6.0.4beta in their production servers or just on the test servers.

I was thinking of putting together another server box and starting from scratch with this beta. 

 

Best Regards,

Jim

 

We have since -beta1.

[jim7fl]

Before you say this is off topic, hear me out.

 

I have a setup with 5.05 installed and have had a lot of issues (likely caused by stumbling around in the dark instead of reading ALL of the instructions before typing).

 

I cannot get any plugins to persist for a reboot.  SSH, etc.  Also, my plex server plugin worked perfect on first install, and hasn't worked since.  In fact, it is now saying that a server I tested 2 months ago is available, and it cannot be available.

 

All that aside, here is the crux of the matter:  I have about 300-400 gb of data on one of my data drives.  My unraid 5.05 did a parity check today with no errors.

 

Here is the question:  If I completely wipe my usb drive and start over installing this latest beta, and only select my two data drives initially and then select parity and turn it on, will any of my 300 GB+ of files be in danger?    Second question:  is there any kind of example to follow for "upgrading" from unRaid Plus to unRaid Plus Beta?

 

I do realize the only difference in basic and plus is (other than supporting the development with some $$), increased functionality of being able to have cache drive and and/or more than 2 data disks, neither of which are important at the moment.  I just want to do a new install without damaging my current data files.

 

Thanks in advance for putting up with my noob questions.  Even though I started with DOS1.0 and Basic 1.0 in the early 80's.

 

 

[jphipps]

I have also been running my 2 servers since beta1 without any issues... I even had a disk failure right after updating to beta4, and rebuilt with a replacement drive without any issues.

[NAS]

Makes sense. Could we handle more than one release of the same plugin in one day with that scheme i.e. oh sh*t thats not right better fix that

 

Yes, add a suffix, eg, "2014.04.04a" which will compare as newer than "2014.04.04", though older than "2014.04.05".

 

It's using php's "strcmp()" function.

http://www.php.net/manual/en/function.strcmp.php

 

Superb, just a sanity check when I thought if it. Thanks for the clear up

[SergeantCC4]

Can anyone clarify the upgrade directions? I'm running beta-3 but the directions only specify beta-1/2. Is it the same as 1/2 or not? because it looks like more file are brought over in the 1/2.

[sadkisson]

I upgraded same as beta 1 and 2.

[Helmonder]

Smb mounts seem to be readonly..

[pinion]

 

Can anyone clarify the upgrade directions? I'm running beta-3 but the directions only specify beta-1/2. Is it the same as 1/2 or not? because it looks like more file are brought over in the 1/2.

I upgraded by redoing the flash drive from scratch (after backing it up) and then I copied the contents of my config directory without the plugins. Worked great for me.

 

 

Sent from my iPhone using Tapatalk

[earthlyreaper]

For some reason,

since my upgrade I keep getting this:

Apr  6 02:41:52 Trauma-unRAID kernel: BUG: unable to handle kernel NULL pointer dereference at          (null)

Apr  6 02:41:52 Trauma-unRAID kernel: IP: [<          (null)>]          (null)

Apr  6 02:41:52 Trauma-unRAID kernel: PGD 1f9f8a067 PUD 1f9f89067 PMD 0

Apr  6 02:41:52 Trauma-unRAID kernel: Oops: 0010 [#1] SMP

Apr  6 02:41:52 Trauma-unRAID kernel: Modules linked in: md_mod coretemp hwmon mperf ata_piix i2c_i801 i2c_core r8169 ahci libahci mvsas libsas scsi_transport_sas [last unloaded: md_mod]

Apr  6 02:41:52 Trauma-unRAID kernel: CPU: 0 PID: 9950 Comm: chmod Not tainted 3.10.24p-unRAID #15

Apr  6 02:41:52 Trauma-unRAID kernel: Hardware name: Supermicro C2SEA/C2SEA, BIOS 1.0c 03/11/2009

Apr  6 02:41:52 Trauma-unRAID kernel: task: ffff88022c608d00 ti: ffff8801d40ee000 task.ti: ffff8801d40ee000

Apr  6 02:41:52 Trauma-unRAID kernel: RIP: 0010:[<0000000000000000>]  [<          (null)>]          (null)

Apr  6 02:41:52 Trauma-unRAID kernel: RSP: 0018:ffff8801d40efc18  EFLAGS: 00010246

Apr  6 02:41:52 Trauma-unRAID kernel: RAX: ffffffff814b4ec0 RBX: ffff88018aaa9d80 RCX: 0000000000000000

Apr  6 02:41:52 Trauma-unRAID kernel: RDX: 0000000000000000 RSI: ffff88018aaa9d80 RDI: ffff88018aad23f0

Apr  6 02:41:52 Trauma-unRAID kernel: RBP: ffff8801d40efc30 R08: ffff88018aaa9d80 R09: 0000000000015c30

Apr  6 02:41:52 Trauma-unRAID kernel: R10: 00000000ffffffff R11: 0000000000000000 R12: ffff88018aaa9cc0

Apr  6 02:41:52 Trauma-unRAID kernel: R13: ffffffff815a0566 R14: 00000000ffffffff R15: ffffffff815a0566

Apr  6 02:41:52 Trauma-unRAID kernel: FS:  00002addc2c3cb80(0000) GS:ffff880237c00000(0000) knlGS:0000000000000000

Apr  6 02:41:52 Trauma-unRAID kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b

Apr  6 02:41:52 Trauma-unRAID kernel: CR2: 0000000000000000 CR3: 00000001f9f5f000 CR4: 00000000000007f0

Apr  6 02:41:52 Trauma-unRAID kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

Apr  6 02:41:52 Trauma-unRAID kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

Apr  6 02:41:52 Trauma-unRAID kernel: Stack:

Apr  6 02:41:52 Trauma-unRAID kernel:  ffffffff810d3f14 0000000000000000 ffff88018aaa9cc0 ffff8801d40efc58

Apr  6 02:41:52 Trauma-unRAID kernel:  ffffffff810d4915 0100000000000038 ffff88018aaa9cc0 0000000000000017

Apr  6 02:41:52 Trauma-unRAID kernel:  ffff8801d40efc90 ffffffff810d6e65 00000017c6445a83 ffffffff815a0566

Apr  6 02:41:52 Trauma-unRAID kernel: Call Trace:

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810d3f14>] ? lookup_real+0x27/0x42

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810d4915>] __lookup_hash+0x2b/0x31

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810d6e65>] lookup_one_len+0xdb/0xee

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff8113783d>] xattr_lookup+0x55/0xf0

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff81137e5d>] reiserfs_xattr_get+0x3f/0x232

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff81138e4a>] reiserfs_get_acl+0xb0/0x37d

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff811393d0>] reiserfs_acl_chmod+0x5c/0x19c

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff814a20cb>] ? _raw_spin_lock+0x9/0xd

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810e9a25>] ? __mark_inode_dirty+0x1ca/0x1f0

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff811221b8>] reiserfs_setattr+0x26b/0x29f

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810ce39a>] ? __sb_start_write+0xb8/0xec

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810e1442>] notify_change+0x1b1/0x27e

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810cb028>] chmod_common+0x63/0x86

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff810cbdfd>] SyS_fchmodat+0x3f/0x77

Apr  6 02:41:52 Trauma-unRAID kernel:  [<ffffffff814a2de9>] system_call_fastpath+0x16/0x1b

Apr  6 02:41:52 Trauma-unRAID kernel: Code:  Bad RIP value.

Apr  6 02:41:52 Trauma-unRAID kernel: RIP  [<          (null)>]          (null)

Apr  6 02:41:52 Trauma-unRAID kernel:  RSP <ffff8801d40efc18>

Apr  6 02:41:52 Trauma-unRAID kernel: CR2: 0000000000000000

Apr  6 02:41:52 Trauma-unRAID kernel: ---[ end trace 1e2c7c8588174fc3 ]---

 

 

 

Here is the link to my syslog

I tried to debug this thing a bit by myself, but didn't seem to find any answer.

The downside of this error is that it makes all my shares hang, so it makes my system unusable.

 

Also a worthy note, I also tried to downgrade it back, but now the error remains.

(clueless here)

If I should repost it somewhere else, because the error remains when I downgrade,

please let me know.

 

I also noticed I can reproduce it while accessing certain folders.

Even from unraid itself, it gives me the error and hangs.

noticed it was when trying to access:

  - /mnt/disk9/Series/Hemlock Grove

  - /mnt/disk9/Movies/Innocent Garden (2013)

 

Also, a warning I tend to get a log is:

REISERFS warning (device md9): jdm-20001 reiserfs_xattr_get: Invalid magic for xattr (system.posix_acl_default) associated with [10 1130 0x0 SD]

but not sure if it's related

[craemer]

I am having issues getting plex to add media to the database when using samba shares across multiple platforms.

 

I tried running a tretflix vm and could get all the download apps to work and move files around no problems but plex for some reason can't see add any files in the folders.

 

I also tried running archvm and plex would mostly work on nfs shares but I would have to refresh the database several times for it to really find everything.

 

On samba I'm also seeing two nameless folders in my Movies share that seem to link back to themselves. So if I click the unnamed folder it just stays in the same folder. I can't delete them because it tries to delete the entire folder. I've attached a screenshot of the two folders as seen in windows explorer and plex. I'm very confused. I think there's something bigger going on here but I can't figure it out.

[trurl]

...Also a worthy note, I also tried to downgrade it back, but now the error remains.

(clueless here)

If I should repost it somewhere else, because the error remains when I downgrade,

please let me know.

...

Probably not related to this release then. Before you post it somewhere else though, try booting in safe mode and see if it goes away.

 

Are you sure all of the plugins you are trying to install are 64bit?

[dlandon]

Tom,

 

xen safe mode still loads plugins.

[devanchya]

I'm a bit confused.

We had a power failure today, and apparently one of my drive housings isn't on the UPS right (oops).

Since then, one drive is showing up with the RED - NOT PRESENT icon in unraid.

 

I've checked the housing, it is blinking in the right way to show it is present.  Looking through the logs it appears to be there (/mnt/disk6 is being reported as mounting correctly).

 

How can I better troubleshoot this to see if it is a bug or a true issue.  There doesn't seem to be any SMART monitor in the defautl v6 beta 4 release.

 

Edit: 

this is all I could find in the syslog

Apr  6 18:14:27 Tower emhttp: shcmd (141): umount /mnt/disk6 |& logger

Apr  6 18:14:27 Tower logger: umount: /mnt/disk6: device is busy.

Apr  6 18:14:27 Tower logger:        (In some cases useful info about processes that use

Apr  6 18:14:27 Tower logger:          the device is found by lsof( or fuser(1))

 

if I lsof the /mnt/disk6 it shows it's correct:

 

root@Tower:/var/log# lsof /mnt/disk6

COMMAND  PID USER  FD  TYPE DEVICE  SIZE/OFF NODE NAME

shfs    3532 root    4r  REG    9,6 157573295 5143 /mnt/disk6/Television/Dora the Explorer/Season 04/Dora the Explorer - 4x04 - The Shy Rainbow.mkv

 

 

[jphipps]

I believe that is the correct result.  When unraid gets a write failure on a drive, it would show up as red and then not be physically part of the array anymore, just emulated via the parity disk.  I think there is a way to force the parity correct, but you have to be 100% sure the parity is valid, or you have to rebuild the disk either on the same drive or a new drive to get the array back in a protected state.  The safest is to rebuild on a new drive.  If you rebuild on the existing drive and something happens, you would have lost the good physical copy as well as the emulated copy.

 

http://lime-technology.com/wiki/index.php/FAQ#How_do_hard_drives_become_disabled.3F

[devanchya]

thanks, I was looking for reasons why it died.

Since the housing was offline for half a day most likely an automated process fired and caused the issue

[bkastner]

I seem to have a bit of an issue since moving to 6.0. The new GUI seems to hang in IE sometimes. If I try and refresh the page it will just try continuously without completing. I need to stop the refresh and then refresh again and it's usually fine.

 

I first noticed it on beta3, but it seems to persist through beta4.

 

I've checked the logs and there are no entries at all, so am not sure what to think.

 

For what it's worth I am using IE11 on Windows 8.1.

 

Has anyone else experienced anything similar?