Jump to content
XPEnology Community

hectoruelo

Rookie
  • Posts

    3
  • Joined

  • Last visited

Posts posted by hectoruelo

  1. Hi.

    Yesterday something strange happened to me on the NAS.

    Suddenly and without warning when I wanted to access the graphic interface appeared the attached message.

     

    My settings :

     

    VMware virtualitation .

    DS3615xs 6.1 Jun's Mod V1.02b

    Raid1 SATA (1TB virtual disc - 1TB fisical disc)

    Basic SATA (3TB fisical disc)

    DSM_DS3617xs_15284.

     

    I accessed the NAS via ssh and saw that all the SATA disks of the virtual machine are dismounted and that the fstab file was incomplete.

     

    Could not chdir to home directory /var/services/homes/hectoruelo: No such file or directory
    hectoruelo@synology:/$ df
    Filesystem     1K-blocks    Used Available Use% Mounted on
    /dev/md0         2385528 1032624   1234120  46% /
    none             1009792       0   1009792   0% /dev
    /tmp             1015088     472   1014616   1% /tmp
    /run             1015088    3868   1011220   1% /run
    /dev/shm         1015088       4   1015084   1% /dev/shm
    none                   4       0         4   0% /sys/fs/cgroup
    cgmfs                100       0       100   0% /run/cgmanager/fs

    hectoruelo@synology:/$ sudo fdisk -l
    Password:
    Disk /dev/sdb: 935.5 GiB, 1004485476352 bytes, 1961885696 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x7317beff

    Device     Boot   Start        End    Sectors   Size Id Type
    /dev/sdb1          2048    4982527    4980480   2.4G fd Linux raid autodetect
    /dev/sdb2       4982528    9176831    4194304     2G fd Linux raid autodetect
    /dev/sdb3       9437184 1961680895 1952243712 930.9G fd Linux raid autodetect


    Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 857092B8-E55D-4B2D-8D9E-31085917FAA3

    Device       Start        End    Sectors  Size Type
    /dev/sdc1     2048    4982527    4980480  2.4G Linux RAID
    /dev/sdc2  4982528    9176831    4194304    2G Linux RAID
    /dev/sdc3  9437184 5860328351 5850891168  2.7T Linux RAID


    Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x6186e130

    Device     Boot   Start        End    Sectors   Size Id Type
    /dev/sdd1          2048    4982527    4980480   2.4G fd Linux raid autodetect
    /dev/sdd2       4982528    9176831    4194304     2G fd Linux raid autodetect
    /dev/sdd3       9437184 1953320351 1943883168 926.9G fd Linux raid autodetect


    Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/zram0: 595 MiB, 623902720 bytes, 152320 sectors
    Units: sectors of 1 * 4096 = 4096 bytes
    Sector size (logical/physical): 4096 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes


    Disk /dev/zram1: 595 MiB, 623902720 bytes, 152320 sectors
    Units: sectors of 1 * 4096 = 4096 bytes
    Sector size (logical/physical): 4096 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    hectoruelo@synology:/$ sudo cat /etc/fstab
    none /proc proc defaults 0 0
    /dev/root / ext4 defaults 1 1


    hectoruelo@synology:/$ sudo mount -a /dev/sdd
    hectoruelo@synology:/$ sudo mount -a /dev/sdb
    hectoruelo@synology:/$ sudo mount -a /dev/sdc


    hectoruelo@synology:/$ df .
    Filesystem     1K-blocks    Used Available Use% Mounted on
    /dev/md0         2385528 1032628   1234116  46% /
    hectoruelo@synology:/$ df
    Filesystem     1K-blocks    Used Available Use% Mounted on
    /dev/md0         2385528 1032628   1234116  46% /
    none             1009792       0   1009792   0% /dev
    /tmp             1015088     472   1014616   1% /tmp
    /run             1015088    3872   1011216   1% /run
    /dev/shm         1015088       4   1015084   1% /dev/shm
    none                   4       0         4   0% /sys/fs/cgroup
    cgmfs                100       0       100   0% /run/cgmanager/fs

     

    I have done the test of connecting a new SATA virtual disk with the same result.

    I have manually modified the fstab but when restarting the NAS it is deleted, can someone help me to mount the discs again?

    Thanks in advance.

     

    Sin título.png

  2. On 23/6/2018 at 10:20 PM, Trakon said:

    Hey,

     

    just made the same mistake (Baremetal installation).

     

    Got my Synology up and running again with the 1.03a2 loader from jun > Download here <

    I'm not happy with the required migration (DS3615xs -> DS918+) but with only 4 disks everything worked out fine for me.

     

    Best regards,

    Trakon

     

     

    Hi.

    There is something that is driving me crazy.

    I use xpenology in a virtual machine with vmware.

    Additionally I use acronies true image to make incremental backups of the directory where I have the virtual machine and the disk volumes.

    Well, I have restored the files to before updating to DSM 6.2 and my box is still bricked .

    Does anyone understand it? I am afraid of losing my data, I have information from 15 years ago in them ...

    I'm going to install the DSM 6.2 with the 1.03a2 loader that says Trakon, then I'll add the disks to the virtual machine and I hope the files are still there ... I'm scared.

    Greetings and thank you .

×
×
  • Create New...