Wondering if anyone has any insight on some errors I'm seeing. I have converted a SX6012 and upgraded it nearly all the way per the 1.12 guide but I'm having trouble with 3.6.8010. 3.6.5000 works just fine. When booting 3.6.8010 I see errors when mount and fsck try to use /lib/libblkid.so.1:
Code:
Starting udev: mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
[ OK ]
Setting clock (utc): Wed Jan 1 18:38:54 UTC 2025 [ OK ]
Setting hostname localhost: [ OK ]
Checking filesystems
fsck: /lib/libblkid.so.1: no version information available (required by fsck)
fsck: /lib/libblkid.so.1: no version information available (required by fsck)
fsck: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
fsck: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
fsck: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
Checking all file systems.
[ OK ]
Remounting root filesystem in read-write mode: mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
[ OK ]
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
Mounting local filesystems: mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
mount: /lib/libblkid.so.1: no version information available (required by /lib/libmount.so.1)
[ OK ]
There are also a couple other errors that I would expect are caused by missing files because filesystems are not getting mounted:
Code:
Running firstboot script error reading information on service arp_responder: No such file or directory
...
file /opt/tms/customization_files/customization.6012 does not exists - safely using default values
I do see mention of this earlier in the thread, but in one place the response was that reinstalling 8010 fixed the problem, and in another that someone had copied kernel and related files
out? of the u-boot storage. A third seemed to be related to trying to go directly to 8010 during the manufacturing stage:
I've followed the 1.12 version of the guide that's posted earlier in the thread as a Google Doc, and up to this point it's almost been too easy. I deviated by using my already existing FreeBSD based TFTPD and web servers, and only upgrading one partition to a new image version before making that partition active, rebooting and then installing the next image version to the newly inactive partiion - I believe this is in keeping with the intent of having two different partitions - to be able to fall back to a good version - and it seems to have paid off here.
Here is the current "show images" output with it booted to 8010 and with those errors in the console:
Code:
sx6012 [standalone: master] # show images
Installed images:
Partition 1:
version: PPC_M460EX 3.6.8010 2018-08-20 18:04:16 ppc
Partition 2:
version: PPC_M460EX 3.6.5000 2017-11-10 18:14:29 ppc
Last boot partition: 1
Next boot partition: 1
Images available to be installed:
1:
Image : image-PPC_M460EX-3.6.8010.img
Version: PPC_M460EX 3.6.8010 2018-08-20 18:04:16 ppc
Serve image files via HTTP/HTTPS: no
No image install currently in progress.
No boot manager password is set.
Image signing : trusted signature always required
Admin require signed images: yes
Settings for next boot only:
Fallback reboot on configuration failure: yes (default)
The only thing I notice that seems a little off is the "/" filesystem seems very full, is this normal? When running the 3.6.5000 image:
Code:
[admin@sx6012 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mtdblock7 512M 500M 13M 98% /
/dev/mtdblock8 100M 3.7M 97M 4% /config
/dev/mtdblock9 860M 392M 469M 46% /var
tmpfs 1014M 6.5M 1008M 1% /dev/shm
tmpfs 64M 8.6M 56M 14% /vtmp
When running 3.6.8010:
Code:
[admin@sx6012 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mtdblock6 512M 481M 32M 94% /
/dev/mtdblock8 100M 3.7M 97M 4% /config
/dev/mtdblock9 860M 390M 471M 46% /var
tmpfs 1014M 6.6M 1008M 1% /dev/shm
tmpfs 64M 9.4M 55M 15% /vtmp
The web interface seems to be running fine in 8010, but did move from http to https with the 8010 upgrade. I'm wondering if this is just a problem with 8010 and it would be fixed with 8012, but I hate to clobber the known good 3.6.5000 partition to try, and I'm not sure if I can go directly to 3.6.8012 from 3.6.5000.
Anyone have any insight? Is this some kind of problem with the kernel not matching the user space utilities and there's some additional manual step I need to take?
