How to Update MX-18 to MX-21  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
Gigahenry007
Posts: 367
Joined: Tue Sep 10, 2019 12:34 pm

Re: How to Update MX-18 to MX-21

#71 Post by Gigahenry007 »

Hallo!
Note the attachment which I've been seeing but thought I'd include it as a help.
Installing Google Chrome and wondering if Chromium might help get this to install correctly.
No matter what I do it stops at 12% Formatting and never changes. Installs on YouTube shows the installs are usually very brief and it done. Waiting for whats next...
Best, Raphael
:frown:
Screenshot_2023-02-18_17-00-26.png
You do not have the required permissions to view the files attached to this post.
The ability of the person to return to normal activities is a hallmark of successful treatment

Huckleberry Finn

Re: How to Update MX-18 to MX-21

#72 Post by Huckleberry Finn »

It obviously takes that long time for that error (whatever causes that, being unable to format the partition).

Just at that point you can open/send the log file I mentioned.

This will open it:

Code: Select all

sudo featherpad /var/log/minstall.log

... Or at least on left pane click the "Live Log" tab (on that installation window) and see/post (copy-paste) it.

User avatar
j2mcgreg
Global Moderator
Posts: 7042
Joined: Tue Oct 23, 2007 12:04 pm

Re: How to Update MX-18 to MX-21

#73 Post by j2mcgreg »

My best guess is that the laptop's hard drive is shot. If the log that Huckleberry Finn has requested you post confirms this, here's how to replace it with a new one:
https://www.ifixit.com/Guide/Toshiba+Sa ... ent/108390

On your laptop, this is a dead easy task. FWIW, a 250 GB Western Digital SSD is $40.00 CDN here in Toronto and I expect that it will be about the same price in Vermont.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Gigahenry007
Posts: 367
Joined: Tue Sep 10, 2019 12:34 pm

Re: How to Update MX-18 to MX-21

#74 Post by Gigahenry007 »

Thanks for letting me the time differences. Sorry to upset you...
Where am I supposed to paste this? sudo featherpad /var/log/minstall.log. I thought it was the same as the QSI.
Do you mean if i do another install and see that Warning formatting window? OR NOW?
The specs needed for MX 21.3 seem to exceed what my computer has to offer? Yes/No?
The ability of the person to return to normal activities is a hallmark of successful treatment

User avatar
j2mcgreg
Global Moderator
Posts: 7042
Joined: Tue Oct 23, 2007 12:04 pm

Re: How to Update MX-18 to MX-21

#75 Post by j2mcgreg »

Paste the log here in a new post.

MX 21.3 will not overwhelm your computer.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Duliwi
Posts: 1178
Joined: Sun Jul 07, 2019 9:34 am

Re: How to Update MX-18 to MX-21

#76 Post by Duliwi »

Gigahenry007 wrote: Sat Feb 18, 2023 7:32 pm I thought it was the same as the QSI.
No, it's different. It's the protocol of your install try.
Gigahenry007 wrote: Sat Feb 18, 2023 7:32 pm Do you mean if i do another install and see that Warning formatting window? OR NOW?
Now.

Huckleberry Finn

Re: How to Update MX-18 to MX-21

#77 Post by Huckleberry Finn »

Gigahenry007 wrote: Sat Feb 18, 2023 7:32 pm...
Where am I supposed to paste this? sudo featherpad /var/log/minstall.log. I thought it was the same as the QSI.
Do you mean if i do another install and see that Warning formatting window?..
Yep. Just after you see that warning again or when it gets stuck etc.. (in case you decide to try installation once more) paste that in a terminal then press Enter.

Also follow the "Live Log" tab on left pane (on that installation window) will show what's going on.

Huckleberry Finn

Re: How to Update MX-18 to MX-21

#78 Post by Huckleberry Finn »

And here's the GSmartControl output of Ralph (posted by PM)

