apt full-upgrade causes system lock-up

[Colin Law]

On Fri, 3 Jun 2022 at 16:08, Bo Berglund <bo.berglund at gmail.com> wrote:
>
> $ df -xsquashfs
> Filesystem                    1K-blocks       Used Available Use% Mounted on
> udev                            8068468          0   8068468   0% /dev
> /dev/nvme0n1p5                 24754404   10399680  13027620  45% /
> /dev/nvme0n1p1                   523248          4    523244   1% /boot/efi
> /dev/nvme0n1p6                 76830988   33592528  39289968  47% /home
> /dev/sda1                    1953513468 1494870368 458643100  77% /mnt/auriga
> //192.168.119.216/video       271380924  184301560  87079364  68% /mnt/smb
> 192.168.119.216:/media/video  271381504  170443776  87079936  67% /mnt/video

That looks ok, I wanted to check that the drive it mentioned as being
set to read only is the one you think it is.

I noticed this from the SMART data earlier
Power Cycles:                       335
Power On Hours:                     13 259
Unsafe Shutdowns:                   209

If I understand correctly (which I may not) that says that it has been
powered on for a total of 550 days and has been power cycled 335
times, of which 209 were unsafe shutdowns.  If an unsafe shutdown is,
for example, a power fail then that seems a bit odd.  It might be
worth watching that for a while and seeing if you can confirm what
those numbers mean for your drive.

I believe you still need to look in syslog to find why the drive went
read only.  You might be able to find that by searching for the
/dev/nvme0

Colin