Need to understand why SLES 15 SP3 ext4 filesystem become TYPE=jmicron

kpoobathi@gmail.com · 12-06-2023, 11:07 AM

Hi guys,

We are running with SLES15 SP3 and server didn't comeup post patching .While checking we found the root LVM file system become type=jmicron.any idea what caused this and how to fix permanently .BTW, The root filesystem in not RAID and single LVM disk

#blkid
“/dev/mapper/sysVG-LVRoot: TYPE="jmicron_raid_member"”

syg00 · 12-06-2023, 08:20 PM

Do you use "auto" in the fstab entry ?. If so change it to the true f/s type and see how that goes.

I see several hits on the web, and it seems it's because of weak testing code in libblkid. Surprised it hasn't been fixed, because it's been reported for over a decade.

kpoobathi@gmail.com · 12-07-2023, 09:46 AM

Quote:

Originally Posted by syg00

Do you use "auto" in the fstab entry ?. If so change it to the true f/s type and see how that goes.

I see several hits on the web, and it seems it's because of weak testing code in libblkid. Surprised it hasn't been fixed, because it's been reported for over a decade.

####

Hey , thanks,
its not configured with auto and we have mentioned with filesystem

# cat /etc/fstab
/dev/sysVG/LVRoot / ext4 acl 0 2

I am able to fix by updating filesystem type in grub as a workaround .This is started getting reported recently and you mean its caused because of recent upgrade related to libblkid?

lvm_ · 12-07-2023, 10:04 AM

It could be an annoying dm-raid issue: if it detects a valid raid superblock in root device it takes precedence over everything else, and the system won't boot. If you have dm-raid loaded and don't need it, remove it, otherwise google where this jmicron raid stores its superblock and try zeroing it. Having LVM adds extra bit of fun to this process, no idea why modern distros insists on stuffing it everywhere.