rebooting will probably fix, no biggie

Aantheas rebooting will probably fix, no biggie

K

Kyle Gospo•3/24/24, 9:00 PM

not the first time their system has done weird shit though

Aantheas rebooting will probably fix, no biggie

T

tryhardsoccermomswag•3/24/24, 9:00 PM

they've had so many other issues and rebooted only 20 minutes ago

T

tryhardsoccermomswag•3/24/24, 9:00 PM

there's something going on here

K

Kyle Gospo•3/24/24, 9:00 PM

I don't think a reboot is gonna make this go away long term

A

antheasOP•3/24/24, 9:00 PM

check your ssd temps and run a smart test

Ttryhardsoccermomswag have you done anything to your drive?

T

Twin Nature•3/24/24, 9:00 PM

not really, I installed bazzite, added another internal drive, been playing games but some shits being going wrong

T

Twin Nature•3/24/24, 9:02 PM

was able to reboot, it's booting up now

TTwin Nature not really, I installed bazzite, added another internal drive, been playing game...

T

tryhardsoccermomswag•3/24/24, 9:02 PM

when you added the other internal drive, did you setup any automount stuff with it?

T

tryhardsoccermomswag•3/24/24, 9:02 PM

not sure if that would affect what is going on here

T

tryhardsoccermomswag•3/24/24, 9:03 PM

but messing with fstab entries have always been known to break stuff if you made an error

T

tryhardsoccermomswag•3/24/24, 9:03 PM

also would take the same advice that antheas mentioned

T

tryhardsoccermomswag•3/24/24, 9:03 PM

run a smart test to see if the drive bazzite is installed to is failing

A

antheasOP•3/24/24, 9:04 PM

sudo smartctl --info /dev/nvme0n1 -a

sudo smartctl --info /dev/nvme0n1 -a

sudo smartctl --info /dev/nvme0n1 -a

sudo smartctl --info /dev/nvme0n1 -a

T

Twin Nature•3/24/24, 9:04 PM

yeah, I added the 2nd drive to fstab, but I was having issues even before that

T

tryhardsoccermomswag•3/24/24, 9:04 PM

then i would enter that command and let it run

A

antheasOP•3/24/24, 9:04 PM

if your drive is named like that

A

antheasOP•3/24/24, 9:04 PM

stick

 | fpaste

| fpaste

 | fpaste

| fpaste at the end

T

tryhardsoccermomswag•3/24/24, 9:05 PM

oh right, yeah you want to make sure it's the correct drive

A

antheasOP•3/24/24, 9:05 PM

90% is

Aantheas stick ` | fpaste` at the end

T

tryhardsoccermomswag•3/24/24, 9:05 PM

and send the link it outputs here too

T

Twin Nature•3/24/24, 9:06 PM

okay I will, one sec, just wanted to let ya know I tried to run the system update after the reboot and it failed with this

TTwin Nature okay I will, one sec, just wanted to let ya know I tried to run the system updat...

K

Kyle Gospo•3/24/24, 9:06 PM

your drive is fucked

K

Kyle Gospo•3/24/24, 9:07 PM

all the confirmation I needed

T

tryhardsoccermomswag•3/24/24, 9:07 PM

T

tryhardsoccermomswag•3/24/24, 9:07 PM

you may want to obtain a new drive if you financially can or use your new internal one as a replacement primary drive

A

antheasOP•3/24/24, 9:07 PM

dont reboot until you backup your data

T

Twin Nature•3/24/24, 9:08 PM

I basically don't have any data on it

A

antheasOP•3/24/24, 9:08 PM

also post smart test for our curiosity

T

Twin Nature•3/24/24, 9:09 PM

https://paste.centos.org/view/5f82e7e8

T

Twin Nature•3/24/24, 9:09 PM

unless I'm missing something it says it passed

K

Kyle Gospo•3/24/24, 9:10 PM

