Upgrading to MX-21 from MX-18 - Keep my Home folder
Upgrading to MX-21 from MX-18 - Keep my Home folder
Hi Everyone,
This might have a simple solution. I have been using MX 18 for awhile now, but yesterday something strange happen and my computer refuse to load up. Something about running fsck manually. I did basic research and read that i need to run the fsck command on the damage sda, but that made everything worse and now my computer doesnt recognize the mx partition. So i just decided to just update to MX 21. My issue is i have important files in my home folder that i need to save, but the MX 21 installation doesnt give me the option to save it or i might have missed it.
My question are, can i update to mx 21 w/o formatting the whole drive? or is there an option that i missed somewhere?
Thank you
This might have a simple solution. I have been using MX 18 for awhile now, but yesterday something strange happen and my computer refuse to load up. Something about running fsck manually. I did basic research and read that i need to run the fsck command on the damage sda, but that made everything worse and now my computer doesnt recognize the mx partition. So i just decided to just update to MX 21. My issue is i have important files in my home folder that i need to save, but the MX 21 installation doesnt give me the option to save it or i might have missed it.
My question are, can i update to mx 21 w/o formatting the whole drive? or is there an option that i missed somewhere?
Thank you
- dolphin_oracle
- Developer
- Posts: 22270
- Joined: Sun Dec 16, 2007 12:17 pm
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
under format there should be a "preserve home" option if we are talking about home being on your root partition, and there is a "preserve" option for any other partition.
You do not have the required permissions to view the files attached to this post.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
You only get the option to save /home when you elect to use custom partitioning. However, there is a huge difference between the Debian base used in MX 18 and in MX 21 and this means that any configuration files held in the home folder of MX 18 will play havoc with the configuration files created during and after the MX 21 install. Your best option is to do a clean install of MX 21 (without saving /home) and then restore your files from a backup. leaving the MX 18 cruft behind.
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.
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.
- dolphin_oracle
- Developer
- Posts: 22270
- Joined: Sun Dec 16, 2007 12:17 pm
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
I would be more concerned about the health the harddrive, and try to back all my stuff off the partition anyway.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
It largely depends on what type of device "sda" is. If it's an SSD / NVMe, then it's likely dying / dead, given the fsck failure. If it's an HDD, it might be recoverable / reusable depending on what event caused the damage.dolphin_oracle wrote: Wed May 24, 2023 8:16 am I would be more concerned about the health the harddrive, and try to back all my stuff off the partition anyway.
@gmap27
You need to boot into a live session of MX 21, run the quick System Info utility and then post its output here so that we have a better idea of the system we are diagnosing.
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.
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.
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
Better still, the output of: sudo smartctl -x /dev/sda
Also if you do preserve home, and you use the same user name as the original home directory's name, the installer will later on ask you what you want to do with the original home directory.
Also if you do preserve home, and you use the same user name as the original home directory's name, the installer will later on ask you what you want to do with the original home directory.
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
My preference is to simply do a backup of my home folder and then go ahead and install the new system and selectively move what I want from the backup into the new system. Especially from MX-18 to MX-21/22 since the underlying system has changed quite a bit. However, there is a setting in the installer to preserve your home folder if you want. Inside the installer read the help notes on the left hand side.
Seaken64
Seaken64
MX21-64 XFCE & W11 on Lenovo 330S LT. MX21-KDE & MX21-XFCE on Live USB.
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
@AK-47 here you go. Thanks.AK-47 wrote: Wed May 24, 2023 9:16 am Better still, the output of: sudo smartctl -x /dev/sda
Also if you do preserve home, and you use the same user name as the original home directory's name, the installer will later on ask you what you want to do with the original home directory.
Code: Select all
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12
Device Model: ST31000528AS
Serial Number: 6VPBFA8A
LU WWN Device Id: 5 000c50 032b2571c
Firmware Version: CC46
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Mon May 29 09:43:24 2023 EDT
==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213891en
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM level is: 208 (intermediate), recommended: 208
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Unknown
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 600) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 171) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 092 092 006 - 232057131
3 Spin_Up_Time PO---- 094 092 000 - 0
4 Start_Stop_Count -O--CK 096 096 020 - 4262
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 32
7 Seek_Error_Rate POSR-- 087 060 030 - 4862898512
9 Power_On_Hours -O--CK 030 030 000 - 61431
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 098 098 020 - 2130
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 001 001 000 - 481
188 Command_Timeout -O--CK 099 096 000 - 8590131449
189 High_Fly_Writes -O-RCK 099 099 000 - 1
190 Airflow_Temperature_Cel -O---K 064 056 045 - 36 (Min/Max 26/36)
194 Temperature_Celsius -O---K 036 044 000 - 36 (0 19 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 032 020 000 - 232057131
197 Current_Pending_Sector -O--C- 096 096 000 - 203
198 Offline_Uncorrectable ----C- 096 096 000 - 203
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 67265 (70 171 0)
241 Total_LBAs_Written ------ 100 253 000 - 437041557
242 Total_LBAs_Read ------ 100 253 000 - 2432724011
||||||_ 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 GPL,SL R/O 1 Summary SMART error log
0x02 GPL,SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x06 GPL,SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 GPL,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
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 2248 Device vendor specific log
0xa8 GPL,SL VS 129 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xb0 GPL VS 2928 Device vendor specific log
0xbd GPL VS 252 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device 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 (5 sectors)
Device Error Count: 479 (device log contains only the most recent 20 errors)
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 479 [18] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 2f 47 00 00 Error: UNC at LBA = 0x3a042f47 = 973352775
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 f8 00 00 3a 04 2f 01 e0 00 00:12:21.101 READ DMA EXT
25 00 00 00 08 00 00 3a 04 2e f9 e0 00 00:12:21.096 READ DMA EXT
25 00 00 00 08 00 00 3a 04 27 f1 e0 00 00:12:21.094 READ DMA EXT
25 00 00 00 f8 00 00 3a 04 26 d9 e0 00 00:12:21.086 READ DMA EXT
25 00 00 00 f8 00 00 3a 04 1f 19 e0 00 00:12:20.835 READ DMA EXT
Error 478 [17] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 83 00 00 Error: UNC at LBA = 0x3a042683 = 973350531
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 06 00 00 3a 04 26 83 e0 00 00:37:00.289 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:37:00.288 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:37:00.285 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:37:00.283 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:37:00.263 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 477 [16] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 82 00 00 Error: UNC at LBA = 0x3a042682 = 973350530
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 3a 04 26 82 e0 00 00:36:57.442 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:57.441 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:36:57.438 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:36:57.436 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:57.414 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 476 [15] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 81 00 00 Error: UNC at LBA = 0x3a042681 = 973350529
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 3a 04 26 81 e0 00 00:36:54.587 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:54.585 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:36:54.582 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:36:54.580 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:54.560 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 475 [14] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 82 00 00 Error: UNC at LBA = 0x3a042682 = 973350530
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 07 00 00 3a 04 26 82 e0 00 00:36:51.739 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:51.737 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:36:51.735 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:36:51.733 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:51.712 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 474 [13] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 81 00 00 Error: UNC at LBA = 0x3a042681 = 973350529
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 3a 04 26 81 e0 00 00:36:48.884 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:48.882 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:36:48.879 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:36:48.877 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:48.856 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 473 [12] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 7b 00 00 Error: UNC at LBA = 0x3a04267b = 973350523
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 06 00 00 3a 04 26 7b e0 00 00:36:46.019 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:46.018 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:36:46.015 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:36:46.013 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:45.993 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 472 [11] occurred at disk power-on lifetime: 61430 hours (2559 days + 14 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
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 3a 04 26 7a 00 00 Error: UNC at LBA = 0x3a04267a = 973350522
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 3a 04 26 7a e0 00 00:36:43.172 READ DMA EXT
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:43.170 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:36:43.168 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:36:43.166 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 00:36:43.145 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
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% 9850 -
# 2 Short offline Completed without error 00% 2990 -
# 3 Short offline Completed without error 00% 2257 -
# 4 Short offline Completed without error 00% 1559 -
# 5 Short offline Completed without error 00% 1109 -
# 6 Short offline Completed without error 00% 0 -
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): 522 (0x020a)
Device State: Active (0)
Current Temperature: 36 Celsius
Power Cycle Min/Max Temperature: 26/36 Celsius
Lifetime Min/Max Temperature: 19/44 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 59 minutes
Min/Max recommended Temperature: 14/55 Celsius
Min/Max Temperature Limit: 10/60 Celsius
Temperature History Size (Index): 128 (125)
Index Estimated Time Temperature Celsius
126 2023-05-24 04:15 33 **************
127 2023-05-24 05:14 33 **************
0 2023-05-24 06:13 33 **************
1 2023-05-24 07:12 32 *************
2 2023-05-24 08:11 33 **************
3 2023-05-24 09:10 32 *************
4 2023-05-24 10:09 33 **************
5 2023-05-24 11:08 34 ***************
... ..( 2 skipped). .. ***************
8 2023-05-24 14:05 34 ***************
9 2023-05-24 15:04 35 ****************
10 2023-05-24 16:03 35 ****************
11 2023-05-24 17:02 36 *****************
12 2023-05-24 18:01 36 *****************
13 2023-05-24 19:00 37 ******************
... ..( 2 skipped). .. ******************
16 2023-05-24 21:57 37 ******************
17 2023-05-24 22:56 36 *****************
18 2023-05-24 23:55 36 *****************
19 2023-05-25 00:54 36 *****************
20 2023-05-25 01:53 35 ****************
21 2023-05-25 02:52 35 ****************
22 2023-05-25 03:51 34 ***************
... ..( 6 skipped). .. ***************
29 2023-05-25 10:44 34 ***************
30 2023-05-25 11:43 35 ****************
31 2023-05-25 12:42 35 ****************
32 2023-05-25 13:41 36 *****************
33 2023-05-25 14:40 37 ******************
... ..( 2 skipped). .. ******************
36 2023-05-25 17:37 37 ******************
37 2023-05-25 18:36 38 *******************
... ..( 2 skipped). .. *******************
40 2023-05-25 21:33 38 *******************
41 2023-05-25 22:32 39 ********************
42 2023-05-25 23:31 39 ********************
43 2023-05-26 00:30 38 *******************
44 2023-05-26 01:29 38 *******************
45 2023-05-26 02:28 38 *******************
46 2023-05-26 03:27 37 ******************
47 2023-05-26 04:26 37 ******************
48 2023-05-26 05:25 36 *****************
... ..( 2 skipped). .. *****************
51 2023-05-26 08:22 36 *****************
52 2023-05-26 09:21 35 ****************
53 2023-05-26 10:20 35 ****************
54 2023-05-26 11:19 35 ****************
55 2023-05-26 12:18 36 *****************
56 2023-05-26 13:17 36 *****************
57 2023-05-26 14:16 37 ******************
58 2023-05-26 15:15 38 *******************
59 2023-05-26 16:14 39 ********************
60 2023-05-26 17:13 40 *********************
61 2023-05-26 18:12 40 *********************
62 2023-05-26 19:11 40 *********************
63 2023-05-26 20:10 39 ********************
64 2023-05-26 21:09 39 ********************
65 2023-05-26 22:08 38 *******************
66 2023-05-26 23:07 37 ******************
67 2023-05-27 00:06 38 *******************
68 2023-05-27 01:05 38 *******************
69 2023-05-27 02:04 38 *******************
70 2023-05-27 03:03 37 ******************
... ..( 2 skipped). .. ******************
73 2023-05-27 06:00 37 ******************
74 2023-05-27 06:59 36 *****************
75 2023-05-27 07:58 35 ****************
76 2023-05-27 08:57 35 ****************
77 2023-05-27 09:56 35 ****************
78 2023-05-27 10:55 36 *****************
... ..( 4 skipped). .. *****************
83 2023-05-27 15:50 36 *****************
84 2023-05-27 16:49 37 ******************
85 2023-05-27 17:48 38 *******************
86 2023-05-27 18:47 38 *******************
87 2023-05-27 19:46 38 *******************
88 2023-05-27 20:45 37 ******************
... ..( 3 skipped). .. ******************
92 2023-05-28 00:41 37 ******************
93 2023-05-28 01:40 36 *****************
94 2023-05-28 02:39 36 *****************
95 2023-05-28 03:38 37 ******************
96 2023-05-28 04:37 37 ******************
97 2023-05-28 05:36 36 *****************
98 2023-05-28 06:35 35 ****************
99 2023-05-28 07:34 36 *****************
100 2023-05-28 08:33 35 ****************
101 2023-05-28 09:32 34 ***************
102 2023-05-28 10:31 33 **************
103 2023-05-28 11:30 34 ***************
104 2023-05-28 12:29 ? -
105 2023-05-28 13:28 22 ***
106 2023-05-28 14:27 ? -
107 2023-05-28 15:26 25 ******
108 2023-05-28 16:25 25 ******
109 2023-05-28 17:24 36 *****************
110 2023-05-28 18:23 ? -
111 2023-05-28 19:22 25 ******
112 2023-05-28 20:21 25 ******
113 2023-05-28 21:20 36 *****************
114 2023-05-28 22:19 36 *****************
115 2023-05-28 23:18 ? -
116 2023-05-29 00:17 26 *******
117 2023-05-29 01:16 ? -
118 2023-05-29 02:15 30 ***********
119 2023-05-29 03:14 ? -
120 2023-05-29 04:13 31 ************
121 2023-05-29 05:12 ? -
122 2023-05-29 06:11 33 **************
123 2023-05-29 07:10 ? -
124 2023-05-29 08:09 26 *******
125 2023-05-29 09:08 26 *******
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 6 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device 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
Last edited by gmap27 on Mon May 29, 2023 9:56 am, edited 1 time in total.
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
Hi Guys sorry for the delay.
@j2mcgreg here you go. Thanks.
@j2mcgreg here you go. Thanks.
Code: Select all
Snapshot created on: 20230515_1743
System: Kernel: 5.10.0-23-amd64 [5.10.179-1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: quiet splasht nosplash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7
dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower May 15 2023
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: Dell product: Inspiron 580 v: N/A serial: <filter> Chassis:
type: 3 serial: <filter>
Mobo: Dell model: 0C2KJT v: A00 serial: <filter> BIOS: Dell v: A07 date: 11/13/2010
CPU: Info: Dual Core model: Intel Core i3 550 bits: 64 type: MT MCP arch: Nehalem family: 6
model-id: 25 (37) stepping: 5 microcode: 2 cache: L2: 4 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25536
Speed: 1463 MHz min/max: 1200/3200 MHz Core speeds (MHz): 1: 1463 2: 1463 3: 1463
4: 1463
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: loaded: intel
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: HDMI1 res: 1366x768 hz: 60 dpi: 57 size: 609x347mm (24.0x13.7")
diag: 701mm (27.6")
OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-23-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Broadcom NetLink BCM57788 Gigabit Ethernet PCIe vendor: Dell driver: tg3
v: kernel port: 0400 bus-ID: 02:00.0 chip-ID: 14e4:1691 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.39 TiB used: 1.86 GiB (0.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST31000528AS size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: CC46 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3500418AS size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s type: HDD rpm: 7200
serial: <filter> rev: CC46 scheme: MBR
ID-3: /dev/sdg maj-min: 8:96 type: USB vendor: PNY model: USB 3.0 FD size: 29.48 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
maj-min: 8:2
Sensors: System Temperatures: cpu: 39.0 C mobo: N/A
Fan Speeds (RPM): cpu: 945 fan-2: 748
Repos: Packages: note: see --pkg apt: 1969 lib: 989 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info: Processes: 201 Uptime: 7m wakeups: 1 Memory: 5.59 GiB used: 1.41 GiB (25.3%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A
alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
Video Tweaks:
pre-sandybridge UXA acceleration
Re: Upgrading to MX-21 from MX-18 - Keep my Home folder
@gmap27
Please use code tags for this type of information. Highlight the output and click on </> at the top of the post.
viewtopic.php?p=726665#p726665
Please use code tags for this type of information. Highlight the output and click on </> at the top of the post.
viewtopic.php?p=726665#p726665
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB