Re: Unbootable system after fresh install on Sun Ultra 45 workstation
Blacklisting that module did indeed fix the issue and the system booted.
Not sure what the ideal fix would be for this. I suspect this should
affect other machines lacking that instructions, and not only this
ultra45.
[]s,
Marcelo
On Mon, May 19, 2025 at 5:59 PM John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
>
> Hello Marcelo,
>
> On Mon, 2025-05-19 at 17:50 +0200, Marcelo Bezerra wrote:
> > As follow up:
> >
> > Just booted the installation cd and mounted the disk, chrooted and
> > started ssh so I could more easily copy and paste :)
> >
> > mosca@ultra45:~$ cat /etc/fstab
> > # /etc/fstab: static file system information.
> > #
> > # Use 'blkid' to print the universally unique identifier for a
> > # device; this may be used with UUID= as a more robust way to name devices
> > # that works even if disks are added and removed. See fstab(5).
> > #
> > # systemd generates mount units based on this file, see systemd.mount(5).
> > # Please run 'systemctl daemon-reload' after making changes here.
> > #
> > # <file system> <mount point> <type> <options> <dump> <pass>
> > # / was on /dev/sdb2 during installation
> > UUID=25f72af7-ea5d-484b-859c-6724ed3382bc / ext4
> > errors=remount-ro 0 1
> > # /boot was on /dev/sdb1 during installation
> > UUID=40e43524-0383-4da1-bb08-ae3a10a6114e /boot ext2
> > defaults 0 2
> > # swap was on /dev/sdb4 during installation
> > UUID=de638666-5dc6-4869-bcdc-014907d38a8b none swap sw
> > 0 0
> > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
>
> OK, this looks good. What does the kernel command line say?
>
> > mosca@ultra45:~$ lsmod
> > Module Size Used by
> > ext4 794624 2
> > crc16 24576 1 ext4
> > mbcache 24576 1 ext4
> > jbd2 122880 1 ext4
> > crc32c_generic 24576 3 <== this is the correct module that
> > should be used, fresh install tries to use crc32c which fails, due to
> > lack of crc32c opcodes in this older cpu.
>
> The question is whether this is related to the failure you are seeing and
> I am not sure about this. It seems that there were some changes to ext4
> with regards to crc32c [1].
>
> If this is actually the problem, we need to figure out why the wrong module
> is loaded on your machine. I don't have an answer to that from the top of
> my head.
>
> You can try blacklisting the crc32c_sparc64 module from the kernel command line.
>
> Adrian
>
> > [1] https://patchwork.kernel.org/project/linux-mips/patch/20241103223154.136127-16-ebiggers@kernel.org/
>
> --
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer
> `. `' Physicist
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: