vtrchan

Trial of Nanoboot (4493) - 5.0.3.1

Recommended Posts

Hi,

I can't get it managed to get my rtl8110sc running.

While updating DSM to 4493 it works, but when booting into it, it doesn't work anymore.

please help

 

I solved my problem. It was the wifi or bluetooth dongle that was connected to the computer. Just had to disconnect them.

 

Also I managed to boot nano boot without video card by editing the syslinux.cfg. Without editing it, nano boot failed to start.

This is all what is in it:

DEFAULT /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N0xxxx vid=0x0780 pid=0x5560 loglevel=0

Share this post


Link to post
Share on other sites

I have connect a USB wifi dongle which was not detected when i go into DMS. any know the command to find out what drivers are needed?

cheers

andy

Share this post


Link to post
Share on other sites

Hi all,

I have installed successfully DSM5 - 5.0.3.1. Nanoboot 4493 update 1 and my question is

if its possible to install mini pci-express WiFi card from REALTEK RTL-8188CE (or 8192CE - 10ec:8178) ?

USB WIFI Stick with this same chipset work perfect but with mini pci-express card I can connect external antennas.

 

BR

Adam

Edited by Guest

Share this post


Link to post
Share on other sites

Hi there,

 

Can someone explain me where i can find a documentation of all options I can use in the cfg file ?

 

2 posts before, I can see

ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N0xxxx vid=0x0780 pid=0x5560 loglevel=0

 

Is it by that way i can change the hardware before installation ? Because all versions of dsm i installed are ds214play, and i want to make a raid 5 (only available in a 3612xs ?)

 

Am i supposed to add only "syno_hw_version=DS3612xs" in the cfg file of my ds214play nanoboot ?

 

Thanks for reply

Share this post


Link to post
Share on other sites
Is it by that way i can change the hardware before installation ? Because all versions of dsm i installed are ds214play, and i want to make a raid 5 (only available in a 3612xs ?)

 

Am i supposed to add only "syno_hw_version=DS3612xs" in the cfg file of my ds214play nanoboot ?

 

You have to try..

 

Anyone tried 5.0-4493 update 2 yet?

 

Version: 5.0-4493 Update 2

(2014/06/27)
Improvements

Enabled SSD Read/Write Cache function on RS3614(RP)xs.
Fixed Issues

Fixed several issues which occurred when managing EDS14 via CMS service.
Fixed an issue that could cause High Availability to be unable to function properly or fail to set up after DSM upgrades.

 

Download 3612xs http://ukdl.synology.com/download/criticalupdate/update_pack/4493-2/synology_bromolow_3612xs.pat

md5 3612xs http://ukdl.synology.com/download/criticalupdate/update_pack/4493-2/synology_bromolow_3612xs.pat.md5

 

 

Just Updated my box. Works fine.

6dIUkWj.png

 

Steps I used to update:

1. Download the update file. (link above)

2. Go into Synologys Control Panel/Update&Restore

3. Click Manual Update

4. Upload Update, but do not click 'OK' right after update.

5. SSH into your box and type the following:

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

6. Go back to DSM and click the 'OK' button.

7. Let the box restart and refresh the page after some time. Success!

Share this post


Link to post
Share on other sites
Is it by that way i can change the hardware before installation ? Because all versions of dsm i installed are ds214play, and i want to make a raid 5 (only available in a 3612xs ?)

 

Am i supposed to add only "syno_hw_version=DS3612xs" in the cfg file of my ds214play nanoboot ?

 

You have to try..

 

Anyone tried 5.0-4493 update 2 yet?

 

Version: 5.0-4493 Update 2

(2014/06/27)
Improvements

Enabled SSD Read/Write Cache function on RS3614(RP)xs.
Fixed Issues

Fixed several issues which occurred when managing EDS14 via CMS service.
Fixed an issue that could cause High Availability to be unable to function properly or fail to set up after DSM upgrades.

 

Download 3612xs http://ukdl.synology.com/download/criticalupdate/update_pack/4493-2/synology_bromolow_3612xs.pat

