Startup problems after wrong antiX shutdown

[Member Robin]

Helpful

Up

0

::

Hi Marcelo,

from your file:

demo@antix1:~
$ kill -SIGUSR1 $(pidof dd)
bash: kill: (12697) - Operation not allowed

means simply, you should have entered sudo in front of this command also, just like you did it for the dd command in the first window before also. Normal user doesn’t have permission to send the SIGUSR1 signal to a running process started by root user.

$ sudo fsck /dev/sda1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
rootantiX19: clean, 118929/1310720 files, 1872413/5242880 blocks

means filesystem is marked as “clean”, so fsck assumes there is no need for checking.

So try to use the command
sudo e2fsck -vf /dev/sda1
instead. (make sure file system sda1 is not mounted before executing the command)

Robin.

• This reply was modified 2 years ago by Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Helpful

Up

0

::

Hi Robin,

Thank you for your guidance and explanations on each step.

demo@antix1:~
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
loop0 7:0 0 701,1M 1 loop /live/linux
sda 8:0 0 74,5G 0 disk
├─sda1 8:1 0 20G 0 part
├─sda2 8:2 0 52,5G 0 part
└─sda3 8:3 0 2G 0 part [SWAP]
sdb 8:16 1 1,9G 0 disk
├─sdb1 8:17 1 803M 0 part /live/boot-dev
└─sdb2 8:18 1 49M 0 part /media/ANTIX-UEFI

demo@antix1:~
$ sudo e2fsck -vf /dev/sda1

Presumimos que você recebeu as instruções de sempre do administrador
de sistema local. Basicamente, resume-se a estas três coisas:

#1) Respeite a privacidade dos outros.
#2) Pense antes de digitar.
#3) Com grandes poderes vêm grandes responsabilidades.

[sudo] senha para demo:
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

118929 inodes used (9.07%, out of 1310720)
40 non-contiguous files (0.0%)
74 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 112586/14
1872413 blocks used (35.71%, out of 5242880)
0 bad blocks
1 large file

100085 regular files
12368 directories
0 character device files
0 block device files
0 fifos
25 links
6467 symbolic links (6321 fast symbolic links)
0 sockets
————
118945 files
demo@antix1:~
$

After applying the above command, turn off the computer and remove the USB device, turn on the computer, boot via hard drive, the error message “failed (code4)” similar to the image:

https://i.ibb.co/ThL3h8C/anti-X-Apos-Desligamento-Errado-09-04-2021-2.jpg

———-

Olá Robin,

Obrigado por suas orientações e explicações sobre cada etapa.

Após aplicar o comando acima, desligar o computador e remover o dispositivo USB, ligar o computador, inicializar via disco rígido, a mensagem de erro “failed (code4)” semelhante a imagem: (URL da imagem no texto traduzido em inglês).

marcelocripe

[Member Robin]

Helpful

Up

0

::

You did everything fine.

OK, now you do know how to perform this test correctly, please do enter the slightly modified command

sudo e2fsck -vfcy /dev/sda1

executed from live system again, make sure /dev/sda is unmounted. This will perform a deep test of structure and try fix block and inode errors automatically.

Hopefully it doesn’t turn out to be true what skidoo foresees by saying the structures are most likely overwritten already. But as long you don’t try it you can’t know for sure. So give it a try, the worst thing to happen is that you learn how to handle all these commands 🙂 Reinstalling is something you can do always when all the repair attempts fail.

Btw, if you’d like to know about the meaning of the options “-vfcy”, read the output from fsck.ext4 – -help carefully: v means verbose, f means force check, c means check for bad blocks (and inodes), y means yes to all the “fix” questions.

Did you perform the command Dave had recommended?

Dave wrote:

I would check the hard drive to see if it is going bad.
smartctl -a /dev/sda

Execute this also from live system in this case. It is important not to use a damaged filesystem as long as it is not fixed, which means not to mount it (at least not in write mode) and always to access it from “outside” only, which means to boot always a live system from another device before executing any repair attempts, after having created a backup copy in the very beginning. All the steps you have observed already.

Robin

• This reply was modified 2 years ago by Robin.
• This reply was modified 2 years ago by Robin.
• This reply was modified 2 years ago by Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Helpful

Up

0

::

demo@antix1:~
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
loop0 7:0 0 701,1M 1 loop /live/linux
sda 8:0 0 74,5G 0 disk
├─sda1 8:1 0 20G 0 part
├─sda2 8:2 0 52,5G 0 part
└─sda3 8:3 0 2G 0 part [SWAP]
sdb 8:16 1 1,9G 0 disk
├─sdb1 8:17 1 803M 0 part /live/boot-dev
└─sdb2 8:18 1 49M 0 part /media/ANTIX-UEFI

demo@antix1:~
$ sudo e2fsck -vfcy /dev/sda1

Presumimos que você recebeu as instruções de sempre do administrador
de sistema local. Basicamente, resume-se a estas três coisas:

#1) Respeite a privacidade dos outros.
#2) Pense antes de digitar.
#3) Com grandes poderes vêm grandes responsabilidades.

[sudo] senha para demo:
e2fsck 1.44.5 (15-Dec-2018)
Checking for bad blocks (read-only test): 0.00% done, 0:00 elapsed. (0/0/0 errdone
rootantiX19: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

rootantiX19: ***** FILE SYSTEM WAS MODIFIED *****

118956 inodes used (9.08%, out of 1310720)
40 non-contiguous files (0.0%)
74 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 112613/14
1873052 blocks used (35.73%, out of 5242880)
0 bad blocks
1 large file

100110 regular files
12370 directories
0 character device files
0 block device files
0 fifos
25 links
6467 symbolic links (6321 fast symbolic links)
0 sockets
————
118972 files

demo@antix1:~
$ smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

Smartctl open device: /dev/sda failed: Permission denied

demo@antix1:~
$ sudo smartctl -a /dev/sda
[sudo] senha para demo:
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Maxtor DiamondMax 20
Device Model: MAXTOR STM3802110A
Serial Number: 5LS9AXLY
Firmware Version: 3.AAK
User Capacity: 80.026.361.856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Thu Apr 15 22:59:57 2021 -03
SMART support is: Available – device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument ‘on’ to enable it.
(override with ‘-T permissive’ option)

demo@antix1:~

[Member ModdIt]

Helpful

Up

0

::

Hi Marcello, needs sudo, normally anyway. I doubt the power outage killed the HDD but who knows.
Anyway you will need to do

$ sudo smartctl -s on /dev/sda to switch on smart, you may also need to look in BIOS, some devices have to be set there.
or in both places.
$ sudo smartctl -a /dev/sda As smart was off probably not the best method, pls use below.

$ sudo smartctl -t /dev/sda runs self tests, extended test takes a while but is often more conclusive option with regard to results.

Dońt panik if you see pre fail, old age. Please post result, smart is not always so easy to interpret and the disk can still fail next start..

Magick word is always “Backup”.

• This reply was modified 2 years ago by ModdIt.

[Member marcelocripe]

Helpful

Up

0

::

Hello ModdIt,

Thanks for the commands, I hope I have applied it correctly in the terminal:

demo@antix1:~
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
loop0 7:0 0 701,1M 1 loop /live/linux
sda 8:0 0 74,5G 0 disk
├─sda1 8:1 0 20G 0 part
├─sda2 8:2 0 52,5G 0 part
└─sda3 8:3 0 2G 0 part [SWAP]
sdb 8:16 1 1,9G 0 disk
├─sdb1 8:17 1 803M 0 part /live/boot-dev
└─sdb2 8:18 1 49M 0 part /media/ANTIX-UEFI

demo@antix1:~
$ sudo smartctl -s /dev/sda

Presumimos que você recebeu as instruções de sempre do administrador
de sistema local. Basicamente, resume-se a estas três coisas:

#1) Respeite a privacidade dos outros.
#2) Pense antes de digitar.
#3) Com grandes poderes vêm grandes responsabilidades.

[sudo] senha para demo:
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=======> INVALID ARGUMENT TO -s: /dev/sda
=======> VALID ARGUMENTS ARE: on, off, aam,[N|off], apm,[N|off], dsn,[on|off], lookahead,[on|off], security-freeze, standby,[N|off|now], wcache,[on|off], rcache,[on|off], wcreorder,[on|off[,p]], wcache-sct,[ata|on|off[,p]] <=======

Use smartctl -h to get a usage summary

demo@antix1:~
$ sudo smartctl -s /dev/sda1
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=======> INVALID ARGUMENT TO -s: /dev/sda1
=======> VALID ARGUMENTS ARE: on, off, aam,[N|off], apm,[N|off], dsn,[on|off], lookahead,[on|off], security-freeze, standby,[N|off|now], wcache,[on|off], rcache,[on|off], wcreorder,[on|off[,p]], wcache-sct,[ata|on|off[,p]] <=======

Use smartctl -h to get a usage summary

demo@antix1:~
$ sudo smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Maxtor DiamondMax 20
Device Model: MAXTOR STM3802110A
Serial Number: 5LS9AXLY
Firmware Version: 3.AAK
User Capacity: 80.026.361.856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Fri Apr 16 19:38:09 2021 -03
SMART support is: Available – device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument ‘on’ to enable it.
(override with ‘-T permissive’ option)

demo@antix1:~
$ sudo smartctl -a /dev/sda1
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Maxtor DiamondMax 20
Device Model: MAXTOR STM3802110A
Serial Number: 5LS9AXLY
Firmware Version: 3.AAK
User Capacity: 80.026.361.856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Fri Apr 16 19:38:14 2021 -03
SMART support is: Available – device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument ‘on’ to enable it.
(override with ‘-T permissive’ option)
demo@antix1:~

$ sudo smartctl -t /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=======> INVALID ARGUMENT TO -t: /dev/sda
=======> VALID ARGUMENTS ARE: offline, short, long, conveyance, force, vendor,N, select,M-N, pending,N, afterselect,[on|off] <=======

Use smartctl -h to get a usage summary

demo@antix1:~
$ sudo smartctl -t /dev/sda1
[sudo] senha para demo:
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=======> INVALID ARGUMENT TO -t: /dev/sda1
=======> VALID ARGUMENTS ARE: offline, short, long, conveyance, force, vendor,N, select,M-N, pending,N, afterselect,[on|off] <=======

Use smartctl -h to get a usage summary

demo@antix1:~
$

———-

Olá ModdIt,

Obrigado pelos comandos, eu espero ter aplicado corretamente no terminal:

marcelocripe

[Member Robin]

Helpful

Up

0

::

the correct command is
sudo smartctl -s on /dev/sda
and after this
sudo smartctl -a /dev/sda
should work fine

• This reply was modified 2 years ago by Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Member ModdIt]