Code: Select all

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-20-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: Hitachi HTS541064A9E680
Serial Number: 120920J814007LG2564A
LU WWN Device Id: 5 000cca 6c2c0fc41
Firmware Version: JA4OA480
User Capacity: 640,135,028,736 bytes [640 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sat Feb 18 19:54:05 2023 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]

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

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 171) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate PO-R-- 100 100 062 - 0
2 Throughput_Performance P-S--- 100 100 040 - 0
3 Spin_Up_Time POS--- 177 177 033 - 1
4 Start_Stop_Count -O--C- 098 098 000 - 4358
5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0
7 Seek_Error_Rate PO-R-- 100 100 067 - 0
8 Seek_Time_Performance P-S--- 100 100 040 - 0
9 Power_On_Hours -O--C- 062 062 000 - 16886
10 Spin_Retry_Count PO--C- 100 100 060 - 0
12 Power_Cycle_Count -O--CK 098 098 000 - 4260
191 G-Sense_Error_Rate -O-R-- 099 099 000 - 2
192 Power-Off_Retract_Count -O--CK 100 100 000 - 163
193 Load_Cycle_Count -O--C- 074 074 000 - 269265
194 Temperature_Celsius -O---- 187 187 000 - 32 (Min/Max 14/47)
196 Reallocated_Event_Count -O--CK 100 100 000 - 0
197 Current_Pending_Sector -O---K 100 100 000 - 0
198 Offline_Uncorrectable ---R-- 100 100 000 - 0
199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 1
223 Load_Retry_Count -O-R-- 100 100 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 1 Comprehensive SMART error log
0x03 GPL R/O 1 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 1
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 [0] occurred at disk power-on lifetime: 10737 hours (447 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 00 00 00 00 00 00 00 00 00 Error: ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
20 ff 00 01 01 00 00 01 00 00 01 a0 00 00:00:00.577 READ SECTOR(S)
00 d7 70 00 01 00 00 00 00 00 01 a0 ff 6d+05:49:56.169 NOP [Reserved subcommand] [OBS-ACS-2]

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 16886 -
# 2 Short offline Completed without error 00% 3 -
# 3 Short offline Completed without error 00% 3 -
# 4 Short offline Completed without error 00% 3 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 33 Celsius
Power Cycle Min/Max Temperature: 29/33 Celsius
Lifetime Min/Max Temperature: 14/47 Celsius
Specified Max Operating Temperature: 33 Celsius
Under/Over Temperature Limit Count: 0/0

SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/60 Celsius
Min/Max Temperature Limit: -40/65 Celsius
Temperature History Size (Index): 128 (105)

Index Estimated Time Temperature Celsius
106 2023-02-18 17:47 32 *************
107 2023-02-18 17:48 31 ************
... ..( 10 skipped). .. ************
118 2023-02-18 17:59 31 ************
119 2023-02-18 18:00 30 ***********
120 2023-02-18 18:01 31 ************
121 2023-02-18 18:02 30 ***********
122 2023-02-18 18:03 31 ************
123 2023-02-18 18:04 30 ***********
124 2023-02-18 18:05 30 ***********
125 2023-02-18 18:06 30 ***********
126 2023-02-18 18:07 31 ************
... ..( 23 skipped). .. ************
22 2023-02-18 18:31 31 ************
23 2023-02-18 18:32 30 ***********
... ..( 16 skipped). .. ***********
40 2023-02-18 18:49 30 ***********
41 2023-02-18 18:50 29 **********
42 2023-02-18 18:51 30 ***********
... ..( 3 skipped). .. ***********
46 2023-02-18 18:55 30 ***********
47 2023-02-18 18:56 29 **********
... ..( 16 skipped). .. **********
64 2023-02-18 19:13 29 **********
65 2023-02-18 19:14 30 ***********
66 2023-02-18 19:15 29 **********
67 2023-02-18 19:16 30 ***********
68 2023-02-18 19:17 30 ***********
69 2023-02-18 19:18 29 **********
70 2023-02-18 19:19 30 ***********
... ..( 11 skipped). .. ***********
82 2023-02-18 19:31 30 ***********
83 2023-02-18 19:32 31 ************
... ..( 19 skipped). .. ************
103 2023-02-18 19:52 31 ************
104 2023-02-18 19:53 32 *************
105 2023-02-18 19:54 32 *************

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0009 2 3747 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 5 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS

Huckleberry Finn

Re: How to Update MX-18 to MX-21

#79 Post by Huckleberry Finn »

Gigahenry007 wrote: Sat Feb 18, 2023 7:32 pm...I thought it was the same as the QSI...
The one I mentioned previously is this, as an alternative and easy way (and a new feature of QSI) :

When you open the QSI click the menu (where the pointer is in the below picture) then select minstall.log

(...again, after the issue appears.. otherwise no such info will be there) :
You do not have the required permissions to view the files attached to this post.

User avatar
j2mcgreg
Global Moderator
Posts: 7042
Joined: Tue Oct 23, 2007 12:04 pm

Re: How to Update MX-18 to MX-21

#80 Post by j2mcgreg »

From the S.M.A.R.T. report, the only thing that may need attention is this:

Code: Select all

UDMA_CRC_Error_Count -O-R-- 200 200 000 - 1
This indicates that there was an error in the data feed to the hard drive. If this was a desktop, I'd recommend that the data cable be replaced, however, since it's a laptop, it might be enough to remove the hard drive, clean the contacts on both the cable and the hard drive with some rubbing alcohol on a QTip and then firmly reseat the hard drive.

This is also reported:

Code: Select all

G-Sense_Error_Rate -O-R-- 099 099 000 - 2
This states that there were two errors due to external vibration. But, these can be discounted because it's a mechanical drive in a ten year old laptop and there are going to be some vibrations as a matter of course.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

Post Reply

Return to “MX Help”