Add system image failed

Hi there!
I’m trying to update rolling release, but it it’s failed:

    wins@vyos:~$ show ver
    Version:          VyOS 1.2-rolling-201908171224
    Built by:         autobuild@vyos.net
    Built on:         Sat 17 Aug 2019 12:24 UTC
    Build UUID:       0ef539be-8d54-4dc6-bbfd-78e09f8e6ab3
    Build Commit ID:  204e0cb825de1d

    Architecture:     x86_64
    Boot via:         installed image
    System type:      bare metal

    Hardware vendor:  Dell Inc.
    Hardware model:   PowerEdge R210 II
    Installing "1.2-rolling-201908310337" image.
    Copying new release files...
    Error trying to mount a partition/directory.
    Please see /tmp/install-9270.log for details

Log file:

Error trying to mount a partition/directory.
mount -t overlay -o noatime,upperdir=/boot/1.2-rolling-201908310337/rw,lowerdir=/mnt/squashfs,workdir=/boot/1.2-rolling-201908310337/work overlay /mnt/inst_root
mount: wrong fs type, bad option, bad superblock on overlay,
       missing codepage or helper program, or other error

Hello @wins, I can’t reproduce issue with update and on old rolling versions, can you provide more information.
show disk sda format
sudo dmesg | grep sda
and
sudo df -lah

Yep.

wins@vyos:~$ show disk sda format

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: 487492FF-F20B-489E-A3B2-79D02CD1F93C

Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 526335 524288 256M EFI System
/dev/sda3 526336 976773134 976246799 465.5G Linux filesystem

wins@vyos:~ sudo dmesg | grep sda [ 1.784727] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 1.784736] sd 0:0:0:0: [sda] Write Protect is off [ 1.784738] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.784748] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.830049] sda: sda1 sda2 sda3 [ 1.830625] sd 0:0:0:0: [sda] Attached SCSI disk [ 7.202700] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 12.691204] EXT4-fs (sda3): re-mounted. Opts: (null) wins@vyos:~ sudo df -lah
Filesystem Size Used Avail Use% Mounted on
sysfs 0 0 0 - /sys
proc 0 0 0 - /proc
tmpfs 787M 82M 706M 11% /run
/dev/sda3 459G 476M 435G 1% /lib/live/mount/persistence
/dev/loop0 370M 370M 0 100% /lib/live/mount/rootfs/1.2-rolling-201908171224.squashfs
tmpfs 2.0G 0 2.0G 0% /lib/live/mount/overlay
overlay 2.0G 178M 1.8G 10% /
devtmpfs 10M 0 10M 0% /dev
securityfs 0 0 0 - /sys/kernel/security
tmpfs 2.0G 0 2.0G 0% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/cpuset
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/blkio
cgroup 0 0 0 - /sys/fs/cgroup/memory
cgroup 0 0 0 - /sys/fs/cgroup/devices
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/net_cls,net_prio
cgroup 0 0 0 - /sys/fs/cgroup/perf_event
cgroup 0 0 0 - /sys/fs/cgroup/hugetlb
cgroup 0 0 0 - /sys/fs/cgroup/pids
systemd-1 0 0 0 - /proc/sys/fs/binfmt_misc
debugfs 0 0 0 - /sys/kernel/debug
hugetlbfs 0 0 0 - /dev/hugepages
mqueue 0 0 0 - /dev/mqueue
tmpfs 2.0G 20K 2.0G 1% /tmp
fusectl 0 0 0 - /sys/fs/fuse/connections
none 2.0G 76K 2.0G 1% /opt/vyatta/config

and this one (from dmesg):

[1188561.669553] ISO 9660 Extensions: Microsoft Joliet Level 3
[1188561.674433] ISO 9660 Extensions: RRIP_1991A
[1188567.100778] overlayfs: filesystem on '/boot/1.2-rolling-201908310337/rw' not supported as upperdir
[1188982.527455] ISO 9660 Extensions: Microsoft Joliet Level 3
[1188982.527504] ISO 9660 Extensions: RRIP_1991A
[1188987.321587] overlayfs: filesystem on '/boot/1.2-rolling-201908310337/rw' not supported as upperdir
[1190232.620481] ISO 9660 Extensions: Microsoft Joliet Level 3
[1190232.620530] ISO 9660 Extensions: RRIP_1991A
[1190235.636200] overlayfs: filesystem on '/boot/1.2-rolling-201908310337/rw' not supported as upperdir

So, I can’t reproduce this issue, can you show me full update process? Begin command:
add system image https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201908310337-amd64.iso

wins@vyos:~$  add system image https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201909041703-amd64.iso
Trying to fetch ISO file from https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201909041703-amd64.iso
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  408M  100  408M    0     0  1468k      0  0:04:44  0:04:44 --:--:-- 1504k
ISO download succeeded.
Checking for digital signature file...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (22) The requested URL returned error: 404 Not Found
Unable to fetch digital signature file.
Do you want to continue without signature check? (yes/no) [yes] 
Checking MD5 checksums of files on the ISO image...OK.
Done!
What would you like to name this image? [1.2-rolling-201909041703]: 
OK.  This image will be named: 1.2-rolling-201909041703
Installing "1.2-rolling-201909041703" image.
Copying new release files...
Error trying to mount a partition/directory.
Please see /tmp/install-6535.log for details.
Failed to set up root directory for postinst

@wins do you have another bootable versions VyOS for updating on this router?

No.
wins@vyos:~$ show system image
The system currently has the following image(s) installed:

1: gatekeeper (default boot)

I can provide admin-access to this router (there is only testing enviroment) if nessesary.

If it possible, I want to see this issue, because I can’t reproduce its. I wrote mail to you

Hi @wins, did you have successfully updated system after reinstallation?

Changing boot mode from uefi to bios solves problem.
Probably vendor-specific bug.
@Dmitry thanks a lot

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.