Boxee

regression: SMB shares from ReadyNAS duo are disconnected

Details

  • Severity:
    Major
  • Version:
    1.1.1.19092
  • Operating System:
    Boxee Box
  • Number of attachments:
    2

Description

After the update (1.0.3.17064) the Boxee Box refuses to play anything from my SMB shares. Sometimes saying they're disconnected, sometimes saying the media source or file is not accessible. I am really annoyed now.

I removed all the shares and tried to re-add them. Which makes Boxee Box say: 'Error. Operation not permitted'

Sitting on a 230€ box that does nothing thanks to this "update".

Issue Links

Activity

Hide
Rutger Middendorp added a comment - 21/Jan/11 9:33 AM
I unplugged the box, waited for a few minutes and connected it to the router with a cable instead of wireless. That made it work again. Then retried through wireless. Still doesn't work. Since I don't want to run a cable through my living room I still need a fix. Besides: I can't just switch to make it work again. I need to shut down, unplug for 30 seconds, plug in again and reboot. Then it does work again.
Show
Rutger Middendorp added a comment - 21/Jan/11 9:33 AM I unplugged the box, waited for a few minutes and connected it to the router with a cable instead of wireless. That made it work again. Then retried through wireless. Still doesn't work. Since I don't want to run a cable through my living room I still need a fix. Besides: I can't just switch to make it work again. I need to shut down, unplug for 30 seconds, plug in again and reboot. Then it does work again.
Hide
Rutger Middendorp added a comment - 21/Jan/11 10:06 AM
Correction: It did work, now I'm back to square one as my SMB shares disconnect on the wired connection as well and I get the same error 'Operation not permitted'. WAAAAA!
Show
Rutger Middendorp added a comment - 21/Jan/11 10:06 AM Correction: It did work, now I'm back to square one as my SMB shares disconnect on the wired connection as well and I get the same error 'Operation not permitted'. WAAAAA!
Hide
Ami Ben-David [Boxee] added a comment - 23/Jan/11 3:36 AM
Please attach a Debug log to this issue.
Settings > System > Debug > Debug Level = Debug
ReStart Boxee, and after experiencing the problem, close Boxee and attach your log file to the bug.
DEBUG log slows down the performance. so afterward, switch the log level back to NONE
Boxee Box log may be found at http://boxeebox:8080/ click on the "Get latest " link.
more information at
http://support.boxee.tv/entries/43963-i-ve-been-asked-by-boxee-support-to-send-debug-logs-how-do-i-do-that
http://support.boxee.tv/entries/329278-i-ve-been-asked-by-boxee-support-to-send-debug-logs-how-do-i-do-that
Show
Ami Ben-David [Boxee] added a comment - 23/Jan/11 3:36 AM Please attach a Debug log to this issue. Settings > System > Debug > Debug Level = Debug ReStart Boxee, and after experiencing the problem, close Boxee and attach your log file to the bug. DEBUG log slows down the performance. so afterward, switch the log level back to NONE Boxee Box log may be found at http://boxeebox:8080/ click on the "Get latest " link. more information at http://support.boxee.tv/entries/43963-i-ve-been-asked-by-boxee-support-to-send-debug-logs-how-do-i-do-that http://support.boxee.tv/entries/329278-i-ve-been-asked-by-boxee-support-to-send-debug-logs-how-do-i-do-that
Hide
Rutger Middendorp added a comment - 25/Jan/11 5:12 PM
OK, I have done as you asked. First I tried to add the SMB server in settings (Error. Operation not permitted). Then I went to files and tried to reach the smb server from there (Loading error. Could not access file, directory or device).

