Jump to content
XPEnology Community

shteve

Member
  • Posts

    61
  • Joined

  • Last visited

Everything posted by shteve

  1. Good news! I had the advantage though as I just configured the microserver the same as I'd done on my CS407e - which microserver has now replaced. And one thing I've learnt from working with Unix/Linux is that if it isn't working, it's usually permissions hence mapping to admin anyway
  2. Interesting. Mine is working fine like that under OpenELEC, with the mySQL back-end hosted under DSM. I think your problem is the no_root_squash. I'm fairly sure that's the "Map to Admin" option under the DSM NFS privilege options.
  3. Mine shows the same as yours, that the module already exists. What does your's show with the command "ps |grep nfsd"? Here's what my /etc/exports looks like: /volume1/Movies 192.168.0.*(rw,async,no_wdelay,root_squash,insecure_locks,anonuid=1024,anongid=100) /volume2/tv 192.168.0.*(rw,async,no_wdelay,root_squash,insecure_locks,anonuid=1024,anongid=100) /volume4/Music 192.168.0.*(rw,async,no_wdelay,root_squash,insecure_locks,anonuid=1024,anongid=100) /volume4/Photos 192.168.0.*(rw,async,no_wdelay,root_squash,insecure_locks,anonuid=1024,anongid=100) /volume3/Movies\0402 192.168.0.*(rw,async,no_wdelay,root_squash,insecure_locks,anonuid=1024,anongid=100) /volume3/TV\0402 192.168.0.*(rw,async,no_wdelay,root_squash,insecure_locks,anonuid=1024,anongid=100)
  4. Have you enabled NFS in the DSM interface? You also need to set up NFS share permissions on your shared folders.
  5. Your N54L should be on the same network as your PC. Step 7 is running Synology Assistant on your other PC, not on the microserver. You get synology assistant from here: http://www.synology.com/support/downloa ... s&m=DS413j And use the DSM images from this thread: viewtopic.php?f=2&t=907
  6. I changed the MAC using the method from post 4 of this thread: viewtopic.php?f=2&t=6
  7. You need to write it to the USB stick as per the original install. The IIRC synology assistant reports your DS as upgradeable. I didn't lose any data, but I have it all backed up anyway as I have just migrated my CS407e from 500GB disks to 1TB disks - just before finding out about xpenology and the HP54l. My initial (fresh to the microserver) install did blank my disks, but I just restored from the backups. The upgrade left everything intact, though I was very nervous doing it!
  8. The one posted by Gerbenz worked straight away on my n54l. Even USB works without any tweaking. viewtopic.php?f=2&t=907
  9. I've got NFS working on mine. Found this on another forum (which links back to here!) and it worked after this. Having said that, I also upgraded to DS3612xs_4.2-3211_x64 and NFS worked out of the box. FWIW, I checked for nfsd running via the ps command rather than rpcinfo. I noticed that the nfsd.ko module wasn't being loaded - hence NFS wasn't functional. A bit of googling took me to: viewtopic...ilit=nfs#p2600 It seems that the module "auth_rpcgss.ko" is required by nfsd.ko and needs to be loaded if NFS is enabled... so you just need to add the following towards the end of the /etc/rc file File: /etc/rc ------------------------------------------------------------ .. ..##### Start Load module for NFS ##### Support=`/bin/get_key_value /etc.defaults/synoinfo.conf supportNFS` if [ "$Support" = "yes" ]; then insmod /lib/modules/auth_rpcgss.ko fi ##### END Load module for NFS ##### SYNOTunnel exit 0
  10. Well, as old said, you press a key combination in the BIOS to copy the current settings to the backup BIOS. This is then what is copied back in the case of a corrupt primary BIOS. I'm only going by what was posted here as I've not had a Gigabyte board for donkey's years and even when I did I didn't need to use the backup BIOS.
  11. Just registered to add that I'm seeing this bug too with my microserver. I don't think it is related to shutting down as it happens on mine when I physically power it off too. I've tried the original hacked BIOS, and TheBay's simplified one. Both lose the IDE/SATA settings once DSM has been run. I suppose I could try disabling all of my power on/off scheduling to see if that's related - worrying if it is as it would be blind luck that the BIOS address being written to doesn't have more catastrophic effects.
×
×
  • Create New...