YAMJ+eversion: NFS no longer works with new PCH firmware on C200

[halfelite]

you have your own settings.xml and at the bottom it contains the version number remove that part from your settings.xml, most people copy the whole esettings-default.xml which is bad for that reason lol

[mikoz]

Well, after 5 hours and my wife almost killing me, I fixed it. Here are the problems:

1. upgrading to the new PCH FW broke eversion over NFS <-- yes, it really did, I swear.

2. Upgrading to the latest eversion skin was problematic. How thi was resolved: I had to remove all of the files in the Jukebox directory and start over

3. Upgrading PCH C200 FW also mangled the IP address of my server: it added a 168. in front of the IP address in the network share.

[halfelite]

1. Yes we knew this would happen the 300 series and v8 have used the same NFS stuff since launch so we knew a new eversion version was needed.

2. Again most likely due to you copied esettings-default.xml to esettings.xml at the bottom it has the version of eversion it was created with and will give you that bad install error if left in.

3. No idea about it mangling NFS shares none of my shares were ever mangled

[mikoz]

(05-28-2012 01:14 AM)halfelite Wrote:  1. Yes we knew this would happen the 300 series and v8 have used the same NFS stuff since launch so we knew a new eversion version was needed.

2. Again most likely due to you copied esettings-default.xml to esettings.xml at the bottom it has the version of eversion it was created with and will give you that bad install error if left in.

3. No idea about it mangling NFS shares none of my shares were ever mangled

Hi, thanks.

One final question: is NFS-TCP with eversion working properly with the latest PCH FW for c200 and R1067 eversion? I know that older combinations only worked with NFS as opposed to NFS-TCP

[accident]

Technically nfs-tcp it works in all versions of the firmware if you have the share defined as such in the settings. It's when your not adding shares to your settings that it has no way of targeting nfs vs nfs-tcp. But the reason for the settings is because the code to do it if the firmware ever allows is there, but until it is, you need eversion to play compatible with your player abilities.

I'm not sure what your entire setup is but I have to say that something is really knocking it out of wack. What your describing as part of the updating process is somethign nobody else is experiencing. My guess is you have either something running or installed that is wrecking havoc on your system OR you have hardware damage. I'd be more willing to say it's somethign running that your not mentioning because of your other threads with strange only you have issues.

[mikoz]

Hmmm, I thought there was a post on the eversion site (and many have commented) that NFS (not nfs-tcp) had problems with the eversion skin, at least before the latest PCH FW upgrade and/or eversion upgrade.

[accident]

There is no way to tell the hardware to mount nfs vs nfs-tcp. But you can setup nfs-tcp in your share settings and use nfs paths and it'll mount as nfs-tcp. You can recreate this behavior in the automounting options by enabling automount and telling it to use the nfs command to mount. it also translates to nfs:// direct paths. many do find the nfs:// urls to be more reliable on the 300s than the file:// and letting eversion translate the path for you.

It's a short in the dark but you can try the experimental version. It doesn't do any mounting but calls the player in a way closer to how syabas changed the api for there interface to call it.. It's experimental for a reason.

BTW: 35MB/sec I wouldn't call working well. Is this an original WHS with the old ip stack?