I sent the log to you guys as described above. I'm trying to see how I can add it to this ticket.
Show
Rutger Middendorp added a comment - 25/Jan/11 5:12 PM OK, I have done as you asked. First I tried to add the SMB server in settings (Error. Operation not permitted). Then I went to files and tried to reach the smb server from there (Loading error. Could not access file, directory or device). I sent the log to you guys as described above. I'm trying to see how I can add it to this ticket.
Hide
Ami Ben-David [Boxee] added a comment - 26/Jan/11 3:48 AM
thank you for the log file,
are the SMB shares password protected?
Show
Ami Ben-David [Boxee] added a comment - 26/Jan/11 3:48 AM thank you for the log file, are the SMB shares password protected?
Hide
Rutger Middendorp added a comment - 26/Jan/11 4:39 AM - edited
Yes they are password protected. Passwords haven't changed though and it has always worked with the passwords before.
Show
Rutger Middendorp added a comment - 26/Jan/11 4:39 AM - edited Yes they are password protected. Passwords haven't changed though and it has always worked with the passwords before.
Hide
Rutger Middendorp added a comment - 28/Jan/11 7:01 AM
Any news? I do not know what Fiona Unscheduled means, but I guess it doesn't have top priority?
Show
Rutger Middendorp added a comment - 28/Jan/11 7:01 AM Any news? I do not know what Fiona Unscheduled means, but I guess it doesn't have top priority?
Hide
haveringcottage added a comment - 28/Jan/11 10:56 AM
Fiona Unscheduled means that it is not planned to be incorporated into SP4, or SP5.

It is currently not even assigned to a staffer, which means no-one is actively looking after this ticket on the jira.

The jira is not the be all and end all though. this may be being worked on as part of a non-jira posted fix.
Show
haveringcottage added a comment - 28/Jan/11 10:56 AM Fiona Unscheduled means that it is not planned to be incorporated into SP4, or SP5. It is currently not even assigned to a staffer, which means no-one is actively looking after this ticket on the jira. The jira is not the be all and end all though. this may be being worked on as part of a non-jira posted fix.
Hide
mikael ström added a comment - 12/Feb/11 7:01 PM
i had the same problem with shares being disconnected and getting error not permitted messages, but i found a workaround:
http://forums.boxee.tv/showthread.php?t=29335

Hopefully it will work for you aswell.
Show
mikael ström added a comment - 12/Feb/11 7:01 PM i had the same problem with shares being disconnected and getting error not permitted messages, but i found a workaround: http://forums.boxee.tv/showthread.php?t=29335 Hopefully it will work for you aswell.
Hide
Rutger Middendorp added a comment - 13/Feb/11 5:58 AM
I just posted this, to say I love you! (Imagine Lionel Richie singing it!)
It works, it works, it works, I have my Boxee experience back.
Well good people at Boxee, it seems as if it won't be too hard to fix this problem now, does it?
Show
Rutger Middendorp added a comment - 13/Feb/11 5:58 AM I just posted this, to say I love you! (Imagine Lionel Richie singing it!) It works, it works, it works, I have my Boxee experience back. Well good people at Boxee, it seems as if it won't be too hard to fix this problem now, does it?
Hide
Rutger Middendorp added a comment - 17/Feb/11 4:14 PM
Changing the name of the readynas to something else and back fixes it. But I need to do it every day. That's annoying. Please help, Boxee.
Show
Rutger Middendorp added a comment - 17/Feb/11 4:14 PM Changing the name of the readynas to something else and back fixes it. But I need to do it every day. That's annoying. Please help, Boxee.
Hide
Craig Clark added a comment - 24/Feb/11 7:48 PM
I've got the same issue with a Netgear ReadyNAS NVX Pioneer Edition with the latest firmware. Problem is that 5 other computers access this NAS device and changing the device name on a daily basis is not a solution. Problem first noticed after the Boxee Box was updated to firmware 1.0.4.17443.
Show
Craig Clark added a comment - 24/Feb/11 7:48 PM I've got the same issue with a Netgear ReadyNAS NVX Pioneer Edition with the latest firmware. Problem is that 5 other computers access this NAS device and changing the device name on a daily basis is not a solution. Problem first noticed after the Boxee Box was updated to firmware 1.0.4.17443.
Hide
Craig Clark added a comment - 26/Feb/11 9:10 AM
I thought I had a solution, but it proved short lived. I enabled the WINS server functionality on my ReadyNAS and instantly my shares were accessible again from the Boxee Box. I don't need WINS for anything, so I've always had it disabled. I was able to access the shares for several hours, and thought I would test by rebooting the Netgear NAS device. After rebooting my shares were no longer accessible, even after restarting the Boxee Box several times.
Show
Craig Clark added a comment - 26/Feb/11 9:10 AM I thought I had a solution, but it proved short lived. I enabled the WINS server functionality on my ReadyNAS and instantly my shares were accessible again from the Boxee Box. I don't need WINS for anything, so I've always had it disabled. I was able to access the shares for several hours, and thought I would test by rebooting the Netgear NAS device. After rebooting my shares were no longer accessible, even after restarting the Boxee Box several times.
Hide
Craig Clark added a comment - 06/Mar/11 8:59 PM
Sometimes the SMB shares just randomly work, doesn't seem to be any rhyme or reason to it. But 98% of the time they do not work.
Show
Craig Clark added a comment - 06/Mar/11 8:59 PM Sometimes the SMB shares just randomly work, doesn't seem to be any rhyme or reason to it. But 98% of the time they do not work.
Hide
Rafael Mizrahi [Boxee] added a comment - 22/Mar/11 10:10 AM
Craig , looking at your log, the SMB failure is due to permissions.
smbc_stat functions returns error 1 which is EPERM
for example:
<smb://NAS-CL4/media/Pictures/> not available according to smbc_stat (-1, 1)
Show
Rafael Mizrahi [Boxee] added a comment - 22/Mar/11 10:10 AM Craig , looking at your log, the SMB failure is due to permissions. smbc_stat functions returns error 1 which is EPERM for example: <smb://NAS-CL4/media/Pictures/> not available according to smbc_stat (-1, 1)
Hide
Rafael Mizrahi [Boxee] added a comment - 22/Mar/11 10:15 AM
Rutger Middendorp , if you experience problems with names resolving of your NAS host name, how about trying to add the source to the ReadyNAS using IP
Show
Rafael Mizrahi [Boxee] added a comment - 22/Mar/11 10:15 AM Rutger Middendorp , if you experience problems with names resolving of your NAS host name, how about trying to add the source to the ReadyNAS using IP
Hide
Rutger Middendorp added a comment - 22/Mar/11 1:11 PM
Hi Rafael: I did. It's called blackbox and that's how I add it. Also tried IP. Makes no difference.
Show
Rutger Middendorp added a comment - 22/Mar/11 1:11 PM Hi Rafael: I did. It's called blackbox and that's how I add it. Also tried IP. Makes no difference.
Hide
Craig Clark added a comment - 30/Mar/11 4:06 PM
Rafael, I understand what you are saying but if it were permissions I would expect it to show some consistency, i.e. never work. But it works maybe 2% of the time and the other 98% of the time it fails. Permissions on the shares are static and are not changing. The other 5 computers that access the ReadyNAS NVX on a daily basis (same shares) never have a permission issue. One of the computers is a Mac Mini running Snow Leopard, 3 of them run flavours of Windows (XP, Vista, Win 7 64bit). The other computer runs Ubuntu Linux. That is a fairly diverse collection of client o/s, but only the Boxee Box has an access issue. I even tried removing all access restrictions on the shares - temporarily - but the Boxee Box still won't connect.
Show
Craig Clark added a comment - 30/Mar/11 4:06 PM Rafael, I understand what you are saying but if it were permissions I would expect it to show some consistency, i.e. never work. But it works maybe 2% of the time and the other 98% of the time it fails. Permissions on the shares are static and are not changing. The other 5 computers that access the ReadyNAS NVX on a daily basis (same shares) never have a permission issue. One of the computers is a Mac Mini running Snow Leopard, 3 of them run flavours of Windows (XP, Vista, Win 7 64bit). The other computer runs Ubuntu Linux. That is a fairly diverse collection of client o/s, but only the Boxee Box has an access issue. I even tried removing all access restrictions on the shares - temporarily - but the Boxee Box still won't connect.
Hide
Craig Clark added a comment - 24/May/11 2:36 PM
I'm now running firmware 1.1.1.19092 but the SMB share problem remains the same. 98% of the time the Boxee Box can "see" my ReadyNAS shares, but can't connect to them. All of my computers (Windows XP, Vista, 7, Mac OS/X, Ubuntu Linux) and my Apple TV can access content on my 8-TB ReadyNAS. I'm getting a little tired of copying local content to SD memory cards just so I can see it on the Boxee Box. If it wasn't for the Netflix support - which is wonderful btw - I would have given up on Boxee and moved on to something else. Very disappointed that a fix has seemingly been put off for now.
Show
Craig Clark added a comment - 24/May/11 2:36 PM I'm now running firmware 1.1.1.19092 but the SMB share problem remains the same. 98% of the time the Boxee Box can "see" my ReadyNAS shares, but can't connect to them. All of my computers (Windows XP, Vista, 7, Mac OS/X, Ubuntu Linux) and my Apple TV can access content on my 8-TB ReadyNAS. I'm getting a little tired of copying local content to SD memory cards just so I can see it on the Boxee Box. If it wasn't for the Netflix support - which is wonderful btw - I would have given up on Boxee and moved on to something else. Very disappointed that a fix has seemingly been put off for now.
Hide
Rafael Mizrahi [Boxee] added a comment - 25/May/11 3:58 AM
I have a tip which might solve the problem for you:
when adding a local network source (SMB or UPNP), DO NOT add the root path of the server machine as the source.
You should navigate into a shared folder inside the server, and add this as a source to boxee.

