LinuxMCE Forums
General => Users => Topic started by: ccoudsi on August 08, 2009, 08:31:25 am
-
Can you guys please double check this before I posted in the Wiki?? Thanks.
=======================================================
How to Install D-Link DNS-323 on LinuxMCE-810
[Dlink DNS-323]
http://www.dlink.com/products/?pid=509 (http://www.dlink.com/products/?pid=509)
The following instructions assume you’re using LinuxMCE version 8.10
Preparing the DNS-323
I recommend to setup the NAS first on your external network then move it to the internal LinuxMCE network.
1- Please follow manufacturer instruction for installing the SATA HDD.
2- Connect the NAS to you external network
3- Check the external router DHCP server for the NAS IP address, or use the utility that came with the NAS “Dlink Easy Search Utility” to locate the IP address
4- Log in to the NAS using any web browser on the external network by setting the URL to: http://NAS-IPaddress
5- Default “admin” password is “Blank, Nothing”, after log in, change admin default password (recommended), from “Tools/Admin Password”
6- Select suitable RAID level for your application and format the drives
7- Check NAS firmware version, it should have 1.07, from “Tools/Firmware” if not; follow manufacturer instruction to update the firmware
8- You should see “Volume_1” as a share directory, from “Advanced/Network access”
9- Add new user with password to the NAS, using “Advanced/Users-Group”
10- Remove default user “ALL” for the “Volume_1” share, and add the user you just created.
11- Set “Oplocks & Map archive” of the “Volume_1” share to “Yes”
12- From “Setup/Device” change workgroup to “linuxmce”
13- Make sure all other services/servers are off or disabled (FTP, UPnP AV, iTunes, DHCP, LLTD)
14- Power down the NAS & disconnect the Ethernet cable
15- Done with NAS preparation
Preparing the LinuxMCE
1- On the Core edit “/etc/samba/smb.conf” with your favorite editor
2- Add the following two lines to the end of the [global] section
lanman auth = yes
client lanman auth = yes
Example:
[global]
## BEGIN : Domain and Hostname
workgroup = LinuxMCE
server string = DCERouter
netbios name = DCERouter
## END : Domain and Hostname
smb ports = 139
log level = 2
invalid users = root
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
encrypt passwords = true
socket options = TCP_NODELAY
dns proxy = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
username map = /etc/samba/usermap.txt
unix extensions = yes
security = user
lanman auth = yes
client lanman auth = yes
[public]
3- save and quit
4- repeat step 2 to all the MDs in the house
5- Done with LinuxMCE preparation
DNS-323 Installation
1- Connect the NAS to the internal network
2- Power up the NAS
3- Wait couple minutes, LinuxMCE will detect it
4- LinuxMCE will ask if you want to use the DNS-323 as a “File server”, select “File Server”
5- Select location “Room”
6- LinuxMCE will install needed SW
7- LinuxMCE will ask to use reload the router, select “OK”, Don’t “reload” yet.
8- LinuxMCE will ask to use DNS-323/web_page as Windows share, select “No, and ignore it every time. Don’t ask again for this device”
9- LinuxMCE will ask to use DNS-323/ Volume_1 as Windows share, select “Yes”
10- LinuxMCE will ask “Regarding your new storage device, can it be used automatically for storing media, such as TV shows and music” select “YES”, or “ use it only when specifically told to”
11- LinuxMCE asks how to use the directory structure select
“YES”, use LinuxMCE’s directory structure”
12- LinuxMCE will ask you for username & Password, enter the ones you created above.
13- After it is done, reload router
14- LinuxMCE will ask to regenerate all orbiters in the house select “YES”
15- Now you can copy or move all your media files to the NAS
16- From the WebAdmin /Files & Media/Media Files Sync/ select Data folder on the left side and click “Resynchronize” wait until it is done
17- Now you should see your media on your Core and all your MDs
18- Done with the installation
19- Cheers {[Beer]
Troubleshooting
If you screwed up something with the above procedure, and you decided to start all over again, then follow the instruction below to remove the NAS from the PnpQueue, and reinstall it again:
1- Power down the NAS
2- Log in to the Mysql database "sudo mysql -uroot"
3- Select the table from the database "use pluto_main"
4- View all the devices in the queue, and locate the IP address of the NAS "SELECT * FROM PnpQueue;"
5- View all rows of the NAS to be sure, you should see at lease 2 rows "SELECT * FROM PnpQueue where IPaddress=’192.168.80.xxx’;"
6- Delete all rows related to the above IP address " DELETE FROM PnpQueue WHERE IPaddress=’192.168.80.xxx’;"
7- Quit Mysql "quit"
8- Reload the router
9- Turn ON the device
10- Now Linuxmce will detect the device automatically "PnP"
11- Done
-
Hi,
Here's a link with lots of pictures.
http://benchmarkreviews.com/index.php?option=com_content&task=view&id=58&Itemid=70&limit=1&limitstart=0
Only really need "client lanman auth = yes" .
After making changes to smb.conf you need to do (as sudo or root) service samba restart.
Good job.
Cheers.
-
Thanks Pigdog,
I will modify the instructions according to your recommendation
-
guys, can we do a device template for this unit, so that we don't have to PATCH samba.conf like this, EVERY TIME?
come on, fellas. Help us do the work to make this damn system plug and play.
-Thom
-
Thom,
I agree with you 100%, but Colin asked me to create a Wiki page, so at least people can use the Device until we make it PnP, I'm willing to do it, but I need sometime to learn the procedure, if you can guide me that will be great.
-
i've placed an inquiry to systems integration at D-Link today, to ask for a MAC address range for the device. If they reply back, then we may have an easy way to fill in the PnP section of a device template.
Otherwise, we'll need to use other ways to identify the device (such as a web page scrape)
-Thom
-
thom,
i will ask my old friends at dlink :-)
-
Here's the link to the Wiki page I created, you're welcome to modify it to make it clearer to the users.
http://wiki.linuxmce.org/index.php/D-Link_DNS-323_How_To_Install_On_LMCE-810 (http://wiki.linuxmce.org/index.php/D-Link_DNS-323_How_To_Install_On_LMCE-810)
P.S. How to keep the numbering sequence in the Wiki page from restarting to 1, when you add "code" or insert "image" in between steps??
Thanks,
-
I have updated my /usr/pluto/bin/Network_Setup.sh script to add "client lanman auth = yes" so that any changes made to networking will not lose the setting. I have attached it here as it will be required for anyone who wants username/password security with 8.10.
My understanding is that once the DNS-323 is setup as per the wiki it is going to be PnP as a normal samba share. How is a device template going to improve/help with making it PnP???
gadget
-
mostly because some NAS devices DO NOT like having this setting enabled, and this needs to be decided on a case by case basis.
-Thom
-
Thom,
After I updated my Core to 2.27 then 2.28, both my NAS share folders failed to mount, I shutdown everything, and rebooted the Core then the NAS no luck???
-
look in the logs for your NAS to see if there are failed password attempts.
-Thom
-
I checked all files under /var/log/pluto/ nothing directly related to the NAS except "StorageDevices.log" which there is not much info in it and "StorageDevices_Symlinks.log" which has the following since Sunday
Sun, 09 Aug 2009 22:03:53 -0700 Generating symlinks for storage device Windows Share-PUBLIC (104)
/home/user_1/data/pictures/Windows Share-PUBLIC [104] -> /mnt/device/104/user_1/data/pictures
/home/user_2/data/pictures/Windows Share-PUBLIC [104] -> /mnt/device/104/user_2/data/pictures
/home/public/data/pictures/Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/pictures
/home/user_1/data/audio/Windows Share-PUBLIC [104] -> /mnt/device/104/user_1/data/audio
/home/user_2/data/audio/Windows Share-PUBLIC [104] -> /mnt/device/104/user_2/data/audio
/home/public/data/audio/Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/audio
/home/user_1/data/documents/Windows Share-PUBLIC [104] -> /mnt/device/104/user_1/data/documents
/home/user_2/data/documents/Windows Share-PUBLIC [104] -> /mnt/device/104/user_2/data/documents
/home/public/data/documents/Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/documents
/home/user_1/data/videos/Windows Share-PUBLIC [104] -> /mnt/device/104/user_1/data/videos
/home/user_2/data/videos/Windows Share-PUBLIC [104] -> /mnt/device/104/user_2/data/videos
/home/public/data/videos/Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/videos
/home/user_1/data/games/MAME/Windows Share-PUBLIC [104] -> /mnt/device/104/user_1/data/games/MAME
/home/user_2/data/games/MAME/Windows Share-PUBLIC [104] -> /mnt/device/104/user_2/data/games/MAME
/home/public/data/games/MAME/Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/games/MAME
/home/user_1/data/pvr/Windows Share-PUBLIC [104] -> /mnt/device/104/user_1/data/pvr
/home/user_2/data/pvr/Windows Share-PUBLIC [104] -> /mnt/device/104/user_2/data/pvr
/home/public/data/pvr/Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/pvr
Sun, 09 Aug 2009 22:03:54 -0700 Generating symlinks for storage device Windows Share-Volume_1 (106)
/home/user_1/data/pictures/Windows Share-Volume_1 [106] -> /mnt/device/106/user_1/data/pictures
/home/user_2/data/pictures/Windows Share-Volume_1 [106] -> /mnt/device/106/user_2/data/pictures
/home/public/data/pictures/Windows Share-Volume_1 [106] -> /mnt/device/106/public/data/pictures
/home/user_1/data/audio/Windows Share-Volume_1 [106] -> /mnt/device/106/user_1/data/audio
/home/user_2/data/audio/Windows Share-Volume_1 [106] -> /mnt/device/106/user_2/data/audio
/home/public/data/audio/Windows Share-Volume_1 [106] -> /mnt/device/106/public/data/audio
/home/user_1/data/documents/Windows Share-Volume_1 [106] -> /mnt/device/106/user_1/data/documents
/home/user_2/data/documents/Windows Share-Volume_1 [106] -> /mnt/device/106/user_2/data/documents
/home/public/data/documents/Windows Share-Volume_1 [106] -> /mnt/device/106/public/data/documents
/home/user_1/data/videos/Windows Share-Volume_1 [106] -> /mnt/device/106/user_1/data/videos
/home/user_2/data/videos/Windows Share-Volume_1 [106] -> /mnt/device/106/user_2/data/videos
/home/public/data/videos/Windows Share-Volume_1 [106] -> /mnt/device/106/public/data/videos
/home/user_1/data/games/MAME/Windows Share-Volume_1 [106] -> /mnt/device/106/user_1/data/games/MAME
I tried to access the error log from WebAdmin, it says "Log not found:/var/log/pluto/106_Windows_Share.log"
-
try looking ON your NAS itself for a log that details failed password attempts.
-Thom
-
I didn't see any log option on the DNS-323, and on the Promise Technology there is "Event Log" it just have "System starting, shutdown, .. "that's it
BTW, the NS4300N, does not have password.
-
FYI,
I did not have problems updating to alpha 2.28 (no passwords) my data was there.
So to see waht was maybe going on...
I deleted my NAS and cleared out pluto_main references.
Shut everyone down. Rebooted, waited for LMCE to load, powered up NAS.
My DNS-323 is not being auto-discovered!!!
I will try different scenarios to see if it comes alive.
-
I double checked the device tree no NAS and no Windows Share-Volume_1 or Volume_2.
When I checked Files & Media|Media Files Sync and I click on videos in left window Files on Disk showed
Checked Windows Share-Volume_1 [51]
Checked Windows Share-Volume_2 [50]
From a console the /mnt directory did not have a device directory created.
I went back to webadmin and selected "Delete all missing files from database".
Got a response of...
Here
/home/public/data/videos
0
RemoveFile:650: /home/public/data/videos/Windows Share-Volume_1 [51]
RemoveFile:788: /home/public/data/videos/Windows Share-Volume_1 [50]
RemoveFile:786: /home/public/data/videos/Windows Share-Volume_2 [50]/Watchmen
RemoveFile:787: /home/public/data/videos/Windows Share-Volume_2 [50]/Caroline
RemoveFile:844: /home/public/data/videos/Windows Share-Volume_2 [50]/Inkheart
RemoveFile:1227: /home/public/data/videos/Windows Share-Volume_2 [50]/Underworld Rise of the Lycans
This changed "Files on disk" from checked - existing both on disk and in database to Exist only on disk.
I shutdown the NAS and rebooted Core.
I went back into webadmin and share volumes were still listed under Files & Media|Media Files Sync.
I powered up NAS. No discovery.
I powered down NAS.
Via console I went to /home/public/data directory and deleted the Windows Share-Volumes from videos/pvr/pictures/documents/audio
Rebooted Core.
Orbiter Generation Start
Orbiter generation Done
...nothing
Checked F8 - Starting DCERouter - waited 30 minutes - nothing - Shutdown (not reboot).
Came back up. Checked /home/public/data/videos - no files
Webadmin - Checked Files & Media|Media Files Sync and "Files on disk" showed nothing.
Powered up NAS. Nothing.
tried /usr/pluto/bin/StorageDevices_StatusRadar.sh background waited five minutes but got no response.
I powered down NAS and powered it up with StatusRader.sh still running and no response. Tried another port/hot - no response.
Rebooted NAS in new port - no response. Powered down Core.
Switched NAS to Fedora box. No problem seeing system and data.
I booted up the Core with the NAS powered up. Normally this causes cifs errors on start up. This time I got nothing.
I executed StausRadar.sh and got nothing. Ths DND-323 has an inactivity timer default=10 minutes. If nothing tries to access - hibernation. Mine hibernates.
Looks like it's time to reload.
-
Pigdog,
I think you should wait a bit on re-installing, maybe Thom will find the cause of the problem.
-
Hi,
Updated to 2.29. NAS was discovered.
Everything seems to be there.
Am monitoring.
-
Yep, 2.29 took care of the mount problem.
Thanks Pigdog & Thom.