apt full-upgrade causes system lock-up

[Aaron Rainbolt]

On Thu, Jun 2, 2022 at 5:23 PM Bo Berglund <bo.berglund at gmail.com> wrote:
>
> On Thu, 2 Jun 2022 22:32:56 +0100, Colin Law <clanlaw at gmail.com> wrote:
>
> >Maybe start with Google or your favourite search engine.
>
> I did but I still do not understand exactly what you are suggesting...
> This is what I read:
> https://linuxconfig.org/how-to-check-an-hard-drive-health-from-the-command-line-using-smartctl
>
> After first installing smartmontools (it was not on my system, by default):
>
> $ sudo smartctl -a /dev/nvme0n1p5
> smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-113-generic] (local build)
> Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Number:                       KINGSTON SA2000M8500G
> Serial Number:                      50026B76838C83AF
> Firmware Version:                   S5Z42105
> PCI Vendor/Subsystem ID:            0x2646
> IEEE OUI Identifier:                0x0026b7
> Controller ID:                      1
> Number of Namespaces:               1
> Namespace 1 Size/Capacity:          500 107 862 016 [500 GB]
> Namespace 1 Utilization:            94 197 727 232 [94,1 GB]
> Namespace 1 Formatted LBA Size:     512
> Namespace 1 IEEE EUI-64:            0026b7 6838c83af5
> Local Time is:                      Fri Jun  3 00:06:22 2022 CEST
> Firmware Updates (0x14):            2 Slots, no Reset required
> Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
> Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
> Timestmp
> Maximum Data Transfer Size:         32 Pages
> Warning  Comp. Temp. Threshold:     75 Celsius
> Critical Comp. Temp. Threshold:     80 Celsius
>
> Supported Power States
> St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
>  0 +     9.00W       -        -    0  0  0  0        0       0
>  1 +     4.60W       -        -    1  1  1  1        0       0
>  2 +     3.80W       -        -    2  2  2  2        0       0
>  3 -   0.0450W       -        -    3  3  3  3     2000    2000
>  4 -   0.0040W       -        -    4  4  4  4    15000   15000
>
> Supported LBA Sizes (NSID 0x1)
> Id Fmt  Data  Metadt  Rel_Perf
>  0 +     512       0         0
>
> === START OF SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> SMART/Health Information (NVMe Log 0x02)
> Critical Warning:                   0x00
> Temperature:                        29 Celsius
> Available Spare:                    100%
> Available Spare Threshold:          10%
> Percentage Used:                    85%
> Data Units Read:                    677 087 673 [346 TB]
> Data Units Written:                 787 090 186 [402 TB]
> Host Read Commands:                 3 519 404 577
> Host Write Commands:                3 571 281 634
> Controller Busy Time:               84 375
> Power Cycles:                       335
> Power On Hours:                     13 259
> Unsafe Shutdowns:                   209
> Media and Data Integrity Errors:    0
> Error Information Log Entries:      0
> Warning  Comp. Temperature Time:    0
> Critical Comp. Temperature Time:    0
> Thermal Temp. 1 Transition Count:   29
> Thermal Temp. 1 Total Time:         33
>
> Error Information (NVMe Log 0x01, max 256 entries)
> No Errors Logged
>
>
> What can be gleaned from this?
> No Errors at least....
>
> So by suggestion from the page I found:
>
> sudo smartctl -t short /dev/nvme0n1p5
> smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-113-generic] (local build)
> Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
> NVMe device successfully opened
> Use 'smartctl -a' (or '-x') to print SMART (and more) information
>
>
> Here the output grossly deviates from what is shown on the page I am reading...
>
> It is supposed to output a timeout until I can view the test result, but what I
> show above is all I am getting.
>
> So I am none the wiser....

Do "sudo smartctl -x". That will show copious amounts of drive info
that can help debug what's going wrong.

However, just from the data I see here, I'm even more led to believe
this is drive failure. Judging from your drive model and your data
written, your drive is supposed to sustain 300 terabytes written.
You've done 402 TB, so that drive isn't just past warranty, it's
probably just shy of fried, if not fried already. That would explain
the read-only state - the drive is likely about to die, and is trying
to preserve the data that's left before you lose it.