md5 3612xs http://ukdl.synology.com/download/criticalupdate/update_pack/4493-2/synology_bromolow_3612xs.pat.md5

 

 

Just Updated my box. Works fine.

6dIUkWj.png

 

Steps I used to update:

1. Download the update file. (link above)

2. Go into Synologys Control Panel/Update&Restore

3. Click Manual Update

4. Upload Update, but do not click 'OK' right after update.

5. SSH into your box and type the following:

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

6. Go back to DSM and click the 'OK' button.

7. Let the box restart and refresh the page after some time. Success!

 

 

Update 2

 

Working! All ok

Share this post


Link to post
Share on other sites
Is it by that way i can change the hardware before installation ? Because all versions of dsm i installed are ds214play, and i want to make a raid 5 (only available in a 3612xs ?)

 

Am i supposed to add only "syno_hw_version=DS3612xs" in the cfg file of my ds214play nanoboot ?

 

You have to try..

 

Anyone tried 5.0-4493 update 2 yet?

 

Version: 5.0-4493 Update 2

(2014/06/27)
Improvements

Enabled SSD Read/Write Cache function on RS3614(RP)xs.
Fixed Issues

Fixed several issues which occurred when managing EDS14 via CMS service.
Fixed an issue that could cause High Availability to be unable to function properly or fail to set up after DSM upgrades.

 

Download 3612xs http://ukdl.synology.com/download/criticalupdate/update_pack/4493-2/synology_bromolow_3612xs.pat

md5 3612xs http://ukdl.synology.com/download/criticalupdate/update_pack/4493-2/synology_bromolow_3612xs.pat.md5

 

 

Just Updated my box. Works fine.

6dIUkWj.png

 

Steps I used to update:

1. Download the update file. (link above)

2. Go into Synologys Control Panel/Update&Restore

3. Click Manual Update

4. Upload Update, but do not click 'OK' right after update.

5. SSH into your box and type the following:

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

6. Go back to DSM and click the 'OK' button.

7. Let the box restart and refresh the page after some time. Success!

 

 

Update 2

 

Working! All ok

Share this post


Link to post
Share on other sites

As mentioned elsewhere in this forum you can make a scheduled task from the commands and avoid having to SSH into DSM. just run the task and install update

Share this post


Link to post
Share on other sites

I'm experiencing problems copying files to the usbshare2 (from Windows) - a 4TB USB drive (NTFS) connected to the N54L server running DSM 5.0 Update 1 (via Nanoboot).

 