Bad example: adding smb://192.168.178.20 as a source to boxee
Good example: adding smb://192.168.178.20/public as a source to boxee

Show
Rafael Mizrahi [Boxee] added a comment - 25/May/11 3:58 AM I have a tip which might solve the problem for you: when adding a local network source (SMB or UPNP), DO NOT add the root path of the server machine as the source. You should navigate into a shared folder inside the server, and add this as a source to boxee. Bad example: adding smb://192.168.178.20 as a source to boxee Good example: adding smb://192.168.178.20/public as a source to boxee
Hide
Craig Clark added a comment - 25/May/11 5:43 PM
I've already tried this and it didn't work. The Boxee Box can see the NAS device on the network, but none of the shares show up (usually). Selecting or "clicking" on the device should show available shares, but it just times out with an error. During the 2% of the time when it's working, you can see the device, see the shares and drill down into them any way you want. Or you can add them like in your good example. If you add a share as a source during that 2% of the time it will work fine for a little while - maybe even up to 2 hours - but later it times out when it tries to access it. Other devices and the computers don't care if it's been 2 minutes or 2 weeks - they can access the shares at all times, for any length of time.
Show
Craig Clark added a comment - 25/May/11 5:43 PM I've already tried this and it didn't work. The Boxee Box can see the NAS device on the network, but none of the shares show up (usually). Selecting or "clicking" on the device should show available shares, but it just times out with an error. During the 2% of the time when it's working, you can see the device, see the shares and drill down into them any way you want. Or you can add them like in your good example. If you add a share as a source during that 2% of the time it will work fine for a little while - maybe even up to 2 hours - but later it times out when it tries to access it. Other devices and the computers don't care if it's been 2 minutes or 2 weeks - they can access the shares at all times, for any length of time.
Hide
Craig Clark added a comment - 25/May/11 5:57 PM
During the 2% of the time when it works - like when I change the name of the NAS device - under the Files menu I will see:

Photos
Music
Movies
Shows

Local Folders and network shares
Network
Unidentified Videos

If I click on Network, I will see 4 items:

NAS-CL4/private (Samba)
NAS-CL4/media (Samba)
NAS-CL4 (Samba)
UPnP

Clicking on either of the first two shows me the folders in that share. Clicking on the third item, NAS-CL4, shows me:

media
private

Now, 98% of the time when it is not working, if I click on network I will see 2 items:

NAS-CL4 (Samba)
UPnP

Clicking NAS-CL4 results in a timeout and an error. The share folders do not display.
Show
Craig Clark added a comment - 25/May/11 5:57 PM During the 2% of the time when it works - like when I change the name of the NAS device - under the Files menu I will see: Photos Music Movies Shows Local Folders and network shares Network Unidentified Videos If I click on Network, I will see 4 items: NAS-CL4/private (Samba) NAS-CL4/media (Samba) NAS-CL4 (Samba) UPnP Clicking on either of the first two shows me the folders in that share. Clicking on the third item, NAS-CL4, shows me: media private Now, 98% of the time when it is not working, if I click on network I will see 2 items: NAS-CL4 (Samba) UPnP Clicking NAS-CL4 results in a timeout and an error. The share folders do not display.
Hide
Rafael Mizrahi [Boxee] added a comment - 26/May/11 3:57 AM
Craig, I see in your guisettings.xml that you are using winsserver
seems that you experience the same issue as described in BOXEE-8419
if WINS is not required, please remove the WINS server value and see if you can access the shares.
Show
Rafael Mizrahi [Boxee] added a comment - 26/May/11 3:57 AM Craig, I see in your guisettings.xml that you are using winsserver seems that you experience the same issue as described in BOXEE-8419 if WINS is not required, please remove the WINS server value and see if you can access the shares.
Hide
Craig Clark added a comment - 26/May/11 6:14 PM
That was a leftover from when I temporarily made my NAS box a WINS server in an attempt to resolve this issue. I tried it - it didn't help, so I disabled it on the NAS box, but forgot to remove that setting on the Boxee Box. I have removed it again. It seems irrelevant to this issue.

