munchgeil1

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

1 Neutral

About munchgeil1

  • Rank
    Newbie
  1. Moving everything (apps and associated data) from one volume to another isn't as easy as I thought. Does anyone have experience on how to do it? I currently have data on Volume 1, I created new Volume 3. I would like to move all apps. and associated data from Volume 1 to Volume 3.. Then I would delete Volume 1 (since both Volume 1 and 3 and or the same SSD, and I need the space). I have 30 installed apps, and some of them do, but most do NOT allow changing "target volume". Deinstalling, reinstalling and reconfiguring would take just too much time. Is there an easier way?
  2. Hi again, Well, I hit the max size again, and wanted to follow the same method to extend the volume via terminal , just like last time. However, I ran into a problem this time and I cannot go around it. The problem is at Step 3 and 4 -> more actually at setp 4 Step 3: When i SSH as "admin" user, then switch to root (sudo -i), then run syno_poweroff_task -d the connection to the server is closed (eventough -d is used) When i SSH as "admin" user, then run syno_poweroff_task -d the command executes correctly (Success) So I proceed to step 4 as "admin" user Step 4: Running sudo mdadm --stop /dev/md2 produces error: mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume group? When I run sudo umount /dev/md2 I get target is busy When I run vgdisplay, I can see all Volume group details When I run cat /proc/mounts, I can see the volume group and volume still mounted! How can i get past this error? If this is not workable, then I'll try adding new datastore, and moving everything to that datastore.
  3. How can I make wi-fi/bluetooth adapter available for synology?... I have ESXI 6.5 U2 installed bare-metal on Motherboard with: Intel Gigabit Ethernet ( Intel® I219V) Integrated 2x2 802.11ac Wi-Fi with MU-MIMO support. In ESXI 6.5, I can see Physical adapter " vmnic0 , 1000 Mbps, Full" In VM setting, I added: E1000e If I want to add new Network Adapter, I have following adapter types: E1000 E1000e VMXNET 3 In Synology, I can connect to internet without problem, but wi-fi and bluetooth are not available. Why is that? Is problem: BIOS? (I have latest BIOS setting, but not sure if I ever explicitly enabled wifi/bluetooth) ESXI 6.5 U2 Jun's Loader Synology itself? Thank you!
  4. For those who want to use Synology DSM to "expand" Volume in DSM, and do not want to use Terminal: In ESXi, build a new VMDK (to existing Xpenology VM): Add New HDD Use existing SATA controller (tied to HDD, where Synology data is being stored), but a different bus node. For example, if existing HDD is using 1:0, the new HDD should use 1:1 Log into DSM and open Storage Manager app Create new Storage Group Create new Volume within that storage group Copy all items from existing (e.g. Volume 1) to new volume (Volume 2): Copy data from Shared folders Some apps, require to be opened and “new storage” to be specified within the app itself: Example: MariaDB May need to re-install some apps into new volume(stated by some on Synology forums Go back to Storage Manager Delete the original Volume and associated Storage Group. In ESXi, delete the old VMDK.
  5. Update: I rebooted Xpenology and I can log in normally into DSM. Nothing is missing. everything looks normal. I stopped docker within DSM. I SSH back into Synology via terminal and when I run command "df" the array looks normal. I see volume is ok when mounted, and unmounted. I see sdb3 and md2 are correctly expanded. So I think everything is normal...I just cannot expand Volume group and logical volume... 😞 With Volume mounted: root@Syno:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1016796 1249948 45% / none 2013752 0 2013752 0% /dev /tmp 2027544 612 2026932 1% /tmp /run 2027544 3136 2024408 1% /run /dev/shm 2027544 12 2027532 1% /dev/shm none 4 0 4 0% /sys/fs/cgroup cgmfs 100 0 100 0% /run/cgmanager/fs /dev/vg1/volume_1 11621336 8114668 3387884 71% /volume1 Volume Unmounted: root@Syno:~# sudo syno_poweroff_task -d Unknown format [ pre-stop process 20270 ], parse failed root@Syno:~# sudo syno_poweroff_task -d root@Syno:~# df | fgrep volume1 root@Syno:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1016028 1250716 45% / none 2013752 0 2013752 0% /dev /tmp 2027544 604 2026940 1% /tmp /run 2027544 2392 2025152 1% /run /dev/shm 2027544 12 2027532 1% /dev/shm none 4 0 4 0% /sys/fs/cgroup cgmfs 100 0 100 0% /run/cgmanager/fs And I can see that sdb3 and md2 are correctly expanded: root@Syno:~# fdisk -l Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 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: 0xf8c48628 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 41943039 32505856 15.5G 83 Linux 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: 594 MiB, 622854144 bytes, 152064 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: 594 MiB, 622854144 bytes, 152064 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/zram2: 594 MiB, 622854144 bytes, 152064 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/zram3: 594 MiB, 622854144 bytes, 152064 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/md2: 15.5 GiB, 16641949696 bytes, 32503808 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 and cat /proc/mdstat shows this: root@Syno:~# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md2 : active raid1 sdb3[0] 16251904 blocks super 1.2 [1/1] md1 : active raid1 sdb2[0] 2097088 blocks [12/1] [U___________] md0 : active raid1 sdb1[0] 2490176 blocks [12/1] [U___________] unused devices: <none> But the Volume group is NOT explanded: root@Syno:~# vgdisplay --- Volume group --- VG Name vg1 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 11.40 GiB PE Size 4.00 MiB Total PE 2918 Alloc PE / Size 2918 / 11.40 GiB Free PE / Size 0 / 0 VG UUID f8NayU-uRhd-Yo2G-XcEC-8I4A-H0C3-kidAwF
  6. I went with terminal route....and have issue. I successfully went through step 5, then tried lvextend (hyperlink) and couldn't proceed: error stated " Device /dev/sdb3 not found (or ignored by filtering) see below code....but bottom line. I noticed you said "/dev/sdb3 -> /dev/md2 -> /dev/vg1 -> filesystem" so I tried to expand md2 first,...and it worked (see fdisk -l)....then I tried again "lvextend" and got the same error: Device /dev/sdb3 not found (or ignored by filtering) Then I ran "df" and noticed that in addition to volume_1 I see other volumes,...because of "docker" app that was installed within synology.... I think array is corrupt.... See full code below. Is there anyway out of this, or should I just recreate VM or even reinstall Xpenology? (Before making changes, I exported entire VM, using "Export as OVF template" function in ESXI (Left checkbox next to VM, then in menu "Export as OVF template"...into following files: disk-0.vmdk, disk-1.vmdk, Xpeno6.2.ovf -> I don't know how/where to put them back into ESXI however) Here is the terminal code: (I made mistake on fdisk, but stopped in time) START OF TERMINAL CODE******** admins-iMac:~ admin$ ssh adminsyno@192.168.1.123 adminsyno@192.168.1.123's password: adminsyno@Syno:~$ df|fgrep volume1 /dev/vg1/volume_1 11621336 8114632 3387920 71% /volume1 adminsyno@Syno:~$ sudo mdadm --detail /dev/md2 | fgrep /dev/ Password: /dev/md2: 0 8 19 0 active sync /dev/sdb3 adminsyno@Syno:~$ cd / adminsyno@Syno:/$ sudo syno_poweroff_task -d adminsyno@Syno:/$ df|fgrep volume1 adminsyno@Syno:/$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1009088 1257656 45% / none 2013752 0 2013752 0% /dev /tmp 2027544 592 2026952 1% /tmp /run 2027544 2392 2025152 1% /run /dev/shm 2027544 12 2027532 1% /dev/shm none 4 0 4 0% /sys/fs/cgroup cgmfs 100 0 100 0% /run/cgmanager/fs adminsyno@Syno:/$ sudo mdadm --detail /dev/md2 | fgrep /dev/ /dev/md2: 0 8 19 0 active sync /dev/sdb3 adminsyno@Syno:/$ sudo mdadm --stop /dev/md2 mdadm: stopped /dev/md2 adminsyno@Syno:/$ sudo fdisk /dev/sdb3 Welcome to fdisk (util-linux 2.26.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. /dev/sdb3: device contains a valid 'linux_raid_member' signature; it is strongly recommended to wipe the device with wipefs(8) if this is unexpected, in order to avoid possible collisions Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0xe05944f1. Command (m for help): m Help: DOS (MBR) a toggle a bootable flag b edit nested BSD disklabel c toggle the dos compatibility flag Generic d delete a partition l list known partition types n add a new partition p print the partition table t change a partition type v verify the partition table Misc m print this menu u change display/entry units x extra functionality (experts only) Script I load disk layout from sfdisk script file O dump disk layout to sfdisk script file Save & Exit w write table to disk and exit q quit without saving changes Create a new label g create a new empty GPT partition table G create a new empty SGI (IRIX) partition table o create a new empty DOS partition table s create a new empty Sun partition table Command (m for help): q adminsyno@Syno:/$ sudo fdisk /dev/sdb Password: Welcome to fdisk (util-linux 2.26.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 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: 0xf8c48628 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 33349631 23912448 11.4G fd Linux raid autodetect Command (m for help): d Partition number (1-3, default 3): 3 Partition 3 has been deleted. Command (m for help): n Partition type p primary (2 primary, 0 extended, 2 free) e extended (container for logical partitions) Select (default p): p Partition number (3,4, default 3): 3 First sector (9176832-41943039, default 9177088): 9437184 Last sector, +sectors or +size{K,M,G,T,P} (9437184-41943039, default 41943039): Created a new partition 3 of type 'Linux' and of size 15.5 GiB. Command (m for help): p Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 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: 0xf8c48628 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 41943039 32505856 15.5G 83 Linux Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Re-reading the partition table failed.: Device or resource busy The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8). adminsyno@Syno:/$ lvgdisplay -sh: lvgdisplay: command not found adminsyno@Syno:/$ vgdisplay WARNING: Running as a non-root user. Functionality may be unavailable. /dev/md2: open failed: Permission denied adminsyno@Syno:/$ sudo -i Password: root@Syno:~# lvgdisplay -ash: lvgdisplay: command not found root@Syno:~# vgdisplay root@Syno:~# lvextend /dev/vg1/volume_1 /dev/sdb3 Volume group "vg1" not found root@Syno:~# partprobe -s -ash: partprobe: command not found root@Syno:~# vgdisplay root@Syno:~# sudo shutdown -r now Broadcast message from adminsyno@Syno (/dev/pts/12) at 20:19 ... The system is going down for reboot NOW! root@Syno:~# Connection to 192.168.1.123 closed by remote host. Connection to 192.168.1.123 closed. admins-iMac:~ admin$ ssh adminsyno@192.168.1.123 adminsyno@192.168.1.123's password: adminsyno@Syno:~$ cd / adminsyno@Syno:/$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1010660 1256084 45% / none 2013752 0 2013752 0% /dev /tmp 2027544 584 2026960 1% /tmp /run 2027544 3504 2024040 1% /run /dev/shm 2027544 188 2027356 1% /dev/shm none 4 0 4 0% /sys/fs/cgroup cgmfs 100 0 100 0% /run/cgmanager/fs /dev/vg1/volume_1 11621336 8114640 3387912 71% /volume1 adminsyno@Syno:/$ lvextend /dev/vg1/volume_1 /dev/sdb3 WARNING: Running as a non-root user. Functionality may be unavailable. /var/lock/lvm/V_vg1:aux: open failed: Permission denied Can't get lock for vg1 adminsyno@Syno:/$ sudo -i Password: root@Syno:~# lvextend /dev/vg/volume_1 /dev/sdb3 Volume group "vg" not found root@Syno:~# lvextend /dev/vg1/volume_1 /dev/sdb3 Physical Volume "/dev/sdb3" not found in Volume Group "vg1". root@Syno:~# vgextend vg1 /dev/sdb3 Device /dev/sdb3 not found (or ignored by filtering). Unable to add physical volume '/dev/sdb3' to volume group 'vg1'. root@Syno:~# sudo syno_poweroff_task -d root@Syno:~# lvextend /dev/vg1/volume_1 /dev/sdb3 Physical Volume "/dev/sdb3" not found in Volume Group "vg1". root@Syno:~# fdisk -l Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 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: 0xf8c48628 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 41943039 32505856 15.5G 83 Linux 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: 594 MiB, 622854144 bytes, 152064 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: 594 MiB, 622854144 bytes, 152064 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/zram2: 594 MiB, 622854144 bytes, 152064 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/zram3: 594 MiB, 622854144 bytes, 152064 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/md2: 11.4 GiB, 12242124800 bytes, 23910400 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 root@Syno:~# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md2 : active raid1 sdb3[0] 11955200 blocks super 1.2 [1/1] md1 : active raid1 sdb2[0] 2097088 blocks [12/1] [U___________] md0 : active raid1 sdb1[0] 2490176 blocks [12/1] [U___________] unused devices: <none> root@Syno:~# sudo mdadm --grow /dev/md2 --size=max mdadm: component size of /dev/md2 has been set to 16251904K root@Syno:~# fdisk -l Disk /dev/sdb: 20 GiB, 21474836480 bytes, 41943040 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: 0xf8c48628 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 41943039 32505856 15.5G 83 Linux 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: 594 MiB, 622854144 bytes, 152064 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: 594 MiB, 622854144 bytes, 152064 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/zram2: 594 MiB, 622854144 bytes, 152064 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/zram3: 594 MiB, 622854144 bytes, 152064 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/md2: 15.5 GiB, 16641949696 bytes, 32503808 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 root@Syno:~# vgdisplay --- Volume group --- VG Name vg1 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 11.40 GiB PE Size 4.00 MiB Total PE 2918 Alloc PE / Size 2918 / 11.40 GiB Free PE / Size 0 / 0 VG UUID f8NayU-uRhd-Yo2G-XcEC-8I4A-H0C3-kidAwF root@Syno:~# pvsacn -ash: pvsacn: command not found root@Syno:~# pvscan -ash: pvscan: command not found root@Syno:~# vgextend vg1 /dev/sdb3 Device /dev/sdb3 not found (or ignored by filtering). Unable to add physical volume '/dev/sdb3' to volume group 'vg1'. root@Syno:~# pvcreate /dev/sdb3 Device /dev/sdb3 not found (or ignored by filtering). root@Syno:~# cat/proc/mdstat -ash: cat/proc/mdstat: No such file or directory root@Syno:~# sudo shutdown -r now Broadcast message from adminsyno@Syno (/dev/pts/20) at 21:03 ... The system is going down for reboot NOW! root@Syno:~# Connection to 192.168.1.123 closed by remote host. Connection to 192.168.1.123 closed. admins-iMac:~ admin$ ssh adminsyno@192.168.1.123 adminsyno@192.168.1.123's password: adminsyno@Syno:~$ cd / adminsyno@Syno:/$ ls bin dev etc.defaults lib lib64 mnt root sbin tmp usr var.defaults volume2 config etc initrd lib32 lost+found proc run sys tmpRoot var volume1 volumeSATA1 adminsyno@Syno:/$ sudo -i Password: root@Syno:~# cat/proc/mdstat -ash: cat/proc/mdstat: No such file or directory root@Syno:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1011432 1255312 45% / none 2013752 0 2013752 0% /dev /tmp 2027544 584 2026960 1% /tmp /run 2027544 3516 2024028 1% /run /dev/shm 2027544 188 2027356 1% /dev/shm none 4 0 4 0% /sys/fs/cgroup cgmfs 100 0 100 0% /run/cgmanager/fs /dev/vg1/volume_1 11621336 8114660 3387892 71% /volume1 none 11621336 8114660 3387892 71% /volume1/@docker/aufs/mnt/0b8b66d8e2b10914a6643256da1ea74ab016460a54f05643fc4af4f1be4cd964 shm 65536 0 65536 0% /volume1/@docker/containers/b42390ab0cfc666bdcb983b238c1ad4109e438f9802c0131daa86696e8fe3b38/shm none 11621336 8114660 3387892 71% /volume1/@docker/aufs/mnt/f16c7e6ef763086e5c50c9886229067a2c48ee30e4cbac7f608db994475c0725 shm 65536 0 65536 0% /volume1/@docker/containers/f6d2fcf17ab7404e632944f60531401cbf605603937af131e5f2b3a5a9dc3850/shm none 11621336 8114660 3387892 71% /volume1/@docker/aufs/mnt/c944b65166871552ea9747d5b4ed7fe5b7dc56b9d7fea44a2f09c6d684351650 shm 65536 0 65536 0% /volume1/@docker/containers/6636385e08e6756f28304f4d0a751e5c2d7e5ac807112827d0f77a21066ca225/shm root@Syno:~# df|fgrep volume1 /dev/vg1/volume_1 11621336 8114800 3387752 71% /volume1 none 11621336 8114800 3387752 71% /volume1/@docker/aufs/mnt/0b8b66d8e2b10914a6643256da1ea74ab016460a54f05643fc4af4f1be4cd964 shm 65536 0 65536 0% /volume1/@docker/containers/b42390ab0cfc666bdcb983b238c1ad4109e438f9802c0131daa86696e8fe3b38/shm none 11621336 8114800 3387752 71% /volume1/@docker/aufs/mnt/f16c7e6ef763086e5c50c9886229067a2c48ee30e4cbac7f608db994475c0725 shm 65536 0 65536 0% /volume1/@docker/containers/f6d2fcf17ab7404e632944f60531401cbf605603937af131e5f2b3a5a9dc3850/shm none 11621336 8114800 3387752 71% /volume1/@docker/aufs/mnt/c944b65166871552ea9747d5b4ed7fe5b7dc56b9d7fea44a2f09c6d684351650 shm 65536 0 65536 0% /volume1/@docker/containers/6636385e08e6756f28304f4d0a751e5c2d7e5ac807112827d0f77a21066ca225/shm root@Syno:~# sudo syno_poweroff_task -d root@Syno:~#
  7. Thanks. "fgrep volume1" didn't work (the cursor just went to the second line, and there was no response) so I used "df". I got error at "$ sudo syno_poweroff_task -d" See screen shot. How do I move on?
  8. I have issue in ESXI 6.6 and Xpenology (ds3615xs, with Jun 1.02 loader) I allocated 16GB of HD data when I installed Xpenology on ESXI. I later expanded in ESXI HD from 16 to 20 GB (same HD). In Storage pool on Synology I can see 20 GB, but I cannot increase the size of Volume. See image. Does anyone know how to expand Volume size? Through terminal/SSH maybe?
  9. Hey mandreto10... Hi! You sound very frustrieted! Let me help you. There is lot of information on this forum....It can be confusing for new person. Here is a very good guide: https://xpenology.com/forum/topic/13061-tutorial-install-dsm-62-on-esxi-67/ This guide will work on ESXI 6.5 and 6.7. Make sure you read through the entire post, as there are few important modifications. Specifically changes to Network Card...This link contains all files you need in one place. It has screen shots. The fourth link seems broken. Don't worry about that file. For now, don't go to any other forum site, as it will confuse you. Can you try this and see if it works? If you have any problems, then just write what it is. There is usually a solution. Now to your general questions: For install you must have 3 files: File 1 (aka Jun's bootloader, .IMG file): Jun's loader is one file in .IMG format. The name is often "bootloader.IMG". This file tricks Synology (DSM) into thinking that you are installing DSM on a Synology device, versus your own.This is the most important file to download on this forum! This is the "hack". You MUST edit this IMG file with OSFMount image mounter (Win, free). If you don't have Windows, download and install Windows 10 into VM on ESXI. You can use evaluation version for free. You need to edit IMG file to set the correct Serial Number (SN) and MAC address. SN gives your a Synology a unique identity, and allows you to create an account with Synology, so that you can access your Synology drive over internet. It seems you are well-versed in porting. You can ignore SN. You are right, you will have better speeds and privacy with your own VPN. MAC allows you to find synology drive on your own network, when you type http://http://find.synology.com/ in your browser. You can manually set MAC address (any address really), but you must insure you specify the same address in your VM setting under "Network Setting". If your http://http://find.synology.com doesn not find synology, this is number one reason why this happens. Don't worry about PID and VID. After you edit this file save the changes. File 2 (file .VMDK) This file is what is loads VM and enables to you start installation process. This file brings that black terminal screen when you installed other OS. You can use VMDK file from above link or generate your own using StartWind V2V Image converter (Win, free) from the IMG file you edited above. It doesn't matter. File 3 (PAT file) This file contains synology DSM OS. This file has same perpose to .ISO files used for Windows, Ubunti and other installs! This file is found on sYnology website. For exmaple for the installation link I gave you, the PAT file will be located here: https://www.synology.com/en-global/support/download/DS3615xs#utilities You probably never saw PAT file, because Synology devices install DSM over internet or come pre-installed with it. PAT file is used in cases where your Synology device crashes or something bad happens to it and you have to reinstall the entire DSM. Just like when you have to reinstall your Windows OS. Now to ESXI!... The process for installing DSM is different from that for other OS, but it's very easy. You must use one Harddrive that points to VMDK file this is almost the same as using CD/DVD drive and pointing it to .ISO image, like you did for Windows installation. You must use the second hard drive that will have actual DSM installed, and all your volumes. You can set minimum 16GB and expand as you wish. You can add any number of other drives later (after you install Synology), for additional volumes. For each harddrive you add, you must add a separate SATA controller. There must be one added SATA controller for each harddrive you add. SATA controller is something that helps move data from your harddrive through Virtual Machine into Synology and back. Some users use IDE. I suggest you use SATA. Don't worry about details on SATA, IDE, ISCS...etc. Note: There is no .ISO file for Xpenology/Synology....you only work with .IMG, VMDK and PAT files. SATA drives you specify in VM, will not slow down your NVMe. Your NVMe will work as fast as it should. When booting you may have to choose to boot in Legacy mode versus UEFI mode. Note that this is boot for Virtual MAchine, and not boot for your ESXI server (bare metal boot). In other words, don't worry that Legacy booting in VM will break your ESXI server. (And I hope you boot your ESXI in UEFI mode :-)... Bottom line, lot of things in VM (but not all) will just create some fog or glue to make your Synology work with your hardware, so don't go to much into details. I hope this helps. Ask questions if you have.