unRAID Server Release 5.0-beta11 Available


Recommended Posts

  • Replies 178
  • Created
  • Last Reply

Top Posters In This Topic

After making a clean upgrade from b6 (freshly formatted USB and no installed add-ons), I wanted to stop my array to remove an unused drive. Got a kernel oops for trying that :-( Currently not running parity (reason for removing drive was to insert future parity drive). Anyone want other relevant info, just ask.  Btw; the array didn't stop...

 

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: Oops: 0000 [#1] SMP 

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host10/target10:0:0/10:0:0:0/block/sdh/stat

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: Process umount (pid: 4290, ti=f1bbc000 task=f11a9a80 task.ti=f1bbc000)

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: Stack:

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: Call Trace:

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: Code: d6 53 89 c3 f0 0f ba 29 00 19 d2 31 c0 85 d2 0f 85 9d 00 00 00 83 79 10 00 74 04 0f 0b eb fe 8d 41 04 39 41 04 74 04 0f 0b eb fe <f6> 06 02 b8 08 00 00 00 75 19 89 c8 e8 a9 e6 ff ff 85 c0 74 08 

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: EIP: [<c103819d>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f1bbde38

Message from syslogd@Tower at Tue Aug 16 12:05:31 2011 ...
Tower kernel: CR2: 0000000000000000

 

Syslog attached

 

Update: Seems the shares stopped (no dirs in /mnt) and it's the GUI that hangs. Still in that state if someone wants investigation done.

syslog_b11_110816.txt.zip

Link to comment

Ok, I'm having serious issues now since sleeping the array last night.

 

Was working fine now nothing can access UnRAID or UnMenu through browsers, my iPhone can't connect to the iStat server and I can't mount the flash drive.

 

Telnet in and doing a command other than shutdown -r now results in the window hanging.

 

Edit: Removing the USB drive and putting my go script back to normal has resulted in life!

 

*Finds what the matters was*

Link to comment

Can I suggest using a GitHub repository to host the packages, so that people can easily modify/create/share their own, which can then easily be folded into the official repository? Also downloading and updating of the repository and installation of packages should happen entirely via the web interface :)

While that sounds good, I would not want someone modifying the packages I create and then uploading them with under the same name.  I want to be in control of all packages I create, and while they will be freely available for others to use and modify I would not want them able to update my packages directly.

 

One problem with unMENU that I'd like to see improved with unRAID's official package system is that many of the packages are still relying on older slackware packages (not the 13.1 that unRAID is built on). Will the official system allow the package repository to handle different versions of unRAID (obviously 5.0beta11 plus, not legacy versions)?

 

Cheers.

The package manager in unRAID will obviously ONLY support 5.0 so when package get updated and moved to the unRAID package manager the "versions" that are used may very well be updated also.  I honestly don't see the point in trying to keep up with it though.  If a package works and uses a file from 12.X Slackware where is the harm?

Link to comment

Can I suggest using a GitHub repository to host the packages, so that people can easily modify/create/share their own, which can then easily be folded into the official repository? Also downloading and updating of the repository and installation of packages should happen entirely via the web interface :)

While that sounds good, I would not want someone modifying the packages I create and then uploading them with under the same name.  I want to be in control of all packages I create, and while they will be freely available for others to use and modify I would not want them able to update my packages directly.

 

On github, no one can modify your files unless you give them the permission. What they can do however is to "clone" the project and make their modifications. You can then "merge" their modifications in to yours if you like.

Link to comment

Looks like this release does not include the "-SMB" for for Lion users

 

Look a few posts up... is that the cause?

http://lime-technology.com/forum/index.php?topic=14664.msg138245#msg138245

 

 

Nobe. Please read this by nezil: http://lime-technology.com/forum/index.php?topic=14623.msg138068#msg138068. You need to change the port number from 139 to 445 in 2 files (smb.service and smb.conf) after which one can use the sidebar in Lion: "yourserver" >> AFP; "yourserver-SMB" >> SAMBA.

Link to comment

Looks like this release does not include the "-SMB" for for Lion users

 

Look a few posts up... is that the cause?

http://lime-technology.com/forum/index.php?topic=14664.msg138245#msg138245

 

 

Nobe. Please read this by nezil: http://lime-technology.com/forum/index.php?topic=14623.msg138068#msg138068. You need to change the port number from 139 to 445 in 2 files (smb.service and smb.conf) after which one can use the sidebar in Lion: "yourserver" >> AFP; "yourserver-SMB" >> SAMBA.

 

Ah, ok, I posted a reply there:

http://lime-technology.com/forum/index.php?topic=14623.msg138383#msg138383

 

Briefly, I'll turn 445 back on and see if syslog gets flooded again.

Link to comment

Tom, having issues with the network driver crashing...

 

Aug 16 21:15:57 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:16:35 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:17:35 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:19:35 Tower last message repeated 2 times
Aug 16 21:20:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:21:35 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:21:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:22:10 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:22:27 Tower last message repeated 2 times
Aug 16 21:22:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:22:39 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:23:37 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:23:41 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)

 