Show
Craig Clark added a comment - 26/May/11 6:14 PM That was a leftover from when I temporarily made my NAS box a WINS server in an attempt to resolve this issue. I tried it - it didn't help, so I disabled it on the NAS box, but forgot to remove that setting on the Boxee Box. I have removed it again. It seems irrelevant to this issue.
Hide
Craig Clark added a comment - 29/May/11 5:33 PM
Good news, and I hope I am not premature in this. I updated my Netgear ReadyNAS to RAIDiator 4.2.17 (which was released a couple of weeks ago) and so far the SMB shares have been 100% accessible from the Boxee Box. When I read the release notes for this firmware it didn't sound like anything would change related to the Boxee problem (I was running RAIDiator 4.2.15 before), but it did.
I have rebooted both devices multiple times and the Boxee Box always reconnects - immediately. Even better, no adverse affects on the other devices and computers accessing my ReadyNAS - they continue to work as reliably as ever. There was also a 4.2.16 release, but I never installed that one. So maybe it fixed the problem - but I'm not going to downgrade to find out. Just happy at this point everything is working again.

Just released – RAIDiator 4.2.17 (x86)

May 5, 2011

NETGEAR is pleased to announce the release of RAIDiator 4.2.17 (x86), the latest firmware for the following ReadyNAS network attached storage products:

ReadyNAS 2100
ReadyNAS 3100
ReadyNAS 3200
ReadyNAS 4200
ReadyNAS Ultra 2/Plus
ReadyNAS Ultra 4/Plus
ReadyNAS Ultra 6/Plus
ReadyNAS Pro 2
ReadyNAS Pro 4
ReadyNAS Pro 6
ReadyNAS Pro Business Edition
ReadyNAS Pro Pioneer Edition
ReadyNAS NVX
ReadyNAS NVX Pioneer Edition

The simplest way to update is to use the System/Update/Remote tab in Frontview. If you prefer, you can choose to do a local update by first downloading the new image here: RAIDiator-x86-4.2.17. We recommend that you update your ReadyNAS to this latest RAIDiator release to ensure your ReadyNAS is running with all the latest bug fixes and enhancements.
WARNING: If you update to 4.2.17, you will NOT be able to go back to 4.2.15 or earlier due to the automatic change in the partition format to support 3TB+ hard disks.

The following are changes since RAIDiator 4.2.16.

New features and enhancements

1. Provide download links for exported user and group lists instead of asking for an email address.
2. Raised iSCSI intiator limit to 256.
3. Updated ReadyNAS Remote to the latest version.

Bug fixes

1. Add monitoring support for the Ultra 2, Ultra 2 Plus, and Pro 2 CPU temperature. Speed up the fan quickly if the CPU temp rises out of conservative safe zone. This fixes a problem with the specified systems potentially freezing in higher temperature environments.
2. Fixed bug in log truncation that caused AFP service to quit.

Limitations

Once you upgrade to this release, you cannot downgrade back to 4.2.15 or prior releases.
IE 6 no longer supported. Please update to IE 7 or 8.
Volume expansion will not work beyond 16 TB. To support 16 TB or greater, you’ll have to factory default with that capacity in place.
Snapshot resizing is disabled in the release. We will re-enable this feature in a future update.
If you have previously configured an SNMP monitored UPS and attach a local USB UPS, the USB UPS will be monitored by the ReadyNAS. To switch back to SNMP monitoring, disconnect the USB UPS and then re-enter the IP address of the SNMP monitored UPS device.
ReadyNAS 3200 and 4200 are limited to 2TB on channels 5-12. Channels 1-4 supports 3TB+ drives with RAIDiator 4.2.16+.

Just released – RAIDiator 4.2.16 (x86)

April 4, 2011

NETGEAR is pleased to announce the release of RAIDiator 4.2.16 (x86), the latest firmware for the following ReadyNAS network attached storage products:
ReadyNAS 1500
ReadyNAS 2100
ReadyNAS 3100
ReadyNAS 3200
ReadyNAS 4200
ReadyNAS Ultra 2/Plus
ReadyNAS Ultra 4/Plus
ReadyNAS Ultra 6/Plus
ReadyNAS Pro 2
ReadyNAS Pro 4
ReadyNAS Pro 6
ReadyNAS Pro Business Edition
ReadyNAS Pro Pioneer Edition
ReadyNAS NVX
ReadyNAS NVX Pioneer Edition

The simplest way to update is to use the System/Update/Remote tab in Frontview. If you prefer, you can choose to do a local update by first downloading the new image here: RAIDiator-x86-4.2.16. We recommend that you update your ReadyNAS to this latest RAIDiator release to ensure your ReadyNAS is running with all the latest bug fixes and enhancements.
WARNING: If you update to 4.2.16, you will NOT be able to go back to 4.2.15 or earlier due to the automatic change in the partition format to support 3TB+ hard disks.

The following are changes since RAIDiator 4.2.15.

New features and enhancements

1. 3TB+ hard drives are now supported. ReadyNAS 3200 and 4200 can support 3TB+ hard disks only on channels 1-4. Channels 5-12 are limited to 2TB drives due to the limitation of the embedded LSI controller.
2. Volume expansion is now supported in Flex-RAID mode.
3. X-RAID2 can now migrate from a single to dual redundancy on 6-bay ReadyNAS and above. To do this, you will need to go to the Volume tab in Frontview and select the option to use the next added drive for dual redundancy, versus expansion (default).
4. RAID 10 is now supported in Flex-RAID mode. To use RAID 10, you must have free space in 4 drives or more.
5. iSCSI restore option now available in FrontView Backup.
6. IPv6 support added (limited to CIFS and FTP for the time-being. Keep in mind CIFS support requires DNS).
7. Teaming selection and support enhanced with switch level settings in 802.3 mode.
8. Add-on menu added, along with new pages for add-ons. You can now directly install add-ons and add-on updates from these pages.
9. Performance of large file writes over CIFS improved.
10. Added support for 4TB+ Time Machine backups.
11. Allow Windows workgroup names to contain spaces.
12. Added fan speed control for the ReadyNAS 2100.
13. Added monitoring and shutdown of APC UPS over SNMP.

Bug fixes

1. Added support for NETGEAR XSM7224S 10G switch.
2. Fixed USB 3.0 device not showing up in Backup tab on Ultra 2.
3. Fixed potential for infrequent iSCSI disconnections and potential hang with Windows MPIO.
4. Fixed scheduled wakeup from power timer.
5. Fixed file transfer problem using CIFS from OS X.
6. Fixed file size display issue on OS X using CIFS.
7. Fixed domain authentication issues with multiple NICs.
8. Fixed TiVo archival issues with Australian TiVos.
9. Fixed stability issue with RALUS.

Limitations

Once you upgrade to this release, you cannot downgrade back to 4.2.15 or prior releases.
IE 6 no longer supported. Please update to IE 7 or 8.
Volume expansion will not work beyond 16 TB. To support 16 TB or greater, you’ll have to factory default with that capacity in place.
Snapshot resizing is disabled in the release. We will re-enable this feature in a future update.
If you have previously configured an SNMP monitored UPS and attach a local USB UPS, the USB UPS will be monitored by the ReadyNAS. To switch back to SNMP monitoring, disconnect the USB UPS and then re-enter the IP address of the SNMP monitored UPS device.
ReadyNAS 3200 and 4200 are limited to 2TB on channels 5-12. Channels 1-4 supports 3TB+ drives with RAIDiator 4.2.16.
Show
Craig Clark added a comment - 29/May/11 5:33 PM Good news, and I hope I am not premature in this. I updated my Netgear ReadyNAS to RAIDiator 4.2.17 (which was released a couple of weeks ago) and so far the SMB shares have been 100% accessible from the Boxee Box. When I read the release notes for this firmware it didn't sound like anything would change related to the Boxee problem (I was running RAIDiator 4.2.15 before), but it did. I have rebooted both devices multiple times and the Boxee Box always reconnects - immediately. Even better, no adverse affects on the other devices and computers accessing my ReadyNAS - they continue to work as reliably as ever. There was also a 4.2.16 release, but I never installed that one. So maybe it fixed the problem - but I'm not going to downgrade to find out. Just happy at this point everything is working again. Just released – RAIDiator 4.2.17 (x86) May 5, 2011 NETGEAR is pleased to announce the release of RAIDiator 4.2.17 (x86), the latest firmware for the following ReadyNAS network attached storage products: ReadyNAS 2100 ReadyNAS 3100 ReadyNAS 3200 ReadyNAS 4200 ReadyNAS Ultra 2/Plus ReadyNAS Ultra 4/Plus ReadyNAS Ultra 6/Plus ReadyNAS Pro 2 ReadyNAS Pro 4 ReadyNAS Pro 6 ReadyNAS Pro Business Edition ReadyNAS Pro Pioneer Edition ReadyNAS NVX ReadyNAS NVX Pioneer Edition The simplest way to update is to use the System/Update/Remote tab in Frontview. If you prefer, you can choose to do a local update by first downloading the new image here: RAIDiator-x86-4.2.17. We recommend that you update your ReadyNAS to this latest RAIDiator release to ensure your ReadyNAS is running with all the latest bug fixes and enhancements. WARNING: If you update to 4.2.17, you will NOT be able to go back to 4.2.15 or earlier due to the automatic change in the partition format to support 3TB+ hard disks. The following are changes since RAIDiator 4.2.16. New features and enhancements 1. Provide download links for exported user and group lists instead of asking for an email address. 2. Raised iSCSI intiator limit to 256. 3. Updated ReadyNAS Remote to the latest version. Bug fixes 1. Add monitoring support for the Ultra 2, Ultra 2 Plus, and Pro 2 CPU temperature. Speed up the fan quickly if the CPU temp rises out of conservative safe zone. This fixes a problem with the specified systems potentially freezing in higher temperature environments. 2. Fixed bug in log truncation that caused AFP service to quit. Limitations Once you upgrade to this release, you cannot downgrade back to 4.2.15 or prior releases. IE 6 no longer supported. Please update to IE 7 or 8. Volume expansion will not work beyond 16 TB. To support 16 TB or greater, you’ll have to factory default with that capacity in place. Snapshot resizing is disabled in the release. We will re-enable this feature in a future update. If you have previously configured an SNMP monitored UPS and attach a local USB UPS, the USB UPS will be monitored by the ReadyNAS. To switch back to SNMP monitoring, disconnect the USB UPS and then re-enter the IP address of the SNMP monitored UPS device. ReadyNAS 3200 and 4200 are limited to 2TB on channels 5-12. Channels 1-4 supports 3TB+ drives with RAIDiator 4.2.16+. Just released – RAIDiator 4.2.16 (x86) April 4, 2011 NETGEAR is pleased to announce the release of RAIDiator 4.2.16 (x86), the latest firmware for the following ReadyNAS network attached storage products: ReadyNAS 1500 ReadyNAS 2100 ReadyNAS 3100 ReadyNAS 3200 ReadyNAS 4200 ReadyNAS Ultra 2/Plus ReadyNAS Ultra 4/Plus ReadyNAS Ultra 6/Plus ReadyNAS Pro 2 ReadyNAS Pro 4 ReadyNAS Pro 6 ReadyNAS Pro Business Edition ReadyNAS Pro Pioneer Edition ReadyNAS NVX ReadyNAS NVX Pioneer Edition The simplest way to update is to use the System/Update/Remote tab in Frontview. If you prefer, you can choose to do a local update by first downloading the new image here: RAIDiator-x86-4.2.16. We recommend that you update your ReadyNAS to this latest RAIDiator release to ensure your ReadyNAS is running with all the latest bug fixes and enhancements. WARNING: If you update to 4.2.16, you will NOT be able to go back to 4.2.15 or earlier due to the automatic change in the partition format to support 3TB+ hard disks. The following are changes since RAIDiator 4.2.15. New features and enhancements 1. 3TB+ hard drives are now supported. ReadyNAS 3200 and 4200 can support 3TB+ hard disks only on channels 1-4. Channels 5-12 are limited to 2TB drives due to the limitation of the embedded LSI controller. 2. Volume expansion is now supported in Flex-RAID mode. 3. X-RAID2 can now migrate from a single to dual redundancy on 6-bay ReadyNAS and above. To do this, you will need to go to the Volume tab in Frontview and select the option to use the next added drive for dual redundancy, versus expansion (default). 4. RAID 10 is now supported in Flex-RAID mode. To use RAID 10, you must have free space in 4 drives or more. 5. iSCSI restore option now available in FrontView Backup. 6. IPv6 support added (limited to CIFS and FTP for the time-being. Keep in mind CIFS support requires DNS). 7. Teaming selection and support enhanced with switch level settings in 802.3 mode. 8. Add-on menu added, along with new pages for add-ons. You can now directly install add-ons and add-on updates from these pages. 9. Performance of large file writes over CIFS improved. 10. Added support for 4TB+ Time Machine backups. 11. Allow Windows workgroup names to contain spaces. 12. Added fan speed control for the ReadyNAS 2100. 13. Added monitoring and shutdown of APC UPS over SNMP. Bug fixes 1. Added support for NETGEAR XSM7224S 10G switch. 2. Fixed USB 3.0 device not showing up in Backup tab on Ultra 2. 3. Fixed potential for infrequent iSCSI disconnections and potential hang with Windows MPIO. 4. Fixed scheduled wakeup from power timer. 5. Fixed file transfer problem using CIFS from OS X. 6. Fixed file size display issue on OS X using CIFS. 7. Fixed domain authentication issues with multiple NICs. 8. Fixed TiVo archival issues with Australian TiVos. 9. Fixed stability issue with RALUS. Limitations Once you upgrade to this release, you cannot downgrade back to 4.2.15 or prior releases. IE 6 no longer supported. Please update to IE 7 or 8. Volume expansion will not work beyond 16 TB. To support 16 TB or greater, you’ll have to factory default with that capacity in place. Snapshot resizing is disabled in the release. We will re-enable this feature in a future update. If you have previously configured an SNMP monitored UPS and attach a local USB UPS, the USB UPS will be monitored by the ReadyNAS. To switch back to SNMP monitoring, disconnect the USB UPS and then re-enter the IP address of the SNMP monitored UPS device. ReadyNAS 3200 and 4200 are limited to 2TB on channels 5-12. Channels 1-4 supports 3TB+ drives with RAIDiator 4.2.16.
Hide
Rafael Mizrahi [Boxee] added a comment - 30/May/11 6:44 AM
Craig, this is great news. thank you for sharing your findings with us and letting us know that updating the firmware of your Netgear ReadyNAS to RAIDiator 4.2.17 has solved the connectivity issues you had with Boxee.
Show
Rafael Mizrahi [Boxee] added a comment - 30/May/11 6:44 AM Craig, this is great news. thank you for sharing your findings with us and letting us know that updating the firmware of your Netgear ReadyNAS to RAIDiator 4.2.17 has solved the connectivity issues you had with Boxee.
Hide
Rafael Mizrahi [Boxee] added a comment - 30/May/11 7:41 AM
Rutger and the rest of the issue watchers,
please upgrade your netgear firmware and see if this solves your connectivity issues.
Show
Rafael Mizrahi [Boxee] added a comment - 30/May/11 7:41 AM Rutger and the rest of the issue watchers, please upgrade your netgear firmware and see if this solves your connectivity issues.
Hide
Yuval Tal [Boxee] added a comment - 09/Jun/11 4:12 PM
Fixed by firmware upgrade of the NAS. Nothing on the boxee side, so it seems.
Show
Yuval Tal [Boxee] added a comment - 09/Jun/11 4:12 PM Fixed by firmware upgrade of the NAS. Nothing on the boxee side, so it seems.
Hide
Craig Clark added a comment - 09/Jun/11 4:19 PM
I can confirm on my end, Boxee Box and Netgear ReadyNAS are still working together very nicely.
Show
Craig Clark added a comment - 09/Jun/11 4:19 PM I can confirm on my end, Boxee Box and Netgear ReadyNAS are still working together very nicely.
Hide
Ami Ben-David [Boxee] added a comment - 12/Jun/11 7:24 AM
Thanks Craig for the confirmation,
issue is closed.
if you guys experience this issue after upgrading your NAS firmware please open a new ticket in Jira.

Show
Ami Ben-David [Boxee] added a comment - 12/Jun/11 7:24 AM Thanks Craig for the confirmation, issue is closed. if you guys experience this issue after upgrading your NAS firmware please open a new ticket in Jira.

People

Vote (2)
Watch (5)

Dates

  • Created:
    20/Jan/11 4:25 PM
    Updated:
    12/Jul/11 10:19 AM
    Resolved:
    09/Jun/11 4:12 PM