• Content Count

  • Joined

  • Last visited

Posts posted by WannabeMKII

  1. Sorry for the lack of reply, very busy weekend and start to the week.


    My resolution was to update to 5.2, but it was far from straightforward. When I updated to 5.2, it appeared to work fine, but as soon as I restarted the NAS, the NAS dropped completely from the network, with no IP or anything.


    So I followed the following thread, in particular, this post - http://xpenology.com/forum/viewtopic.php?p=38545#p38545


    It's now working, but I've not tried a reboot the NAS to see if the IP stays, as I don't have the time to tinker if it doesn't at the moment. So I'm going to keep checking in on that thread to see how things progress.


    Appreciate the help from everyone, especially 'Thecapri'!


    I also hope this helps others!

  2. Did you try to map whit the ip not whit the name \\\share to see if it will work

    I have, yes. Was one of the first things I tried, as thought it might be DNS relaxed. But that didn't work.


    I'm wondering if it's worth resetting or similar, as long as the data stays intact.


    Just as an additional note, another NAS backs up to this NAS through Backup and Restore and it's saying my server is offline?

  3. Did you check the shares? And the permissions on the shares?

    Is Windows file service enabled?

    That was one of the first things I checked, as this was my concern. All shares are correct and the relevant tick boxes are ticked. I even tried disabling the Windows file service and restarting it, but no good.


    It's so frustrating and I bet it's something simple that I've overlooked, but I've spent about 4 hours trying different things, but nothing appears to work...


    Anything else I can try?

  4. Hello, first of all are you on a workgroup or a domain.

    I'm on a workgroup and the machines and NAS are on the same workgroup.


    Are you able to login in the web page? If yes try to create a new folder and see if it working.

    I can log into the web interface fine, but as I'm not able to navigate to the NAS through explorer, I'm unable to map or see any of the drives on the NAS. The connection fails at the first step, just connecting to the NAS.


    Any ideas?

  5. Just wanted to add, I've been through various forums and tried changing the workgroup along with the netBIOS setting for ipv4, but still no luck.


    Pinging the DNS name gives the correct IP and it does respond.


    Also, using Synology Assistant, when mapping a network drive, I get an error, "The network path was not found.(53)".


    I've turned off all security (AV and Firewalls), but still no success.


    Apple products appear to connect fine, just Windows...


    I'm guessing it's a setting somewhere, but can't see it anywhere, or something Windows is caching from 5.0?

  6. I've just updated from Nanoboot running DSM 5.0-4528 to XPEnoboot 5.1-5055.1 and DSM 5.1-5055.


    Everything appeared to go well, settings are all still present and correct, but when trying to access the shares or even the DiskStation through the network (via name or IP) through any of my Windows machines, Windows states "Windows cannot access \\DiskStation". I tried the diagnose through the prompts, which it advises "The remote device or resource won't accept the connection". I'm therefore thinking a setting has changed with the update?


    Anyone any ideas what may be causing this?

  7. Thanks for the pointer, I've found the following;

    DiskStation> du -ks *
    796     bin
    0       core
    96      dev
    6184    etc
    5768    etc.defaults
    4       initrd
    149480  lib
    5276    lib64
    4       lost+found
    4       mnt
    12      proc
    8       root
    8       run
    5288    sbin
    0       sys
    376     tmp
    338176  usr
    1880304 var
    156     var.defaults
    4       volume1
    4       volumeUSB1
    4       volumeUSB2


    DiskStation> cd /var
    DiskStation> du -ks *
    4       db
    4       empty
    76      lib
    8       lock
    1879636 log
    12      net-snmp
    308     packages
    12      quarantine
    188     run
    12      services
    24      spool
    8       state
    8       synobackup
    0       tmp


    DiskStation> cd /var/log/
    DiskStation> du -ks *
    45052   cloudsync
    4       cluster
    102932  cstn
    4       disk_log.xml
    4       disk_overview.xml
    368     dmesg
    48      dmesg.1.xz
    28      dpkg.log
    24      dpkg_upgrade.log
    52      httpd
    28      log.nmbd
    24      log.smbd
    4       lv_log_expand
    4       lvm_lv_create_log
    65164   messages
    168     messages.1.xz
    168     messages.2.xz
    168     messages.3.xz
    168     messages.4.xz
    0       mount.log
    4       nginx
    0       partition
    28      postgresql.log
    1662744 router.log
    0       rsync.error
    120     scemd.log
    4       smart_quick_log
    1208    synolog
    8       synopkg.log
    4       synoupdate.log
    520     syslog.log
    4       timebkp.debug
    576     upstart

    So if I'm reading that correctly, it's the "router.log" file that's causing the issue? Does that appear correct? I've search for info on that log file, with no luck. What's it's for and can I safely remove it? Or have I got it totally wrong?



  8. Quick update - I tried a reboot to see if that resolved the login issues and now the drives don't appear to be mounting, so I've now lost all storage :shock:


    This is all I see:


    DiskStation> df -h

    Filesystem Size Used Available Use% Mounted on

    /dev/md0 2.3G 2.3G 0 100% /

    /tmp 1.9G 216.0K 1.9G 0% /tmp


    Any ideas?

  9. Great news, I've now got root access again! :grin: So a step in the right direction.


    What is my next best step? I'm assuming something to do with XPENOboot?


    I'm currently using Nanoboot and running DSM 5.0-4528.


    I'd like to update to a more recent version, but keep all my files and setting intact. How am I best to go about this?


    FYI - I'm unable to log into the web interface, with an error of "You cannot login to the system because the disk space is full currently. Please restart the system and try again".


    Again all help appreciated and the help so far has been brilliant in moving me forwards!! :wink:

  10. Anyone any ideas or suggestions, as I'm stuck at the moment... Nearly 100 views, I was hoping someone could help point me in the right direction?


    Can I save the data on the drives if I build a new XPEnology NAS with the spare N54L I have?


    Any suggestions / ideas more than welcome!!

  11. Hi all, I'm after some assistance, as I'm in a bit of a situation on a barebones N54L running from an internal USB.


    1. I don't seem to be able to access the server to run updates, as the root password no longer appears to work after the last update, mentioned here -http://xpenology.com/forum/viewtopic.php?f=2&t=5051 Therefore, still running an older version that I'd like to update


    2. When trying to log into the web interface, or network shares with my account, I get an error message. Through the web interface, it's "You cannot log into the system the disk space is full currently. Please restart the system and try again". I've tried this, with no success, as I still can't access the GUI or network shares. I've read that certain log files need to be deleted using root, but as I've no root access, I'm unable to do this


    As you can see, I'm in quite a situation where I'm unable to access the system at all to resolve anything... :sad:


    Therefore, I'm after assistance with regards to what my options? Just to add, I'd REALLY like to keep all the data on the drives (3x 4TB drives in SHR). Also, I do have a second brand N54L in a box unused if that could help? Perhaps a new USB and move the drives across?


    Can anyone offer some guidance, as any help would be greatly appreciated!

  12. Are you sure you didn't enter a typo when you typed in the password for the update? You can always rollback and then apply the update again that will allow you to enter a fresh password.

    So am I right in thinking the root password never changes from my original password from day one and used when completing minor or major updates? Or is it set when major updates are installed?

  13. I've just updated from 4493 Update 5 to 4493 Update 7. I then updated to 4528, all with no problems.


    However, I've just tried to update to 4528 Update 2 and when logging in with SSH, the root password is no longer working.


    I know what the password is, as 15 minutes ago I did the exact same process to update from 4493 Update 5 to 4493 Update 7 and that worked without any issues.


    Can anyone please help?


    I'm also using Nanoboot if that info is need on a HP N54L running from USB as bare bones.