Was required elsewhere
Back and located my openSUSE-Live to boot up so could read or post here a bit easier.
At least twice previously similar problems, on those occasions thought was snapper records filled the partition, so re-installed, what see appears not that, also like find better solution.
Start of boot seems normal, until select either latest or previous kernel/boot settings, then end up in terminal, failing, so use **journalctl -xd **<Enter> this appears enable READ only mode, with other text every now and then appearing on screen as well as what typed.
Can mount old /home no problem, see the 455 GB partition on Files.
Q: How to mount sda3 root / to view log files etc there ?
Else try re-boot to see if attempt to rollback worked.
in BOLD the partition root /
linux:~ # gdisk /dev/sda
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 976764911 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3A6AAD46-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976764877
Partitions will be aligned on 2048-sector boundaries
Total free space is 4012 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 primary
2 4096 4225023 2.0 GiB 0700 primary
** 3 4225024 88117247 40.0 GiB EF00 **
4 88117248 976762879 423.7 GiB 0700 primary
Command (? for help): q
linux:~ #
Use e2fsck to check sda3 the / for partition errors, is result another problem ?
linux:~ # e2fsck -v /dev/sda3
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda3
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
linux:~ #
Use e2fsck to check sda4 the /home for partition errors, is result another problem ?
linux:~ # e2fsck -v /dev/sda4
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda4
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
linux:~ #
.