Error Information (NVMe Log 0x01, 16 of 16 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        755     0  0x8019  0x4004  0x004            0     1     -  Invalid Field in Command
  1        754     0  0x1004  0x4004  0x004            0     1     -  Invalid Field in Command
  2        753     0  0x6018  0x4005  0x028            0     0     -  Invalid Field in Command
 
Read Self-test Log failed: Invalid Field in Command (0x2002)

Error Information (NVMe Log 0x01, 16 of 16 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        755     0  0x8019  0x4004  0x004            0     1     -  Invalid Field in Command
  1        754     0  0x1004  0x4004  0x004            0     1     -  Invalid Field in Command
  2        753     0  0x6018  0x4005  0x028            0     0     -  Invalid Field in Command
 
Read Self-test Log failed: Invalid Field in Command (0x2002)

Error Information (NVMe Log 0x01, 16 of 16 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        755     0  0x8019  0x4004  0x004            0     1     -  Invalid Field in Command
  1        754     0  0x1004  0x4004  0x004            0     1     -  Invalid Field in Command
  2        753     0  0x6018  0x4005  0x028            0     0     -  Invalid Field in Command
 
Read Self-test Log failed: Invalid Field in Command (0x2002)

Error Information (NVMe Log 0x01, 16 of 16 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        755     0  0x8019  0x4004  0x004            0     1     -  Invalid Field in Command
  1        754     0  0x1004  0x4004  0x004            0     1     -  Invalid Field in Command
  2        753     0  0x6018  0x4005  0x028            0     0     -  Invalid Field in Command
 
Read Self-test Log failed: Invalid Field in Command (0x2002)

K

Kyle Gospo•3/24/24, 9:10 PM

she big not happy

K

Kyle Gospo•3/24/24, 9:11 PM

Data Units Read:                    232,256,529 [118 TB]
Data Units Written:                 190,257,515 [97.4 TB]
Host Read Commands:                 3,461,683,661
Host Write Commands:                2,507,853,514
Controller Busy Time:               31,420
Power Cycles:                       177
Power On Hours:                     24,182
Unsafe Shutdowns:                   144

Data Units Read:                    232,256,529 [118 TB]
Data Units Written:                 190,257,515 [97.4 TB]
Host Read Commands:                 3,461,683,661
Host Write Commands:                2,507,853,514
Controller Busy Time:               31,420
Power Cycles:                       177
Power On Hours:                     24,182
Unsafe Shutdowns:                   144

Data Units Read:                    232,256,529 [118 TB]
Data Units Written:                 190,257,515 [97.4 TB]
Host Read Commands:                 3,461,683,661
Host Write Commands:                2,507,853,514
Controller Busy Time:               31,420
Power Cycles:                       177
Power On Hours:                     24,182
Unsafe Shutdowns:                   144

Data Units Read:                    232,256,529 [118 TB]
Data Units Written:                 190,257,515 [97.4 TB]
Host Read Commands:                 3,461,683,661
Host Write Commands:                2,507,853,514
Controller Busy Time:               31,420
Power Cycles:                       177
Power On Hours:                     24,182
Unsafe Shutdowns:                   144

A

antheasOP•3/24/24, 9:11 PM

wtf only 177 power cycles

A

antheasOP•3/24/24, 9:11 PM

100TB reads

A

antheasOP•3/24/24, 9:11 PM

what are you doing chia mining

Aantheas what are you doing chia mining

K

Kyle Gospo•3/24/24, 9:11 PM

https://tenor.com/view/chia-chia-pet-gif-13763465

Tenor

chia pet man

A

antheasOP•3/24/24, 9:12 PM

tbh test looks normal

A

antheasOP•3/24/24, 9:12 PM

mostly

A

antheasOP•3/24/24, 9:12 PM

mine looks like that at least, minus the errors

T

Twin Nature•3/24/24, 9:12 PM

if I'm not mistaken this drive was part of my Plex server, so those reads are from streaming content

A

antheasOP•3/24/24, 9:12 PM

Data Units Read:                    19,573,742 [10.0 TB]
Data Units Written:                 18,229,393 [9.33 TB]
Host Read Commands:                 290,434,441
Host Write Commands:                387,161,847
Controller Busy Time:               499
Power Cycles:                       1,262
Power On Hours:                     213
Unsafe Shutdowns:                   113

Data Units Read:                    19,573,742 [10.0 TB]
Data Units Written:                 18,229,393 [9.33 TB]
Host Read Commands:                 290,434,441
Host Write Commands:                387,161,847
Controller Busy Time:               499
Power Cycles:                       1,262
Power On Hours:                     213
Unsafe Shutdowns:                   113

Data Units Read:                    19,573,742 [10.0 TB]
Data Units Written:                 18,229,393 [9.33 TB]
Host Read Commands:                 290,434,441
Host Write Commands:                387,161,847
Controller Busy Time:               499
Power Cycles:                       1,262
Power On Hours:                     213
Unsafe Shutdowns:                   113

Data Units Read:                    19,573,742 [10.0 TB]
Data Units Written:                 18,229,393 [9.33 TB]
Host Read Commands:                 290,434,441
Host Write Commands:                387,161,847
Controller Busy Time:               499
Power Cycles:                       1,262
Power On Hours:                     213
Unsafe Shutdowns:                   113

ratios are different

T

Twin Nature•3/24/24, 9:13 PM

so like, definitely don't use this drive?

T

tryhardsoccermomswag•3/24/24, 9:13 PM

if you do not mind, i would try reinstalling on the other internal drive you put in

T

tryhardsoccermomswag•3/24/24, 9:14 PM

at least for a test, obviously backup the data for that one

K

Kyle Gospo•3/24/24, 9:14 PM

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        47 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    6%
Data Units Read:                    152,902,480 [78.2 TB]
Data Units Written:                 115,320,409 [59.0 TB]
Host Read Commands:                 2,239,228,168
Host Write Commands:                1,648,187,589
Controller Busy Time:               11,676
Power Cycles:                       3,398
Power On Hours:                     3,757
Unsafe Shutdowns:                   229
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               47 Celsius
Temperature Sensor 2:               52 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        47 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    6%
Data Units Read:                    152,902,480 [78.2 TB]
Data Units Written:                 115,320,409 [59.0 TB]
Host Read Commands:                 2,239,228,168
Host Write Commands:                1,648,187,589
Controller Busy Time:               11,676
Power Cycles:                       3,398
Power On Hours:                     3,757
Unsafe Shutdowns:                   229
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               47 Celsius
Temperature Sensor 2:               52 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        47 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    6%
Data Units Read:                    152,902,480 [78.2 TB]
Data Units Written:                 115,320,409 [59.0 TB]
Host Read Commands:                 2,239,228,168
Host Write Commands:                1,648,187,589
Controller Busy Time:               11,676
Power Cycles:                       3,398
Power On Hours:                     3,757
Unsafe Shutdowns:                   229
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               47 Celsius
Temperature Sensor 2:               52 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        47 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    6%
Data Units Read:                    152,902,480 [78.2 TB]
Data Units Written:                 115,320,409 [59.0 TB]
Host Read Commands:                 2,239,228,168
Host Write Commands:                1,648,187,589
Controller Busy Time:               11,676
Power Cycles:                       3,398
Power On Hours:                     3,757
Unsafe Shutdowns:                   229
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               47 Celsius
Temperature Sensor 2:               52 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

T

Twin Nature•3/24/24, 9:14 PM

I have another nvme I could use, I just gotta make sure it doesn't have anything on it first

A

antheasOP•3/24/24, 9:14 PM

inconclusive

T

Twin Nature•3/24/24, 9:16 PM

okay shutting down and putting in my other nvme

A

antheasOP•3/24/24, 9:17 PM

Warning  Comp. Temperature Time:    16

Warning  Comp. Temperature Time:    16

Warning  Comp. Temperature Time:    16

Warning  Comp. Temperature Time:    16

lol the legion go does in fact overheat the drive

rebooting will probably fix, no biggie

Similar Threads

Similar Threads

Similar Threads