Judging by the smdb.log file Samba unexpectedly dies. Copied file is created (it's blank though) but I can't access it w/o rebooting the server (file is locked).

 

I didn't have this problem before while using gnoBoot.

 

It's worth mentioning that while I can't COPY files to the usbshare2 I can still DOWNLOAD/RENAME/DELETE them w/o any issues.

 

The issue occurs regardless of the path, filename and filesize,

 

  
check_user_ok: user admin is an admin user. Setting uid as 0
smbd/service.c:1169: [2014/06/27 20:50:26.621706, all 1, pid=27664] make_connection_snum
 UMSPC (192.168.1.20) connect to service usbshare2 initially as user admin (uid=0, gid=100) (pid 27664)
smbd/sesssetup.c:1417: [2014/06/27 20:50:26.622110, all 2, pid=27664] setup_new_vc_session
 setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
smbd/vfs.c:1131: [2014/06/27 20:50:26.622980, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [1234567890ABCDEFG01.txt] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.623097, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: 1234567890ABCDEFG01.txt reduced to /volumeUSB2/usbshare/1234567890ABCDEFG01.txt
smbd/vfs.c:1131: [2014/06/27 20:50:26.623669, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [.] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.623766, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: . reduced to /volumeUSB2/usbshare
smbd/vfs.c:1131: [2014/06/27 20:50:26.647827, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [.] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.647915, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: . reduced to /volumeUSB2/usbshare
smbd/trans2.c:2966: [2014/06/27 20:50:26.648113, all 3, pid=27664] smbd_do_qfsinfo
 smbd_do_qfsinfo: level = 1001
smbd/trans2.c:2966: [2014/06/27 20:50:26.648253, all 3, pid=27664] smbd_do_qfsinfo
 smbd_do_qfsinfo: level = 1005
smbd/trans2.c:2966: [2014/06/27 20:50:26.648639, all 3, pid=27664] smbd_do_qfsinfo
 smbd_do_qfsinfo: level = 1007
lib/sysquotas.c:470: [2014/06/27 20:50:26.649010, quota 3, pid=27664] sys_get_quota
 sys_get_vfs_quota() failed for mntpath[/volumeUSB2/usbshare] bdev[/dev/sdu1] qtype[2] id[0]: Function not implemented
lib/sysquotas.c:470: [2014/06/27 20:50:26.649209, quota 3, pid=27664] sys_get_quota
 sys_get_vfs_quota() failed for mntpath[/volumeUSB2/usbshare] bdev[/dev/sdu1] qtype[4] id[100]: Function not implemented
smbd/vfs.c:1131: [2014/06/27 20:50:26.665068, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [1234567890ABCDEFG01.txt] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.665228, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: 1234567890ABCDEFG01.txt reduced to /volumeUSB2/usbshare/1234567890ABCDEFG01.txt
smbd/dosmode.c:335: [2014/06/27 20:50:26.665269, all 3, pid=27664] unix_mode
 unix_mode(1234567890ABCDEFG01.txt) returning 0777
smbd/open.c:810: [2014/06/27 20:50:26.666450, all 2, pid=27664] open_file
 admin opened file 1234567890ABCDEFG01.txt read=Yes write=Yes (numopen=3)
smbd/oplock_linux.c:160: [2014/06/27 20:50:26.666582, locking 3, pid=27664] linux_set_kernel_oplock
 linux_set_kernel_oplock: got kernel oplock on file 1234567890ABCDEFG01.txt, file_id = 4141:5563:0 gen_id = 2260675554
smbd/dosmode.c:335: [2014/06/27 20:50:26.666626, all 3, pid=27664] unix_mode
 unix_mode(1234567890ABCDEFG01.txt) returning 0777
smbd/trans2.c:7802: [2014/06/27 20:50:26.667938, all 3, pid=27664] smbd_do_setfilepathinfo
 smbd_do_setfilepathinfo: 1234567890ABCDEFG01.txt (fnum 12406) info_level=1020 totdata=8

and then ..

smbd/server.c:314: [2014/06/27 20:50:26.671574, all 3, pid=27454] remove_child_pid
 smbd/server.c:314 Unclean shutdown of pid 27664
smbd/server.c:322: [2014/06/27 20:50:26.671661, all 1, pid=27454] remove_child_pid
 Scheduled cleanup of brl and lock database after unclean shutdown
smbd/server.c:275: [2014/06/27 20:50:46.693236, all 1, pid=27454] cleanup_timeout_fn
 Cleaning up brl and lock database after unclean shutdown

 

I've checked permissions to the share and everything seems to be fine there (group users has read/write access).

 

There are no issues when I first copy file to volume1 and then move it to usbshare2 - only with directly accessing the share from windows.

 

Any ideas?

Share this post


Link to post
Share on other sites
I'm experiencing problems copying files to the usbshare2 (from Windows) - a 4TB USB drive (NTFS) connected to the N54L server running DSM 5.0 Update 1 (via Nanoboot).

 

Judging by the smdb.log file Samba unexpectedly dies. Copied file is created (it's blank though) but I can't access it w/o rebooting the server (file is locked).

 

I didn't have this problem before while using gnoBoot.

 

It's worth mentioning that while I can't COPY files to the usbshare2 I can still DOWNLOAD/RENAME/DELETE them w/o any issues.

 

The issue occurs regardless of the path, filename and filesize,

 

  
check_user_ok: user admin is an admin user. Setting uid as 0
smbd/service.c:1169: [2014/06/27 20:50:26.621706, all 1, pid=27664] make_connection_snum
 UMSPC (192.168.1.20) connect to service usbshare2 initially as user admin (uid=0, gid=100) (pid 27664)
smbd/sesssetup.c:1417: [2014/06/27 20:50:26.622110, all 2, pid=27664] setup_new_vc_session
 setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
smbd/vfs.c:1131: [2014/06/27 20:50:26.622980, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [1234567890ABCDEFG01.txt] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.623097, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: 1234567890ABCDEFG01.txt reduced to /volumeUSB2/usbshare/1234567890ABCDEFG01.txt
smbd/vfs.c:1131: [2014/06/27 20:50:26.623669, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [.] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.623766, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: . reduced to /volumeUSB2/usbshare
smbd/vfs.c:1131: [2014/06/27 20:50:26.647827, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [.] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.647915, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: . reduced to /volumeUSB2/usbshare
smbd/trans2.c:2966: [2014/06/27 20:50:26.648113, all 3, pid=27664] smbd_do_qfsinfo
 smbd_do_qfsinfo: level = 1001
smbd/trans2.c:2966: [2014/06/27 20:50:26.648253, all 3, pid=27664] smbd_do_qfsinfo
 smbd_do_qfsinfo: level = 1005
smbd/trans2.c:2966: [2014/06/27 20:50:26.648639, all 3, pid=27664] smbd_do_qfsinfo
 smbd_do_qfsinfo: level = 1007
lib/sysquotas.c:470: [2014/06/27 20:50:26.649010, quota 3, pid=27664] sys_get_quota
 sys_get_vfs_quota() failed for mntpath[/volumeUSB2/usbshare] bdev[/dev/sdu1] qtype[2] id[0]: Function not implemented
lib/sysquotas.c:470: [2014/06/27 20:50:26.649209, quota 3, pid=27664] sys_get_quota
 sys_get_vfs_quota() failed for mntpath[/volumeUSB2/usbshare] bdev[/dev/sdu1] qtype[4] id[100]: Function not implemented
smbd/vfs.c:1131: [2014/06/27 20:50:26.665068, vfs 3, pid=27664] check_reduced_name
 check_reduced_name [1234567890ABCDEFG01.txt] [/volumeUSB2/usbshare]
smbd/vfs.c:1265: [2014/06/27 20:50:26.665228, vfs 3, pid=27664] check_reduced_name
 check_reduced_name: 1234567890ABCDEFG01.txt reduced to /volumeUSB2/usbshare/1234567890ABCDEFG01.txt
smbd/dosmode.c:335: [2014/06/27 20:50:26.665269, all 3, pid=27664] unix_mode
 unix_mode(1234567890ABCDEFG01.txt) returning 0777
smbd/open.c:810: [2014/06/27 20:50:26.666450, all 2, pid=27664] open_file
 admin opened file 1234567890ABCDEFG01.txt read=Yes write=Yes (numopen=3)
smbd/oplock_linux.c:160: [2014/06/27 20:50:26.666582, locking 3, pid=27664] linux_set_kernel_oplock
 linux_set_kernel_oplock: got kernel oplock on file 1234567890ABCDEFG01.txt, file_id = 4141:5563:0 gen_id = 2260675554
smbd/dosmode.c:335: [2014/06/27 20:50:26.666626, all 3, pid=27664] unix_mode
 unix_mode(1234567890ABCDEFG01.txt) returning 0777
smbd/trans2.c:7802: [2014/06/27 20:50:26.667938, all 3, pid=27664] smbd_do_setfilepathinfo
 smbd_do_setfilepathinfo: 1234567890ABCDEFG01.txt (fnum 12406) info_level=1020 totdata=8

and then ..

smbd/server.c:314: [2014/06/27 20:50:26.671574, all 3, pid=27454] remove_child_pid
 smbd/server.c:314 Unclean shutdown of pid 27664
smbd/server.c:322: [2014/06/27 20:50:26.671661, all 1, pid=27454] remove_child_pid
 Scheduled cleanup of brl and lock database after unclean shutdown
smbd/server.c:275: [2014/06/27 20:50:46.693236, all 1, pid=27454] cleanup_timeout_fn
 Cleaning up brl and lock database after unclean shutdown

 

I've checked permissions to the share and everything seems to be fine there (group users has read/write access).

 

There are no issues when I first copy file to volume1 and then move it to usbshare2 - only with directly accessing the share from windows.

 

Any ideas?

 

I don't really know a solution, but maybe a workaround.. Have you tried copy your files with ssh as root?

 

cp /volume1/YOURFILE /volumeUSB2/share/YOURFILE

 

maybe making a dmesg for more information

dmesg > /volume1/FOLDER/dmesg.txt

Share this post


Link to post
Share on other sites
I'm experiencing problems copying files to the usbshare2 (from Windows) - a 4TB USB drive (NTFS) connected to the N54L server running DSM 5.0 Update 1 (via Nanoboot).

Judging by the smdb.log file Samba unexpectedly dies. Copied file is created (it's blank though) but I can't access it w/o rebooting the server (file is locked).

 

..snip..

 

 

I don't really know a solution, but maybe a workaround.. Have you tried copy your files with ssh as root?

 

cp /volume1/YOURFILE /volumeUSB2/share/YOURFILE

 

maybe making a dmesg for more information

dmesg > /volume1/FOLDER/dmesg.txt

 

I can copy files onto /volumeUSB2/usbshare/ via SSH - there's no problem with it whatsoever.

 

I think I'm onto something as I just tried doing the same thing on another computer and it worked without any problems.

 

There may be an issue with credentials stored on my main computer as I was using it before the gnoBoot -> Nanoboot change. It's possible that Windows keeps some incorrect credentials and keeps on passing them onto the DSM and crashes Samba in the process.

 

I'll try clearing up credentials on my Windows machine then report here if I fix it.

Share this post


Link to post
Share on other sites

Hi,

 

I just upgrade from GNOboot to Nanoboot 5.0.2.1 and DSM 5.0 4482, running as a VM in my HP N54L on ESXi 5.5.

Question is can I just upgrade to Nanoboo 5.0.3.1.

 

Thanks

 

A noob

AndyNg

Share this post


Link to post
Share on other sites
Hi,

 

I just upgrade from GNOboot to Nanoboot 5.0.2.1 and DSM 5.0 4482, running as a VM in my HP N54L on ESXi 5.5.

Question is can I just upgrade to Nanoboo 5.0.3.1.

 

Thanks

 

A noob

AndyNg

 

Yes you can just upgrade nanoboot versions without any problems. Just when you want to upgrade DSM you have to choose that in the nanoboot menu.

 

 

Gesendet von iPhone mit Tapatalk

Share this post


Link to post
Share on other sites
Hi,

 

I just upgrade from GNOboot to Nanoboot 5.0.2.1 and DSM 5.0 4482, running as a VM in my HP N54L on ESXi 5.5.

Question is can I just upgrade to Nanoboo 5.0.3.1.

 

Thanks

 

A noob

AndyNg

 

Yes you can just upgrade nanoboot versions without any problems. Just when you want to upgrade DSM you have to choose that in the nanoboot menu.

 

 

Gesendet von iPhone mit Tapatalk

Share this post


Link to post
Share on other sites

Hey guys,

 

i just upgrade from Trantor his DSM 5.0 beta to Nano-boot 5.0.3.1/ 4493 update 2 without major issues. Only one bugging point and that is that my Gigabit Network Realtek 8111f is only seen als 100 Mpbs instead of 1000 Mbps.

 

Anyone having this same issue and found a solution for this issue ?

 

Greetz.

593ef3b27c1b0_Schermafbeelding2014-06-29om13_49_50.png.82b60ef55bd4306fe64b455d4a012888.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.