Topics

Hi,

i'm getting a lot of UFS2 superblock failed errors when booting the opnsense (OPNsense 23.7.1_3-amd64), is this a dying ssd?
A reboot to singleuser and a fsck and this disk gives the same errors but a clean at the end.

2023-08-15T07:33:34   Notice   kernel   Root mount waiting for: CAM
2023-08-15T07:33:34   Notice   kernel   ada0 at ata0 bus 0 scbus0 target 0 lun 0   
2023-08-15T07:33:34   Notice   kernel   ada0: <Hoodisk SSD SBFM61.3> ACS-4 ATA SATA 3.x device   
2023-08-15T07:33:34   Notice   kernel   ada0: Serial Number KBTMCGC41234867   
2023-08-15T07:33:34   Notice   kernel   ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)   
2023-08-15T07:33:34   Notice   kernel   ada0: 244198MB (500118192 512 byte sectors)   
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_sblockloc (0) != SBLOCK_UFS2 (0x10000)   
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_nindir (353637138) != fs->fs_bsize / sizeof(ufs2_daddr_t) (136841191)   
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_inopb (421009174) != fs->fs_bsize / sizeof(struct ufs2_dinode) (4276287)   
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_bsize (1094729534) > MAXBSIZE (65536)   
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: powerof2(fs->fs_bsize) (0) == 0 (0)   
(...)
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_fragshift (1600019804) != ILOG2(fs->fs_frag) (-1)
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_fsbtodb (1667391840) != ILOG2(fs->fs_fsize / sectorsize) (21)   
2023-08-15T07:33:34   Notice   kernel   UFS2 superblock failed: fs->fs_old_cgoffset * (~fs->fs_old_cgmask) (0) > fs->fs_fpg (-2021227132)   
2023-08-15T07:33:34   Notice   kernel   <118>** /dev/gpt/rootfs
2023-08-15T07:33:34   Notice   kernel   <118>FILE SYSTEM CLEAN; SKIPPING CHECKS   

I'm getting those errors on the system log


2020-11-11T21:15:30   RA with a lower CurHopLimit sent from fe80:2::1 on em1 (current = 255, received = 64). Ignored.
2020-11-11T21:15:21   RA with a lower CurHopLimit sent from fe80:2::1 on em1 (current = 255, received = 64). Ignored.
2020-11-11T21:15:12   RA with a lower CurHopLimit sent from fe80:2::1 on em1 (current = 255, received = 64). Ignored.

On the server side IPv6 is working without a problem, but no client can connect to IPv6 sites nor does get an IPv6 address.

System is connected to a bridge modem via vodafone business cable.
Only one WAN interface and one LAN interface (nothing fancy)