[Trisquel-users] Re : Cannot boot after trying MATE Tweak > Interface > Panels
If you reformat the partition: You will lose the data on it (since that perspective does not seem to bother you, I guess you have a recent backup); The problem should be fixed... ... but not for long (or at all) if the drive is actually defective! You can see the SMART data of the drive. The easiest way is probably: to install the "gnome-disk-utility" package in the live system; to launch "Disks" from the "Control Center"; to click on the disk (in the left panel); to click on "SMART Data & Self-Tests" in the "burger" menu (the three stacked horizontal segments). As the name says, you can test the disk from there too. On GNOME Disks' main window, after clicking on "Partition 5", the button with three gears allows you to "Format Partition...". You would then have to edit accordingly /etc/fstab's line that refers to /home. I mean the file /etc/fstab of the installed system (you can still write on its root filesystem, right?). And you would have to recreate (e.g., with 'mkdir') the home folders of the users, setting the same uid and gid (e.g., with 'chown') as before: they can be respectively read in the third and fourth column of /etc/passwd. Again: I mean the file /etc/passwd of the installed system. Well, that instructive process or reinstalling everything. :-)
[Trisquel-users] Re : Cannot boot after trying MATE Tweak > Interface > Panels
I believe XFS supports all the architectures Linux supports. It is indeed implemented in the kernel. As far as I understand, XFS being 64 bits means it uses 64 bits to address the disk. That allows to have XFS filesystems of size up to 8 exbibytes minus one byte. That is about 8 billions of GiB. :-)
[Trisquel-users] Re : Cannot boot after trying MATE Tweak > Interface > Panels
Yes.
[Trisquel-users] Re : Cannot boot after trying MATE Tweak > Interface > Panels
A priori, the fact you modified the panel layout before the problem occurs is a mere coincidence. Your XFS filesystem to be mounted at /home is corrupted. As the log says, you need to 'umount' it and run 'xfs_repair' on it. If the filesystem is indeed mounted, the following command will tell you the corresponding device: # mount | grep home If that filesystem is /dev/sdaX (where "X" is a number and "a" may actually be another letter if /home is not on the first disk): # umount /home # xfs_repair /dev/sdaX If that is not enough: # xfs_repair -L /dev/sdaX You can also do that from a live system (prefix the commands with "sudo ", without the quotes).