Helpful

Up

0

::

Hallo Marcello, Robin, sadly Language and distance are making this problem more complicated than it should be.
seems Marcello misunderstood my earlier post.

To enable smart the command must include the option on The readout shows smart is still switched off/disabled.

SMART support is: Available – device has SMART capability.
SMART support is: Disabled
SMART Disabled. Use option -s with argument ‘on’ to enable it.
(override with ‘-T permissive’ option)

sudo smartctl -s on /dev/sda

sudo smartctl -a /dev/sda -T permissive should also work.

Maybe at the end of this creating a test an internal drive cheat sheet would be good.

[Member Xecure]

Helpful

Up

0

::

I am late to this topic. Life forced me away from computers for some time.

Following marcelocripe’s terminal output, skidoo’s recommendations and Robin’s observations, I assume you need to fix the sda2 partition, and not the sda1 partition, based on:

marcelocripe wrote:

fsck from util-linux 2.33.1
homeantiX contains a file system with errors, check forced.
homeantiX: Inodes that were part of a corrupted orphan linked list found.

homeantiX: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4

marcelocripe wrote:

After following some topics on this forum, I understood the importance of separating into different partitions, one partition for the operating system and another for storing user data and settings. At installation the system – “root” is on the sda1 partition and “home” is on the sda2 partition of the hard drive.

Robin wrote:

Is there any possibility it is /dev/sda2 instead, which is damaged?

So, fixing the partition (from live USB, with automount disabled) using
sudo fsck /dev/sda2
or, as suggested later in the thread
sudo e2fsck -vf /dev/sda2

After this, reboot and try to login to the “fixed” system. If you cannot log in with the “felipe” user, log in as root, and use the antiX User Manager to create a new user (for example, felipe2). Log out and log in with the felipe2 user just to see if the system can now log in with a user created and saved in the homeantiX partition.

Copy the important files from /home/felipe to /home/felipe2, reboot, and now you should be able to work with the new felipe2 user with the same files and configuration as the original felipe user. If this works, use the antiX User manager to remove the original felipe user (removing the files) and then create it again using the option to copy the user files from felipe2 (and later remove felipe2 so there is no possibility of confusion).

I hope you followed the recommendations before mentioned in this thread to backup the /home/felipe/ folder (just in case) before trying to fix the filesystem.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member marcelocripe]

Helpful

Up

0

::

I hope everyone is well.

Robin and ModdIt, now I understood what was wrong with the command, I had confused the command with the text translated into pt-BR.

Xecure, it’s good to have you back …

I made a backup copy of Felipe’s important data, I hope to be able to apply all the teachings until today (17-04-2021). If they do not work or I am unable to apply the teachings, I will have to install again in order to return the computer. I would really like to be able to learn how to fix damaged system files in antiX, but Felipe can’t be without his computer any longer. I hope you understand me.

I will need to restart the computer and soon I will return to this topic.

My sincere thanks to everyone for the instructions and teachings.

marcelocripe

demo@antix1:~
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
loop0 7:0 0 701,1M 1 loop /live/linux
sda 8:0 0 74,5G 0 disk
├─sda1 8:1 0 20G 0 part
├─sda2 8:2 0 52,5G 0 part
└─sda3 8:3 0 2G 0 part [SWAP]
sdb 8:16 1 1,9G 0 disk
├─sdb1 8:17 1 803M 0 part /live/boot-dev
└─sdb2 8:18 1 49M 0 part /media/ANTIX-UEFI
demo@antix1:~
$ sudo fsck /dev/sda2

Presumimos que você recebeu as instruções de sempre do administrador
de sistema local. Basicamente, resume-se a estas três coisas:

#1) Respeite a privacidade dos outros.
#2) Pense antes de digitar.
#3) Com grandes poderes vêm grandes responsabilidades.

[sudo] senha para demo:
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
homeantiX contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 1192120 was part of the orphaned inode list. FIXED.
Inode 1192633 was part of the orphaned inode list. FIXED.
Inode 1192862 was part of the orphaned inode list. FIXED.
Inode 1192863 was part of the orphaned inode list. FIXED.
Inode 1192864 was part of the orphaned inode list. FIXED.
Inode 1192865 was part of the orphaned inode list. FIXED.
Inode 1192866 was part of the orphaned inode list. FIXED.
Inode 1192867 was part of the orphaned inode list. FIXED.
Inode 1192868 was part of the orphaned inode list. FIXED.
Inode 1192869 was part of the orphaned inode list. FIXED.
Inode 1192870 was part of the orphaned inode list. FIXED.
Inode 1192871 was part of the orphaned inode list. FIXED.
Inode 1192872 was part of the orphaned inode list. FIXED.
Inode 1192873 was part of the orphaned inode list. FIXED.
Inode 1192874 was part of the orphaned inode list. FIXED.
Inode 1192875 was part of the orphaned inode list. FIXED.
Inode 1192876 was part of the orphaned inode list. FIXED.
Inode 1192877 was part of the orphaned inode list. FIXED.
Inode 1192878 was part of the orphaned inode list. FIXED.
Inode 1192879 was part of the orphaned inode list. FIXED.
Inode 1192880 was part of the orphaned inode list. FIXED.
Inode 1192881 was part of the orphaned inode list. FIXED.
Inode 1192882 was part of the orphaned inode list. FIXED.
Inode 1192883 was part of the orphaned inode list. FIXED.
Inode 1192884 was part of the orphaned inode list. FIXED.
Inode 1192885 was part of the orphaned inode list. FIXED.
Inode 1192886 was part of the orphaned inode list. FIXED.
Inode 1192887 was part of the orphaned inode list. FIXED.
Inode 1192888 was part of the orphaned inode list. FIXED.
Inode 1192889 was part of the orphaned inode list. FIXED.
Inode 1192890 was part of the orphaned inode list. FIXED.
Inode 1192891 was part of the orphaned inode list. FIXED.
Inode 1192892 was part of the orphaned inode list. FIXED.
Inode 1192893 was part of the orphaned inode list. FIXED.
Inode 1192894 was part of the orphaned inode list. FIXED.
Inode 1192895 was part of the orphaned inode list. FIXED.
Inode 1192897 was part of the orphaned inode list. FIXED.
Inode 1192898 was part of the orphaned inode list. FIXED.
Inode 1192899 was part of the orphaned inode list. FIXED.
Inode 1192900 was part of the orphaned inode list. FIXED.
Inode 1192901 was part of the orphaned inode list. FIXED.
Inode 1192902 was part of the orphaned inode list. FIXED.
Inode 1192903 was part of the orphaned inode list. FIXED.
Inode 1192904 was part of the orphaned inode list. FIXED.
Inode 1192905 was part of the orphaned inode list. FIXED.
Inode 1192906 was part of the orphaned inode list. FIXED.
Inode 1192907 was part of the orphaned inode list. FIXED.
Inode 1192908 was part of the orphaned inode list. FIXED.
Inode 1192909 was part of the orphaned inode list. FIXED.
Inode 1192910 was part of the orphaned inode list. FIXED.
Inode 1192911 was part of the orphaned inode list. FIXED.
Inode 1192912 was part of the orphaned inode list. FIXED.

Pass 2: Checking directory structure
Entry ‘log’ in /felipe/.desktop-session (1179656) has deleted/unused inode 1179676. Clear<y>? yes
Entry ‘log.old’ in /felipe/.desktop-session (1179656) has deleted/unused inode 1192912. Clear<y>? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -4751368 +4773910 +4797139 -5207124
Fix<y>? yes
Free blocks count wrong for group #145 (0, counted=2).
Fix<y>? yes
Free blocks count wrong for group #158 (1992, counted=1993).
Fix<y>? yes
Free blocks count wrong (4608825, counted=4608914).
Fix<y>? yes
Inode bitmap differences: -1179676 -1192912
Fix<y>? yes
Free inodes count wrong for group #144 (1, counted=2).
Fix<y>? yes
Free inodes count wrong for group #145 (3172, counted=3173).
Fix<y>? yes
Free inodes count wrong (3403749, counted=3403751).
Fix<y>? yes

homeantiX: ***** FILE SYSTEM WAS MODIFIED *****
homeantiX: 45081/3448832 files (1.4% non-contiguous), 9161326/13770240 blocks
demo@antix1:~
$ sudo smartctl -s on /dev/sda
[sudo] senha para demo:
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

demo@antix1:~
$ sudo smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Maxtor DiamondMax 20
Device Model: MAXTOR STM3802110A
Serial Number: 5LS9AXLY
Firmware Version: 3.AAK
User Capacity: 80.026.361.856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Sat Apr 17 09:43:58 2021 -03
SMART support is: Available – device has SMART capability.
SMART support is: Enabled

=== 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: ( 430) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 27) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 097 006 Pre-fail Always – 120024455
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always – 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always – 1841
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always – 0
7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always – 131477141
9 Power_On_Hours 0x0032 093 093 000 Old_age Always – 6808
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always – 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always – 1887
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always – 503
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always – 0
190 Airflow_Temperature_Cel 0x0022 065 054 045 Old_age Always – 35 (Min/Max 26/36)
194 Temperature_Celsius 0x0022 035 046 000 Old_age Always – 35 (0 12 0 0 0)
195 Hardware_ECC_Recovered 0x001a 076 051 000 Old_age Always – 15213987
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always – 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline – 0
199 UDMA_CRC_Error_Count 0x003e 200 191 000 Old_age Always – 2254
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline – 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always – 0

