arTii Posted October 16, 2020 Share #1 Posted October 16, 2020 I had Xpenology 6.1.x and updated it to 6.2.3. After the update, the services did not start first, and now I cannot access the webservice. Ssh access works. Where is the cause? I've already changed the computer, changed the disks and still can't access the webservice. bootloader 1.03b DS3617xs Quote Link to comment Share on other sites More sharing options...
arTii Posted October 16, 2020 Author Share #2 Posted October 16, 2020 Additional informations: - SMB - work - FTP - work - Mail Server - work - but all services in tjhe web - not works. Cannot start ngix, Apache2.2 and 2.4 and I have one directory with problem... /volume1/@tmp d?????????? ? ? ? ? ? @tmp d---------+ 11 root root 4096 Dec 2 2019 TMP d---------+ 7 root root 4096 Dec 4 2019 video d---------+ 5 root root 4096 May 25 2018 VirtualBox VMs d---------+ 16 root root 4096 Jul 8 19:01 web Quote Link to comment Share on other sites More sharing options...
billat29 Posted October 16, 2020 Share #3 Posted October 16, 2020 Are you able to log in to the DSM desktop? And what happens when you do? Quote Link to comment Share on other sites More sharing options...
Guest Posted October 16, 2020 Share #4 Posted October 16, 2020 Hello,I had a similar problem, I was not able to "fix" DSM. I carried out an update of DSM which solved the problem. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted October 17, 2020 Share #5 Posted October 17, 2020 22 hours ago, arTii said: - but all services in tjhe web - not works. Cannot start ngix, Apache2.2 and 2.4 the documented case here is the existance of a directory ".xepnology" in root ("/") thats usually when comming from 5.x, did you update your system from 5.x to 6.1 in the past, ssh into the system and check for that directory, delete it https://xpenology.com/forum/topic/26723-network-down-after-dsm-login/ Quote Link to comment Share on other sites More sharing options...
billat29 Posted October 17, 2020 Share #6 Posted October 17, 2020 (edited) 3 hours ago, IG-88 said: the documented case here is the existance of a directory ".xepnology" in root ("/") /.xpenoboot 😀 Edited October 17, 2020 by billat29 Quote Link to comment Share on other sites More sharing options...
arTii Posted October 19, 2020 Author Share #7 Posted October 19, 2020 On 10/16/2020 at 10:17 PM, billat29 said: Are you able to log in to the DSM desktop? And what happens when you do? No I don't - no any page On 10/17/2020 at 3:49 PM, billat29 said: /.xpenoboot 😀 I'm remove, but still no response from DSM at the port 5000 or 5001 I'm mean - problem is in folder /volume1/@tmp this folder is no owner, no attributes root@DSM-Osmeckiego:/volume1$ ls -la /volume1 ls: cannot access /volume1/@tmp: Input/output error total 17864 drwxr-xr-x 37 root root 4096 Oct 19 10:31 . drwxr-xr-x 24 root root 4096 Oct 19 10:31 .. d---------+ 3 root root 4096 Mar 25 2020 AAAA drwxr-xr-x 45 root root 4096 Oct 16 12:08 @appstore -rw------- 1 root root 23552 Oct 19 10:25 aquota.group -rw------- 1 root root 26624 Oct 19 10:25 aquota.user d---------+ 5 root root 4096 Sep 23 15:15 BBBB drwxr-xr-x 2 root root 4096 Oct 15 11:07 @clamav drwxr-xr-x 7 root root 4096 Sep 8 06:30 @cloudsync drwxr-xr-x 8 admin users 4096 Oct 8 08:59 @database d---------+ 22 root root 4096 Sep 25 2019 CCCCC drwxr-xr-x 4 DownloadStation DownloadStation 4096 Aug 26 00:46 @download drwxrwxrwx+ 18 root root 4096 Sep 23 15:15 @eaDir -rw------- 1 root root 22949888 Nov 12 2019 @ffmpeg.core drwx--x--x+ 12 root root 4096 Apr 15 2020 homes -rw------- 1 root root 225280 Sep 24 12:06 @ipcalc.core drwxr-xr-x 2 root root 4096 May 23 2018 @ipkgui_archive drwx------ 3 root root 4096 Aug 12 2018 @iSCSI d---------+ 5 root root 4096 Sep 23 09:43 DDD d---------+ 6 root root 4096 Oct 15 11:15 Log drwx------ 2 root root 16384 May 23 2018 lost+found drwxr-xr-x 2 root root 4096 Oct 10 02:25 @maillog drwxr-xr-x 5 root root 4096 Oct 15 11:07 @MailScanner d---------+ 26 root root 4096 Aug 12 2018 EEE drwxrwxr-x 11 root root 4096 May 25 2018 @optware drwxrwxrwx 4 root root 4096 Nov 12 2019 photo -rw------- 1 root root 555443 Oct 15 11:07 @php56-fpm.core.gz -rw------- 1 root root 560685 Oct 19 10:31 @php70-fpm.core.gz drwxr-xr-x 16 postfix root 4096 Apr 22 05:11 @postfix -rw------- 1 root root 389120 Jan 13 2020 @pptpcm.core d---------+ 4 root root 4096 Oct 4 2019 FFF d---------+ 6 root root 4096 Oct 21 2019 GGG d---------+ 19 root root 4096 Jun 5 2019 HHH drwxrwxrwx 4 root root 4096 Oct 16 09:48 @spool -rw------- 1 root root 716275 Oct 7 17:12 @SYNO.Core.Exter.core.gz drwx------ 3 root users 4096 Aug 12 2018 @SynoDrive -rw------- 1 root root 974848 Oct 2 02:24 @synologrotated.core drwxr-xr-x 3 root root 4096 Jul 23 2019 @SynologyApplicationService drwxr-xr-x 3 root root 4096 May 24 2018 @synologydrive drwxr-xr-x 6 root root 4096 May 23 2018 @SynologyDriveShareSync -rw------- 1 root root 5120 Jul 14 2019 synoquota.db d---------+ 7 root root 4096 Mar 12 2020 JJJJ d?????????? ? ? ? ? ? @tmp d---------+ 11 root root 4096 Dec 2 2019 TMP d---------+ 7 root root 4096 Dec 4 2019 video d---------+ 5 root root 4096 May 25 2018 VirtualBox VMs d---------+ 16 root root 4096 Jul 8 19:01 web Quote Link to comment Share on other sites More sharing options...
billat29 Posted October 19, 2020 Share #8 Posted October 19, 2020 Understand that there is a problem with volume1... but did you reboot after deleting /.xpenoboot? Quote Link to comment Share on other sites More sharing options...
arTii Posted October 19, 2020 Author Share #9 Posted October 19, 2020 No I don't rebuild - how do it? How repair volume1? This is RAID5 volume - /dev/md2 but /opt is too /dev/md2... I'm umount /volume1 and /opt, but if I run fsck.ext4 I'v get repose e2fsck: Cannot continue, aborting. root@DSM-Osmeckiego:/volume1$ mount /dev/md0 on / type ext4 (rw,relatime,journal_checksum,barrier,data=ordered) none on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=2010464k,nr_inodes=502616,mode=755) none on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) none on /proc type proc (rw,nosuid,nodev,noexec,relatime) none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) /tmp on /tmp type tmpfs (rw,relatime) /run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) /dev/shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime) none on /sys/fs/cgroup type tmpfs (rw,relatime,size=4k,mode=755) cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset,release_agent=/run/cgmanager/agents/cgm-release-agent.cpuset,clone_children) cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu,release_agent=/run/cgmanager/agents/cgm-release-agent.cpu) cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct,release_agent=/run/cgmanager/agents/cgm-release-agent.cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory,release_agent=/run/cgmanager/agents/cgm-release-agent.memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices,release_agent=/run/cgmanager/agents/cgm-release-agent.devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer,release_agent=/run/cgmanager/agents/cgm-release-agent.freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio,release_agent=/run/cgmanager/agents/cgm-release-agent.blkio) none on /proc/bus/usb type devtmpfs (rw,nosuid,noexec,relatime,size=2010464k,nr_inodes=502616,mode=755) none on /sys/kernel/debug type debugfs (rw,relatime) securityfs on /sys/kernel/security type securityfs (rw,relatime) /dev/md3 on /volume2 type ext4 (rw,relatime,journal_checksum,synoacl,data=writeback,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group) none on /config type configfs (rw,relatime) /dev/synoboot2 on /tmp/bootmnt type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=fault,iocharset=default,shortname=mixed,flush,errors=remount-ro) none on /proc/fs/nfsd type nfsd (rw,relatime) root@DSM-Osmeckiego:/volume1$ fsck.ext4 /dev/md2 e2fsck 1.42.6 (21-Sep-2012) /dev/md2 is in use. e2fsck: Cannot continue, aborting. Quote Link to comment Share on other sites More sharing options...
billat29 Posted October 19, 2020 Share #10 Posted October 19, 2020 OK. We're talking about two different things here. What I am saying is that if the /.xpenoboot directory is present on 6.2.3, then the system will not come up properly. And we must fix that problem first. As you have found and deleted the directory, then that problem existed and you now need to reboot the box. Once rebooted, DSM might be able to repair the problem. Quote Link to comment Share on other sites More sharing options...
arTii Posted October 19, 2020 Author Share #11 Posted October 19, 2020 I'm reboot server and the direcotory not rebulid Quote Link to comment Share on other sites More sharing options...
billat29 Posted October 19, 2020 Share #12 Posted October 19, 2020 OK. Do any DSM services come up? Obviously ssh is working, But still no access to the desktop? Quote Link to comment Share on other sites More sharing options...
arTii Posted October 19, 2020 Author Share #13 Posted October 19, 2020 Some services works eg ftp, mail, file sharing, ssh but cannot log to the desktop, Quote Link to comment Share on other sites More sharing options...
billat29 Posted October 19, 2020 Share #14 Posted October 19, 2020 I'm still trying to get DSM to come up. I see you have a volume2 and and apparent error on volume1. Pull the drives that make up volume1 from the box and boot it with just volume2. I expect that your applications won't come up as they will be (probably) be installed on volume1 but DSM desktop should as the system partition is copied to all disks. If it doesn't come up at this point, then your problem with DSM has nothing to do with the error on your RAID array. Quote Link to comment Share on other sites More sharing options...
arTii Posted October 19, 2020 Author Share #15 Posted October 19, 2020 OK. I'm disconected disks from volume1, and I can log-in to the DSM desktop. Now I try connect this dosks and repair from portable debian distro Quote Link to comment Share on other sites More sharing options...
arTii Posted October 19, 2020 Author Share #16 Posted October 19, 2020 (edited) After connect disks to the live Debian distro, I run command fsck.ext4 -fyv /dev/md/2 Tool repair my Volume and now I can connect to the desktop Thansk for all Edited October 19, 2020 by arTii 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.