Realtek® 8112L card.

 

I'll go back to b10 to see if that fixes it...

 

Edit: Confirmed. My GbE works perfectly now with b10.

 

I feel b11 is a lemon, had quite a few issues with it :(

Link to comment

Very limited success ratio mounting bluray isos through user shares over network (smb) to windows boxes using slysoft virtual clone drive 5450.  

 

If successful disk will mount normally.  If unsuccessful vcd will display "can't mount p:\03  video\1  movies BLURAY\movietitle.iso!" where 'p' is mapped user share.  Same iso can mount today, not mount 10min from now and vice versa.  Navigating again to same iso but instead of user shares direct to diskxx is successful.  Copying isos to local hard drive then mounting is successful.

 

First noticed in 5.0beta10 before that running 4.7 final without issue

 

- navigating to same problem isos directly through network \\NORCO\disk8\ALL\03  video\1  movies BLURAY\movietitle.iso = 100% successful

- mapping above (\\NORCO\disk8\ALL\03  video\1  movies BLURAY\movietitle.iso) = 100% successful

- navigating to problem isos in network user share produces error "can't mount \\norco\all\03  video\1  movies BLURAY\movietitle.iso!"

- rerun 'new permissions' in unraid setting = no change

- regressed to vcd 5443, 5440 = no change

- accessing through another windows box = no change

- regressed unraid to 5.0beta9 = 100% successful

- updated to 5.0beta11 = no change

 

This is really worrying.

 

I am building a new media server with 3TB drives, so will need v5 of UnRaid. A lot of my content will be bluray ISOs.

My current 4.7 UnRaid server mounts bluray isos from user shares with virtual clonedrive and works great.

 

Is anyone else having issues mounting bluray isos from user shares on 5.0beta11? Should I just stick to 5.0beta9?

 

Link to comment

Tom, having issues with the network driver crashing...

 

Aug 16 21:15:57 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:16:35 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:17:35 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:19:35 Tower last message repeated 2 times
Aug 16 21:20:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:21:35 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:21:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:22:10 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:22:27 Tower last message repeated 2 times
Aug 16 21:22:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:22:39 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:23:37 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:23:41 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)

 

Are you sure it isn't a disk/controller/driver error instigating the problems? Those "Hard Drives active, resetting counter" lines don't look good. Syslog?

Link to comment

Tom, having issues with the network driver crashing...

 

Aug 16 21:15:57 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:16:35 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:17:35 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:19:35 Tower last message repeated 2 times
Aug 16 21:20:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:21:35 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:21:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:22:10 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:22:27 Tower last message repeated 2 times
Aug 16 21:22:36 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:22:39 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Aug 16 21:23:37 Tower logger: Tue Aug 16 14:37:13 BST 2011 - Hard Drives active, resetting counter
Aug 16 21:23:41 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)

 

Are you sure it isn't a disk/controller/driver error instigating the problems? Those "Hard Drives active, resetting counter" lines don't look good. Syslog?

 

That, from what I can tell, is to do with the sleep spin-down timer.

 

Besides, I've been running b10 since and it's fine.

Link to comment
Besides, I've been running b10 since and it's fine.

 

Yep, and the significant difference between b10 and b11 is the Realtek driver.  I suspect that different drivers are patched to circumvent the various shortcomings in the different generations of Realtek hardware.  I've already made my views on Realtek quite clear in earlier posts!

Link to comment

Hi from OZ

 

Just set up UNRAID server (Basic). Have an additional disk (outside of the array) using NTFS. NTFS Slackware package installed along with simple features GUI. Otherwise stock standard. Have used beta 10 and OK.

 

Problems is with powerdown command issues an oops as follows:

 

Aug 17 14:11:45 Tower kernel:BUG: unable to handle kernel NULL pointer dereference at 00000040

Aug 17 14:11:45 Tower kernel: IP: [<c131ffdf>] _raw_spin_lock_irq+0x9/0x1a

Aug 17 14:11:45 Tower kernel: *pdpt = 000000002fff5001 *pde = 0000000000000000

Aug 17 14:11:45 Tower kernel: Oops: 0002 [#1] SMP

 

If I use a halt command is OK.

 

FYI. I have attached the full system log.

 

Regards

 

Ramjet303

syslog.txt

Link to comment

Yeah, in Lion, both are available to me, the normal "Tower" (AFP) and the "Tower-SMB"

 

Does it work as expected?  That is if you access via "Tower" Lion is using AFP, and if you access via "Tower-SMB" Lion is using SMB?

 

no, my mistake. It will not allow me to connect. AFP works fine though, which for the moment, is all that matters.

Link to comment

Can I suggest using a GitHub repository to host the packages, so that people can easily modify/create/share their own, which can then easily be folded into the official repository? Also downloading and updating of the repository and installation of packages should happen entirely via the web interface :)

While that sounds good, I would not want someone modifying the packages I create and then uploading them with under the same name.  I want to be in control of all packages I create, and while they will be freely available for others to use and modify I would not want them able to update my packages directly.

 

This is not how GitHub works. Other people cannot modify your scripts, as they exist in the "official" repository. But they can fork the official repository, make any changes they like, which other people can use if they like. If a change is tested and good, a pull request can be sent to the maintainer of the official repository and that person can decide if they want to merge it in or not.

 

Git (and GitHub) just makes it a lot easier for people to fork the repository, make their own changes, and share changes with each other (again, without modifying the official repository). This allows you to be entirely in control of the packages that you install, from the officlal repository, a fork, or maintain your own local modifications without having them be overwritten when an official update is released.

 

Link to comment

From Beta10:

 

- linux: use Realtek r8168 driver instead of linux r8169 driver

 

From Beta11:

 

- linux: restore linux r8169 driver

 

I'm guessing the Realtek 8111E is still causing problems?  Too bad if that's the case, since the majority of cheap socket 1155 motherboards use that NIC.

Link to comment

From Beta10:

 

- linux: use Realtek r8168 driver instead of linux r8169 driver

 

From Beta11:

 

- linux: restore linux r8169 driver

 

I'm guessing the Realtek 8111E is still causing problems?  Too bad if that's the case, since the majority of cheap socket 1155 motherboards use that NIC.

 

Just noticed that, so yes that is what is causing the issue.

 

A number of the AMD m-ATX boards also use that...

 

Any reason for putting it back in the first place!?

Link to comment

Since upgrading to beta11 from beta10 I now get this error when trying to connect to Tower over AFP:

 

Aug 17 10:05:50 Tower cnid_dbd[29285]: Error opening lockfile: Permission denied
Aug 17 10:05:50 Tower cnid_dbd[29285]: main: fatal db lock error
Aug 17 10:05:50 Tower afpd[29274]: read: Connection reset by peer
Aug 17 10:05:51 Tower cnid_dbd[29286]: Set syslog logging to level: LOG_NOTE
Aug 17 10:05:51 Tower cnid_dbd[29286]: Error opening lockfile: Permission denied
Aug 17 10:05:51 Tower cnid_dbd[29286]: main: fatal db lock error
Aug 17 10:05:51 Tower afpd[29274]: read: Connection reset by peer
Aug 17 10:06:11 Tower last message repeated 20 times
Aug 17 10:06:11 Tower afpd[29274]: transmit: Request to dbd daemon (db_dir /mnt/user/music) timed out.
Aug 17 10:06:11 Tower afpd[29274]: Reopen volume /mnt/user/music using in memory temporary CNID DB.

 

Any help would be appreciated.

Link to comment

Having issues stopping array.. Has done it twice in a row since installing latest beta. emhttp reporting bug, /mnt/user is showing as busy and won't unmount. Have to force shut down...

 

Anyone else having issues with this? Upgraded to -beta11 on a small test server last night and had this happen twice. At first I was convinced that I had left a telnet session open somewhere, but I'm fairly certain that was not the case. Had to force shutdown both times.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.