Here is the link for "unRAID OS 5.0-rc2-test".  If you have been following along in this thread, and you have an LSI controller, or you have a Realtek NIC, please give it a try and let me know what issues you find.  I'm expecting everything to be great. 

 

I really appreciate this!

 

Did some preliminary tests on my 6 drive array using the built-in server LSI controller and so far everything is working fine.

 

I was able to:

• start the array
  
• stop the array
  
• access the array
  
• spin-down the drives
  
• access a spun-down drive or three and they spun-up correctly without false read-errors and causing red-balls
  
• spin-down drives while some were being accessed and only the un-accessed drives were spun-down
  

Sorry to have to report a bug, but since upgrading to rc2 about an hour ago, from beta8, i am getting this message pop up every time i try to access an AFP share 

 

Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

 

The share works ok for the first 20 seconds, but after that OSX gives me the above alert and then i cannot navigate any further around the share :-(

 

I also have the GUI lock up problem, mainly after a full system boot just after clicking to start the array, however mine never comes back, no matter how long i wait :-(

 

 

Any ideas Tom?

 

Rich

Sorry to have to report a bug, but since upgrading to rc2 about an hour ago, from beta8, i am getting this message pop up every time i try to access an AFP share 

 

Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

 

The share works ok for the first 20 seconds, but after that OSX gives me the above alert and then i cannot navigate any further around the share :-(

 

I also have the GUI lock up problem, mainly after a full system boot just after clicking to start the array, however mine never comes back, no matter how long i wait :-(

 

 

Any ideas Tom?

 

Rich

 

With your lockup, could you connect to the server via telnet?

No i couldn't and the shares didn't mount either.

Sounds like the same lockup issue I'm having, but when I'm stopping the array. It's odd...  I cannot get access to shell either, server actually locks up. That also means no log file.

Try telneting in prior to testing the crash issue and have a tail -f running on it. Any errors that show up in the log just prior to crashing should display.

Sounds like the same lockup issue I'm having, but when I'm stopping the array. It's odd...  I cannot get access to shell either, server actually locks up. That also means no log file.

 

Are you using AFP?

Sounds like the same lockup issue I'm having, but when I'm stopping the array. It's odd...  I cannot get access to shell either, server actually locks up. That also means no log file.

 

Are you using AFP?

 

Correct

 

Try telneting in prior to testing the crash issue and have a tail -f running on it. Any errors that show up in the log just prior to crashing should display.

 

That's the plan once I get out of work

Sorry to have to report a bug, but since upgrading to rc2 about an hour ago, from beta8, i am getting this message pop up every time i try to access an AFP share 

 

Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

 

The share works ok for the first 20 seconds, but after that OSX gives me the above alert and then i cannot navigate any further around the share :-(

 

Any ideas about this Tom??

Sorry to have to report a bug, but since upgrading to rc2 about an hour ago, from beta8, i am getting this message pop up every time i try to access an AFP share 

 

Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

 

The share works ok for the first 20 seconds, but after that OSX gives me the above alert and then i cannot navigate any further around the share :-(

 

Any ideas about this Tom??

 

Yes, something wrong with AFP.

Sorry to have to report a bug, but since upgrading to rc2 about an hour ago, from beta8, i am getting this message pop up every time i try to access an AFP share 

 

Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

 

The share works ok for the first 20 seconds, but after that OSX gives me the above alert and then i cannot navigate any further around the share :-(

 

Any ideas about this Tom??

 

Yes, something wrong with AFP.

 

Lol, thanks for that!

I was thinking more, is there something obvious that i am missing and can look at / change.... So glad i asked! 

Here are the log entries that might be causing issues. Tail -f didn't show anything out of the ordinary. I used the powerdown script instead, seems like an AFP issue. I'm moving back to beta 14 for now

 

Here are the log entries - emhttp isn't saying much:

 

May  3 12:43:25 Storage afpd[7229]: dsi_stream_read: len:0, unexpected EOF
May  3 12:43:31 Storage afpd[7232]: volume "Backup" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "Documentaries" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "HD Movies" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "Movies" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "Music" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "Sports" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "Storage" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: volume "TV" does not support Extended Attributes, using ea:ad instead
May  3 12:43:31 Storage afpd[7232]: dsi_stream_read: len:0, unexpected EOF
May  3 12:44:02 Storage afpd[7235]: volume "Backup" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "Documentaries" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "HD Movies" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "Movies" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "Music" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "Sports" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "Storage" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: volume "TV" does not support Extended Attributes, using ea:ad instead
May  3 12:44:02 Storage afpd[7235]: dsi_stream_read: len:0, unexpected EOF

 

May  3 12:45:24 Storage emhttp: shcmd (272): rmmod md-mod |& logger
May  3 12:45:24 Storage emhttp: shcmd (273): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger
May  3 12:45:24 Storage emhttp: shcmd (274): udevadm settle
May  3 12:45:24 Storage emhttp: Device inventory:
May  3 12:45:24 Storage emhttp: WDC_WD20EARX-00PASB0_WD-WCAZA7721691 (sdb) 1953514584
May  3 12:45:24 Storage emhttp: WDC_WD20EARX-00PASB0_WD-WCAZAC269465 (sdc) 1953514584
May  3 12:45:24 Storage emhttp: ST31000340AS_9QJ0PVWK (sdg) 976762584
May  3 12:45:24 Storage emhttp: ST31000333AS_9TE1KPE1 (sdf) 976762584
May  3 12:45:24 Storage emhttp: WDC_WD15EARS-00Z5B1_WD-WMAVU1908482 (sde) 1465138584
May  3 12:45:24 Storage emhttp: Hitachi_HTS545032B9SA02_100818PBSC00EYJK825S (sdh) 312571224
May  3 12:45:24 Storage emhttp: ST31500341AS_9VS0B8ER (sdd) 1465138584
May  3 12:45:24 Storage kernel: md: unRAID driver removed
May  3 12:45:24 Storage kernel: md: unRAID driver 2.1.3 installed
May  3 12:45:24 Storage kernel: mdcmd (1): import 0 8,16 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZA7721691
May  3 12:45:24 Storage kernel: md: import disk0: [8,16] (sdb) WDC_WD20EARX-00PASB0_WD-WCAZA7721691 size: 1953514552
May  3 12:45:24 Storage kernel: mdcmd (2): import 1 8,96 976762552 ST31000340AS_9QJ0PVWK
May  3 12:45:24 Storage kernel: md: import disk1: [8,96] (sdg) ST31000340AS_9QJ0PVWK size: 976762552
May  3 12:45:24 Storage kernel: mdcmd (3): import 2 8,80 976762552 ST31000333AS_9TE1KPE1
May  3 12:45:24 Storage kernel: md: import disk2: [8,80] (sdf) ST31000333AS_9TE1KPE1 size: 976762552
May  3 12:45:24 Storage kernel: mdcmd (4): import 3 8,64 1465138552 WDC_WD15EARS-00Z5B1_WD-WMAVU1908482
May  3 12:45:24 Storage kernel: md: import disk3: [8,64] (sde) WDC_WD15EARS-00Z5B1_WD-WMAVU1908482 size: 1465138552
May  3 12:45:24 Storage kernel: mdcmd (5): import 4 8,48 1465138552 ST31500341AS_9VS0B8ER
May  3 12:45:24 Storage emhttp: shcmd (275): /usr/local/sbin/emhttp_event driver_loaded
May  3 12:45:24 Storage emhttp_event: driver_loaded
May  3 12:45:24 Storage kernel: md: import disk4: [8,48] (sdd) ST31500341AS_9VS0B8ER size: 1465138552
May  3 12:45:24 Storage kernel: mdcmd (6): import 5 8,32 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAC269465
May  3 12:45:24 Storage kernel: md: import disk5: [8,32] (sdc) WDC_WD20EARX-00PASB0_WD-WCAZAC269465 size: 1953514552
May  3 12:45:24 Storage kernel: mdcmd (7): import 6 0,0
May  3 12:45:24 Storage kernel: mdcmd (: import 7 0,0
May  3 12:45:24 Storage kernel: mdcmd (9): import 8 0,0
May  3 12:45:24 Storage kernel: mdcmd (10): import 9 0,0
May  3 12:45:24 Storage kernel: mdcmd (11): import 10 0,0
May  3 12:45:24 Storage kernel: mdcmd (12): import 11 0,0
May  3 12:45:24 Storage kernel: mdcmd (13): import 12 0,0
May  3 12:45:24 Storage kernel: mdcmd (14): import 13 0,0
May  3 12:45:24 Storage kernel: mdcmd (15): import 14 0,0
May  3 12:45:24 Storage kernel: mdcmd (16): import 15 0,0
May  3 12:45:24 Storage kernel: mdcmd (17): import 16 0,0
May  3 12:45:24 Storage kernel: mdcmd (18): import 17 0,0
May  3 12:45:24 Storage kernel: mdcmd (19): import 18 0,0
May  3 12:45:24 Storage kernel: mdcmd (20): import 19 0,0
May  3 12:45:24 Storage kernel: mdcmd (21): import 20 0,0
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/Backup No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/Backup No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/Documentaries No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/Documentaries No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/HD Movies No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/HD Movies No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/Movies No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/Movies No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/Music No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/Music No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/Sports No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/Sports No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/Storage No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/Storage No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: statfs: /mnt/user/TV No such file or directory
May  3 12:45:25 Storage emhttp: get_filesystem_status: opendir: /mnt/user/TV No such file or directory
May  3 12:45:26 Storage afpd[7780]: volume "Backup" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "Documentaries" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "HD Movies" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "Movies" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "Music" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "Sports" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "Storage" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: volume "TV" does not support Extended Attributes, using ea:ad instead
May  3 12:45:26 Storage afpd[7780]: dsi_stream_read: len:0, unexpected EOF

I'm using a system with a SASLP-MV8, with beta14 I'm getting speeds of about 60MB/sec average for paritycheck, however, with the rc2-test version, I'm only getting speeds of up to 20MB/sec for paritycheck, in the same situation.

Reading and writing didn't test the speed, but in normal usage appear the same in both, so not slow like that.

 

Where is you parity drive? Not to assume that you have all your drives on the card.

Sorry to have to report a bug, but since upgrading to rc2 about an hour ago, from beta8, i am getting this message pop up every time i try to access an AFP share 

 

Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

 

The share works ok for the first 20 seconds, but after that OSX gives me the above alert and then i cannot navigate any further around the share :-(

 

Any ideas about this Tom??

 

Yes, something wrong with AFP.

 

Lol, thanks for that!

I was thinking more, is there something obvious that i am missing and can look at / change.... So glad i asked! 

 

What version of OSX?

I'm still experiencing this problem with rc2.

 

It stopped at around 158MB, and it seems impossible to get the nautilus process to die on my ubuntu desktop - I have to reboot it.

 

Reverting to b11

for anyone with realtek NIC issues should consider buying an intel NIC, much much much better support under linux and not an expensive hardware change at all. save you a lot of headaches.

30+ 5 shipping

http://www.newegg.ca/Product/Product.aspx?Item=N82E16833106121CVF

 

Just my 2c

 

Keep up the great work tom, unraid is really starting to come together into an AMAZING product, Bravo

 

For those having issues with AFP & the CNID DB I was able to correct these following the instructions here: http://lime-technology.com/forum/index.php?topic=15657.0

Here as requested our my transfer speeds with Asus M4A785TD-V EVO  mobo using on-board RTL8112L Gigabit LAN controller.

 

 

---UNRAID RC1---

driver: r8169

version: 2.3LK-NAPI

firmware-version:

bus-info: 0000:02:00.0

Array Write (protected) - ~28 MB/s

Array Read -                    ~90 MB/s

Parity (correct) -  Peak 85 MB/s  Avg 65MB/s    after full parity check

---UNRAID RC2 TEST---

driver: r8169

version: 2.3LK-NAPI

firmware-version: N/A

bus-info: 0000:02:00.0

Array Write (protected) - ~23 MB/s

Array Read -                    ~90 MB/s

Parity (correct) -  Peak 85 MB/s  Avg 65MB/s    after full parity check

 

 

Seems problem free ill keep on testing it,

Thanks again

 

rc2 -test working fine on my old board with br10

 

didn't see 24 drives yet though

 

 

Perhaps the next beta can be a kernel module release only.

 

Probably nobody cares, but I would support this approach.

I'm not sure if Limetech is sticking to the definitions of beta and release candidates. When in beta, you can add/remove/change functionality in software, that's what beta's are for. But once RC-status has been reached, you should only fix bugs, and leave new and/or updated functionality to a new release.

 

I really think it's better if 5.0 would go final, and push all other things to 5.1+. It's been a long time coming....

I really think it's better if 5.0 would go final, and push all other things to 5.1+. It's been a long time coming....

 

Indeed ... I think that it's more important to get nfs working properly again!  It was broken in beta12 and has never worked since..

I really think it's better if 5.0 would go final, and push all other things to 5.1+. It's been a long time coming....

 

Indeed ... I think that it's more important to get nfs working properly again!  It was broken in beta12 and has never worked since..

+1

I really think it's better if 5.0 would go final, and push all other things to 5.1+. It's been a long time coming....

 

Indeed ... I think that it's more important to get nfs working properly again!  It was broken in beta12 and has never worked since..

 

 

I think this answers my previous question about NFS, but not explicitly. Does anyone have experience with RC2 and NFS and is the stale file handle problem still present in RC2?

 

Thanks.

Tom, just wondering if you have any thoughts of when RC3 and/or 5 Final is going to be available.

 

Reason  I ask is I have recently purchased M1015 flashed with LSI firmware in IT mode in transit to me as I type this.  Just wondering if I should go ahead and upgrade to RC2 (from beta 13) when it arrives or if it's close to being ready just hold off until RC3 or Final is available?

 

 

 

unRaid Server 5.0-beta13

Intel E8400 3.0 GHz

Biostar TP45 HP Ver 5.x (http://www.biostar-usa.com/app/en-us/mb/introduction.php?S_ID=366&tab=3)

4 GB G.Skill PC2 8500