SMART Error Log Version: 1
ATA Error Count: 584 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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 584 occurred at disk power-on lifetime: 6446 hours (268 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 SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 28 40 c4 37 e0 00 00:01:35.966 READ DMA
c8 00 40 00 c4 37 e0 00 00:01:35.953 READ DMA
c8 00 30 90 c3 37 e0 00 00:01:35.943 READ DMA
c8 00 20 b0 c2 37 e0 00 00:01:35.934 READ DMA
c8 00 0f c8 86 24 e0 00 00:01:35.921 READ DMA

Error 583 occurred at disk power-on lifetime: 6446 hours (268 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 SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 18 48 ae 37 e0 00 00:01:35.022 READ DMA
c8 00 28 60 ad 37 e0 00 00:01:35.149 READ DMA
c8 00 10 10 ad 37 e0 00 00:01:35.136 READ DMA
c8 00 08 08 ab 37 e0 00 00:01:35.132 READ DMA
c8 00 08 80 a9 37 e0 00 00:01:35.106 READ DMA

Error 582 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 40 18 d7 37 e0 00 00:01:30.553 READ DMA
c8 00 40 d8 d6 37 e0 00 00:01:30.538 READ DMA
c8 00 40 98 d6 37 e0 00 00:01:30.532 READ DMA
c8 00 08 50 d6 37 e0 00 00:01:30.681 READ DMA
c8 00 28 08 d3 37 e0 00 00:01:30.676 READ DMA

Error 581 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 28 40 c4 37 e0 00 00:01:29.693 READ DMA
c8 00 40 00 c4 37 e0 00 00:01:29.664 READ DMA
c8 00 30 90 c3 37 e0 00 00:01:29.657 READ DMA
c8 00 20 b0 c2 37 e0 00 00:01:29.650 READ DMA
c8 00 28 48 c2 37 e0 00 00:01:29.631 READ DMA

Error 580 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 40 a8 89 37 e0 00 00:01:27.036 READ DMA
c8 00 20 48 89 37 e0 00 00:01:27.035 READ DMA
c8 00 08 c0 88 37 e0 00 00:01:27.035 READ DMA
c8 00 08 78 88 37 e0 00 00:01:27.035 READ DMA
c8 00 10 28 88 37 e0 00 00:01:27.034 READ DMA

SMART Self-test log structure revision number 1

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.

demo@antix1:~
$ sudo smartctl -t /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=======> INVALID ARGUMENT TO -t: /dev/sda
=======> VALID ARGUMENTS ARE: offline, short, long, conveyance, force, vendor,N, select,M-N, pending,N, afterselect,[on|off] <=======

Use smartctl -h to get a usage summary

demo@antix1:~
$ sudo smartctl -s on /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

demo@antix1:~
$ sudo smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Maxtor DiamondMax 20
Device Model: MAXTOR STM3802110A
Serial Number: 5LS9AXLY
Firmware Version: 3.AAK
User Capacity: 80.026.361.856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Sat Apr 17 09:45:45 2021 -03
SMART support is: Available – device has SMART capability.
SMART support is: Enabled

=== 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: ( 430) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 27) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 097 006 Pre-fail Always – 120024455
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always – 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always – 1841
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always – 0
7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always – 131477154
9 Power_On_Hours 0x0032 093 093 000 Old_age Always – 6808
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always – 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always – 1887
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always – 503
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always – 0
190 Airflow_Temperature_Cel 0x0022 065 054 045 Old_age Always – 35 (Min/Max 26/36)
194 Temperature_Celsius 0x0022 035 046 000 Old_age Always – 35 (0 12 0 0 0)
195 Hardware_ECC_Recovered 0x001a 076 051 000 Old_age Always – 15213997
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always – 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline – 0
199 UDMA_CRC_Error_Count 0x003e 200 191 000 Old_age Always – 2254
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline – 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always – 0

SMART Error Log Version: 1
ATA Error Count: 584 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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 584 occurred at disk power-on lifetime: 6446 hours (268 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 SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 28 40 c4 37 e0 00 00:01:35.966 READ DMA
c8 00 40 00 c4 37 e0 00 00:01:35.953 READ DMA
c8 00 30 90 c3 37 e0 00 00:01:35.943 READ DMA
c8 00 20 b0 c2 37 e0 00 00:01:35.934 READ DMA
c8 00 0f c8 86 24 e0 00 00:01:35.921 READ DMA

Error 583 occurred at disk power-on lifetime: 6446 hours (268 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 SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 18 48 ae 37 e0 00 00:01:35.022 READ DMA
c8 00 28 60 ad 37 e0 00 00:01:35.149 READ DMA
c8 00 10 10 ad 37 e0 00 00:01:35.136 READ DMA
c8 00 08 08 ab 37 e0 00 00:01:35.132 READ DMA
c8 00 08 80 a9 37 e0 00 00:01:35.106 READ DMA

Error 582 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 40 18 d7 37 e0 00 00:01:30.553 READ DMA
c8 00 40 d8 d6 37 e0 00 00:01:30.538 READ DMA
c8 00 40 98 d6 37 e0 00 00:01:30.532 READ DMA
c8 00 08 50 d6 37 e0 00 00:01:30.681 READ DMA
c8 00 28 08 d3 37 e0 00 00:01:30.676 READ DMA

Error 581 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 28 40 c4 37 e0 00 00:01:29.693 READ DMA
c8 00 40 00 c4 37 e0 00 00:01:29.664 READ DMA
c8 00 30 90 c3 37 e0 00 00:01:29.657 READ DMA
c8 00 20 b0 c2 37 e0 00 00:01:29.650 READ DMA
c8 00 28 48 c2 37 e0 00 00:01:29.631 READ DMA

Error 580 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 40 a8 89 37 e0 00 00:01:27.036 READ DMA
c8 00 20 48 89 37 e0 00 00:01:27.035 READ DMA
c8 00 08 c0 88 37 e0 00 00:01:27.035 READ DMA
c8 00 08 78 88 37 e0 00 00:01:27.035 READ DMA
c8 00 10 28 88 37 e0 00 00:01:27.034 READ DMA

SMART Self-test log structure revision number 1

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.

demo@antix1:~
$ sudo smartctl -a /dev/sda -T permissive
smartctl 6.6 2017-11-05 r4594 [i686-linux-4.4.240-antix.2-486-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Maxtor DiamondMax 20
Device Model: MAXTOR STM3802110A
Serial Number: 5LS9AXLY
Firmware Version: 3.AAK
User Capacity: 80.026.361.856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Sat Apr 17 09:46:18 2021 -03
SMART support is: Available – device has SMART capability.
SMART support is: Enabled

=== 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: ( 430) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 27) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 097 006 Pre-fail Always – 120024455
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always – 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always – 1841
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always – 0
7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always – 131477164
9 Power_On_Hours 0x0032 093 093 000 Old_age Always – 6808
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always – 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always – 1887
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always – 503
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always – 0
190 Airflow_Temperature_Cel 0x0022 065 054 045 Old_age Always – 35 (Min/Max 26/36)
194 Temperature_Celsius 0x0022 035 046 000 Old_age Always – 35 (0 12 0 0 0)
195 Hardware_ECC_Recovered 0x001a 076 051 000 Old_age Always – 15214007
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always – 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline – 0
199 UDMA_CRC_Error_Count 0x003e 200 191 000 Old_age Always – 2254
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline – 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always – 0

SMART Error Log Version: 1
ATA Error Count: 584 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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 584 occurred at disk power-on lifetime: 6446 hours (268 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 SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 28 40 c4 37 e0 00 00:01:35.966 READ DMA
c8 00 40 00 c4 37 e0 00 00:01:35.953 READ DMA
c8 00 30 90 c3 37 e0 00 00:01:35.943 READ DMA
c8 00 20 b0 c2 37 e0 00 00:01:35.934 READ DMA
c8 00 0f c8 86 24 e0 00 00:01:35.921 READ DMA

Error 583 occurred at disk power-on lifetime: 6446 hours (268 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 SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 18 48 ae 37 e0 00 00:01:35.022 READ DMA
c8 00 28 60 ad 37 e0 00 00:01:35.149 READ DMA
c8 00 10 10 ad 37 e0 00 00:01:35.136 READ DMA
c8 00 08 08 ab 37 e0 00 00:01:35.132 READ DMA
c8 00 08 80 a9 37 e0 00 00:01:35.106 READ DMA

Error 582 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 40 18 d7 37 e0 00 00:01:30.553 READ DMA
c8 00 40 d8 d6 37 e0 00 00:01:30.538 READ DMA
c8 00 40 98 d6 37 e0 00 00:01:30.532 READ DMA
c8 00 08 50 d6 37 e0 00 00:01:30.681 READ DMA
c8 00 28 08 d3 37 e0 00 00:01:30.676 READ DMA

Error 581 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 28 40 c4 37 e0 00 00:01:29.693 READ DMA
c8 00 40 00 c4 37 e0 00 00:01:29.664 READ DMA
c8 00 30 90 c3 37 e0 00 00:01:29.657 READ DMA
c8 00 20 b0 c2 37 e0 00 00:01:29.650 READ DMA
c8 00 28 48 c2 37 e0 00 00:01:29.631 READ DMA

Error 580 occurred at disk power-on lifetime: 6427 hours (267 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
— — — — — — —
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
c8 00 40 a8 89 37 e0 00 00:01:27.036 READ DMA
c8 00 20 48 89 37 e0 00 00:01:27.035 READ DMA
c8 00 08 c0 88 37 e0 00 00:01:27.035 READ DMA
c8 00 08 78 88 37 e0 00 00:01:27.035 READ DMA
c8 00 10 28 88 37 e0 00 00:01:27.034 READ DMA

SMART Self-test log structure revision number 1

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.

demo@antix1:~
$ sudo e2fsck -vf /dev/sda2
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

45081 inodes used (1.31%, out of 3448832)
584 non-contiguous files (1.3%)
29 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 44915/24
9161326 blocks used (66.53%, out of 13770240)
0 bad blocks
2 large files

42623 regular files
2307 directories
0 character device files
0 block device files
0 fifos
0 links
142 symbolic links (134 fast symbolic links)
0 sockets
————
45072 files

demo@antix1:~
$

———-

Eu espero que todos estejam bem.

Robin e ModdIt, agora eu entendi o que estava errado no comando, eu havia confundido o comando com o texto traduzido para pt-BR.

Xecure, é bom tê-lo de volta…

Eu fiz a cópia de segurança dos dados importantes do Felipe, eu espero conseguir aplicar todos os ensinamentos até o dia de hoje (17-04-2021). Se não funcionarem ou eu não conseguir aplicar os ensinamentos, eu terei que instalar novamente para poder devolver o computador. Eu gostaria muito de poder aprender a corrigir arquivos de sistema danificados no antiX, mas o Felipe não pode ficar mais tempo sem o computador. Eu espero que vocês me compreendam.

Eu vou precisar reiniciar o computador e daqui a pouco eu retorno neste tópico.

Meus sinceros agradecimentos a todos pelas instruções e ensinamentos.

marcelocripe

[Member marcelocripe]

Helpful

Up

0

::

I restarted the computer and started laughing on my own … (the laughter, they are happy!), It was possible to access Felipe’s user normally and the graphic mode was started successfully.

You are really impressive, you know a lot about antiX Linux. Only those who do not want to learn here with these teachers and teachers. I say, that I always want to learn more, that I am extremely grateful for all of you, for being patient with me and for not giving up on me.

As this tutorial is in two languages, it will certainly be of great help and usefulness to other people who speak the Portuguese language, they will only need to translate the texts in English.

Thank you very much.

marcelocripe

———-

Eu reiniciei o computador e comecei a rir sozinho … (os risos, são de felicidade!), foi possível acessar o usuário do Felipe normalmente e o modo gráfico foi iniciado com sucesso.

Vocês são realmente impressionantes, conhecem muito do antiX Linux. Só não aprende aqui com estes professores e mestres quem não quer. Eu digo, que quero sempre aprender mais, que sou extremamente grato por todos vocês existirem, por terem paciência comigo e ainda por não desistirem de mim.

Como este tutorial está em dois idiomas, certamente será de grande ajuda e utilidade para as outras pessoas falantes do idioma Português, só precisarão traduzir os texto em Inglês.

Muito obrigado.

marcelocripe

[Author]

Posts