-
Search Results
-
In reply to: Clean out redundant windoze partition & resize antix
Budgie
Hi skidoo,
I am sorry if I have offended you and assure you I have not refused your advice. I did have a problem finding my way around but did as you advised.Here is what undetsand is the correct way to edit the time parameter:
# swap Amount of swap in use # swapmax Total amount of swap # swapperc Percentage of swap in use # sysname System name, Linux for example time %H:%M # information about format # totaldown net Total download, overflows at 4 GB on # Linux with 32-bit arch and there doesn't # seem to be a way to know how many timesI hope I had this right.
Unfortunately even after reboot the Conky time is still stubbornly showing in 12hr format even though my tray is showing 19:52:51 as I send this.
Thanks for your time. Sorry I couldn’t fix this. Will start a new thread with correct title.In reply to: Asunder problem
roland
roland@antix1:~
$ su
Password:
root@antix1:/home/roland# lsblk -o name,mountpoint,label,size,uuid
NAME MOUNTPOINT LABEL SIZE UUID
sda 465.8G
├─sda1 / rootantiX19 48.8G 2310738f-8a5a-4dee-a14f-c0ec6c3a93a6
├─sda2 1K
├─sda5 [SWAP] swap 11.7G 1540a43b-5380-407b-a657-be4b262d6e04
├─sda6 /home homeantiX 200.2G 231afe95-3cba-4993-beb1-b52726510965
└─sda7 /media/antix_data sda7_data 205G 3eedced4-3153-41ef-9147-953c4a5795fe
sdb 465.8G
├─sdb1 /media/sdb1 sdb1 232.7G 0a085231-c321-49d4-aaf0-9d7f71cf067d
└─sdb2 /media/sdb2 sdb2 233.1G 7cf9bdcd-a2e9-493c-90f7-68cbd17af463
sdc 465.8G
├─sdc1 /media/sdc1 sdc1 232.9G a8aca46c-d144-456c-93ae-39bc84a527c9
└─sdc2 /media/sdc2 sdc2 232.9G 8b2f7fe4-ac6f-406e-a4e4-8e9e0ab2d50c
sdd 465.8G
├─sdd1 /media/sdd1 sdd1 232.9G f949503c-76cd-4b06-ade0-fc54a756915a
└─sdd2 /media/sdd2 sdd2 232.9G 198b6b77-a1e4-4adf-b340-98a24491a44e
sde 100M
sr0 1024M
root@antix1:/home/roland#It doesn’t seem to provide any further information. Being only very small it isn’t a problem, but anything I don’t know the reason for may be a hidden problem. There are no other physical drives or volumes than the ones listed and which I know about having built it from scratch, which are sda thru sdd and their associated volumes. The screenshot shows files in /dev in this name range, there is an sde and an sdf present.
I wonder if I should simply disregard it, unless you feel it there may be value in further investigation, Xecure?
Attachments:
In reply to: Clean out redundant windoze partition & resize antix
OK, making slow progress as the pointer still has a mind of it’s own until I sort out the touchpad but to assist further, here is my system configuration at present:-
alastair@OldDell32:~ $ inxi -Fxz System: Host: OldDell32 Kernel: 4.9.193-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: IceWM 2.3.3 Distro: antiX-19_386-full Marielle Franco 16 October 2019 base: Debian GNU/Linux 10 (buster) Machine: Type: Portable System: Dell product: Inspiron 9300 v: N/A serial: <filter> Mobo: Dell model: 0C5668 serial: <filter> BIOS: Dell v: A05 date: 09/19/2005 Battery: ID-1: BAT0 charge: 79.9 Wh condition: 59.3/79.9 Wh (74%) model: Sanyo DELL C54475 status: Full CPU: Topology: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan rev: 8 L2 cache: 2048 KiB flags: pae sse sse2 bogomips: 2128 Speed: 1067 MHz min/max: 800/1867 MHz Core speed (MHz): 1: 1333 Graphics: Device-1: AMD RV370/M22 [Mobility Radeon X300] vendor: Dell driver: radeon v: kernel bus ID: 01:00.0 Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1200~59Hz OpenGL: renderer: ATI RV370 v: 2.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus ID: 00:1e.2 Sound Server: ALSA v: k4.9.193-antix.1-486-smp Network: Device-1: Broadcom Limited BCM4401-B0 100Base-TX vendor: Dell driver: b44 v: 2.0 port: de00 bus ID: 03:00.0 Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: de00 bus ID: 03:03.0 IF: eth0 state: up mac: <filter> Device-3: Dell Wireless 350 Bluetooth type: USB driver: btusb bus ID: 3-1:2 IF-ID-1: eth1 state: down mac: <filter> Drives: Local Storage: total: 74.53 GiB used: 547.73 GiB (734.9%) ID-1: /dev/sda vendor: Hitachi model: HTS548080M9AT00 size: 74.53 GiB Partition: ID-1: / size: 14.53 GiB used: 5.41 GiB (37.2%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 33.42 GiB used: 2.09 GiB (6.3%) fs: ext4 dev: /dev/sda3 ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 Sensors: System Temperatures: cpu: 48.0 C mobo: N/A sodimm: 46.0 C Fan Speeds (RPM): cpu: 2561 Info: Processes: 149 Uptime: 1h 34m Memory: 1.97 GiB used: 667.9 MiB (33.1%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 alastair@OldDell32:~ $ ^C alastair@OldDell32:~ $You will see I am only on kernel 4.9 so no point in changing this, although I do not understand yet why it is not at 5.0.3.
I edited /etc/conky/conky.conf to add the time parameter but this has not worked. I thought conky.conf took precedence but will edit conkyrc as you advise and see what happens.
As for wireless this is what I have:-
alastair@OldDell32:~ $ iwconfig eth0 IEEE 802.11 ESSID:"Errichel_Guests" Mode:Managed Frequency:2.447 GHz Access Point: 8E:DC:96:87:29:BA Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=88/100 Signal level=-41 dBm Noise level=-83 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:5 eth1 no wireless extensions. lo no wireless extensions. alastair@OldDell32:~No idea how to sort this out. As you advised, not totally necessary but it does help to have conky display correct when sorting out APs.
Thanks for your replies and I hope you can shed a bit more light in due course.
BudgieIn reply to: Asunder problem
roland
The suggested chown has restored the permissions to what they should be however have produced another mystery that I do not understand. I installed 4 identical and brand new 500gb disk drives in this build. At first boot it became apparent they came already formatted as Vfat with names in chinese characters which I did not want. I therefore before the installer ran, removed these with Gparted and replaced them as follows:-
drive 0 – sda1 for antiX, sda5 for swap, sda6 for $HOME and sda7 for data
drive 1 – sdb1 for data, sdb2 for data
drive 2 – sdc1 for data, sdc2 for data
drive 3 – sdd1 for data, sdd2 for dataDisk manager then produced a list of drive labels saying that no drives could be found corresponding to these labels, and inviting me to delete the labels if I wished and which was recommended, I did so.
I took advantage of the facility in 19.3 to install antiX on a dedicated partition sda1, swap on sda5, $HOME on sda6 and data on the remaining volumes.
But Gparted finds another partition and I do not know where it is located, 100mb and which Gparted cannot read, producing i-o errors. It is not visible on the maps of sda sdb sdc or sdd. It is causing no trouble except slows up the load of Gparted considerably and the warning messages have to be repeatedly cancelled, but strictly speaking I have no reason to run Gparted now the build is complete. However I would like to be rid of it after discovering the reason why it appears. I wonder if it has a real existence? I don’t suppose it could be the extended partition containing sda5 sda6 and sda7?
I’m sorry this post is drifting away from the original Asunder topic which I feel is secondary to resolving this mystery. I hope I am not stretching the rule too much?
I am doing some housekeeping on an old 32bit machine which did have a dual boot facility. This has not been used for a while, the details have been lost to me and the machine only boots to Antix, which is fine but I have no idea where grub is installed and upgrading has thrown up a grub question I cannot answer.
At present there are four partitions on the drive, windoze, Antix /, Antix home and swap. What I want to do is to delete the unwanted hpfs/ntfs partition, move my Antix root partition to the start of the drive, grow it a bit and then expand my home partition to fill the unused space.
I am on another machine temporarily so cannot give you fdisk -l output but my concern is making sure I do not lose boot capability during the process. Please could I have some guidance on when to do what and on rebuilding the boot configuration without making a mistake.
In reply to: Keyboard hangs after several minutes of uptime.
52midnight
Thanks for the replies. Output of inxi -Fxz:
[code]System: Host: qt2 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: LXDE 0.10.0
Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: AMI model: Aptio CRB serial: N/A UEFI [Legacy]: American Megatrends v: 5.6.5 date: 02/25/2019
CPU: Topology: Quad Core model: Intel Celeron J1900 bits: 64 type: MCP arch: Silvermont rev: 9 L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15993
Speed: 1333 MHz min/max: 1333/2416 MHz Core speeds (MHz): 1: 1333 2: 1333 3: 1333 4: 1333
Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920×1080~60Hz
OpenGL: renderer: Mesa DRI Intel Bay Trail v: 4.2 Mesa 18.3.6 direct render: Yes
Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio driver: snd_hda_intel v: kernel
bus ID: 00:1b.0
Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI port: e000
bus ID: 01:00.0
IF: eth0 state: down mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-2.1:4
IF: wlan1 state: up mac: <filter>
Drives: Local Storage: total: 998.75 GiB used: 414.47 GiB (41.5%)
ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB
ID-2: /dev/sdb vendor: Hoodisk model: SSD size: 59.63 GiB
ID-3: /dev/sdc type: USB vendor: Verbatim model: Store n Go Drive size: 7.61 GiB
Partition: ID-1: / size: 16.02 GiB used: 4.82 GiB (30.1%) fs: ext4 dev: /dev/sdb2
ID-2: swap-1 size: 3.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb5
Sensors: System Temperatures: cpu: 25.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 195 Uptime: 10m Memory: 3.69 GiB used: 617.2 MiB (16.3%) Init: SysVinit runlevel: 5 Compilers:
gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36
[/code]I’ve checked running processes and nothing is consuming system resources. The CPU is about 96% idle, 600MB of RAM are used from 3G6 available, and swap is unused.
CPU core temperature is normal according to the last dmesg posts.
mythcat
Hardware name: Hewlett-Packard HP Compaq 6710b (FG040EC#ABB)/30C0, BIOS 68DDU Ver. F.18 07/12/2011
dmesg report errors on default install[ 12.208093] usb usb7-port2: disabled by hub (EMI?), re-enabling... [ 12.208160] usb 7-2: USB disconnect, device number 2 [ 12.420047] usb 7-2: new full-speed USB device number 3 using uhci_hcd [ 12.535044] usb 7-2: device descriptor read/64, error -71 [ 12.964030] usb 7-2: device descriptor read/64, error -71 [ 13.176046] usb 7-2: new full-speed USB device number 4 using uhci_hcd [ 13.184491] udevd[398]: starting version 3.2.9 [ 13.318436] random: udevd: uninitialized urandom read (16 bytes read) [ 13.318685] random: udevd: uninitialized urandom read (16 bytes read) [ 13.318703] random: udevd: uninitialized urandom read (16 bytes read) [ 13.579771] udevd[399]: starting eudev-3.2.9 [ 13.704039] usb 7-2: device not accepting address 4, error -71 ... [ 15.968691] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000004) is beyond end of object (length 0x4) (20160831/exoparg2-427) [ 15.968709] ACPI Error: Method parse/execution failed [\_SB.C003.C098._DOD] (Node ffff88007c94e3e8), AE_AML_PACKAGE_LIMIT (20160831/psparse-543) [ 15.968723] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _DOD (20160831/video-1254) ... [ 3.308724] ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102F conflicts with OpRegion 0x0000000000001000-0x0000000000001042 (\_SB.C003.C004.C0D2) (20160831/utaddress-247) [ 3.308732] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 3.308736] ACPI Warning: SystemIO range 0x0000000000001130-0x000000000000113F conflicts with OpRegion 0x0000000000001100-0x000000000000113B (\_SB.C003.C004.C0E4) (20160831/utaddress-247) [ 3.308740] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 3.308741] ACPI Warning: SystemIO range 0x0000000000001100-0x000000000000112F conflicts with OpRegion 0x0000000000001100-0x000000000000113B (\_SB.C003.C004.C0E4) (20160831/utaddress-247) ... [ 0.137209] smpboot: CPU0: Intel(R) Celeron(R) CPU 560 @ 2.13GHz (family: 0x6, model: 0x16, stepping: 0x1) ... [ 46.048062] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out [ 46.149030] ------------[ cut here ]------------ [ 46.149047] WARNING: CPU: 0 PID: 2244 at drivers/gpu/drm/drm_irq.c:1254 drm_wait_one_vblank+0x181/0x190 [drm] [ 46.149048] vblank wait timed out on crtc 0 [ 46.149049] Modules linked in: ccm cpufreq_powersave cpufreq_conservative nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc dm_crypt dm_mod hid_uclogic(O) hp_wmi sparse_keymap ppdev coretemp joydev evdev input_leds serio_raw arc4 iTCO_wdt iTCO_vendor_support b43 snd_hda_codec_hdmi yenta_socket i915 snd_hda_codec_analog pcmcia_rsrc bcma snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec cfg80211 snd_hda_core drm_kms_helper snd_hwdep rfkill rng_core drm snd_pcm i2c_algo_bit fb_sys_fops snd_timer syscopyarea sysfillrect snd sysimgblt soundcore hp_accel i2c_core wmi lis3lv02d battery input_polldev shpchp parport_pc intel_agp parport tpm_infineon intel_gtt video button ac btrfs xor raid6_pq hid_generic ssb_hcd psmouse lpc_ich firewire_ohci firewire_core tg3 ssb pcmcia pcmcia_core fan thermal [ 46.149104] fjes [ 46.149108] CPU: 0 PID: 2244 Comm: Xorg Tainted: G W O 4.9.235-antix.1-amd64-smp #1 [ 46.149109] Hardware name: Hewlett-Packard HP Compaq 6710b (FG040EC#ABB)/30C0, BIOS 68DDU Ver. F.18 07/12/2011 [ 46.149111] ffffc9000075f960 ffffffff813b1c49 ffffc9000075f9b0 0000000000000000 [ 46.149114] ffffc9000075f9a0 ffffffff81123865 000004e600000000 ffff880036250000 [ 46.149117] 0000000000000000 0000000000000000 0000000003000002 ffff88007c37f808 [ 46.149119] Call Trace: [ 46.149126] [<ffffffff813b1c49>] dump_stack+0x6d/0x94 [ 46.149130] [<ffffffff81123865>] __warn+0xce/0xe9 [ 46.149133] [<ffffffff8106516a>] warn_slowpath_fmt+0x4a/0x50 [ 46.149136] [<ffffffff810a3111>] ? finish_wait+0x51/0x60 [ 46.149143] [<ffffffffa03095f1>] drm_wait_one_vblank+0x181/0x190 [drm] [ 46.149145] [<ffffffff810a3390>] ? wake_atomic_t_function+0x50/0x50 [ 46.149182] [<ffffffffa0581782>] intel_get_load_detect_pipe+0x562/0x570 [i915] [ 46.149196] [<ffffffffa05bd841>] intel_tv_detect+0x121/0x570 [i915] [ 46.149201] [<ffffffffa037cf1f>] drm_helper_probe_single_connector_modes+0x39f/0x4f0 [drm_kms_helper] [ 46.149208] [<ffffffffa0320124>] ? __drm_mode_object_find+0x64/0xd0 [drm] [ 46.149215] [<ffffffffa031f4ee>] drm_mode_getconnector+0x2ee/0x370 [drm] [ 46.149217] [<ffffffff81135e89>] ? balance_dirty_pages_ratelimited+0x229/0x470 [ 46.149224] [<ffffffffa0307e01>] drm_ioctl+0x221/0x480 [drm] [ 46.149227] [<ffffffff811d55f9>] ? seq_read+0x1e9/0x3d0 [ 46.149234] [<ffffffffa031f200>] ? drm_mode_connector_property_set_ioctl+0x30/0x30 [drm] [ 46.149237] [<ffffffff811ae6f0>] ? __vfs_write+0xf0/0x140 [ 46.149240] [<ffffffff811c38f4>] do_vfs_ioctl+0x94/0x5e0 [ 46.149242] [<ffffffff811c3eb5>] SyS_ioctl+0x75/0x80 [ 46.149243] [<ffffffff811b0d48>] ? SyS_write+0x48/0xc0 [ 46.149246] [<ffffffff810024fe>] do_syscall_64+0x6e/0xe0 [ 46.149249] [<ffffffff817be78e>] entry_SYSCALL_64_after_swapgs+0x58/0xc6 [ 46.149251] ---[ end trace 674974fc8bee7f0b ]--- [ 46.284243] ------------[ cut here ]------------In reply to: How should I set up a sideways ram in my new build?
ModdIt
SSD, fragile if wrongly handled regarding setup,
That is pretty much a mythical animal, if you do not swap to the ssd and make sure it is
cooled as much as possible it will very likely last a long long time.
In any case with the memory you have and antiX swapping is unlikely to be a major problem.
Unless you are running really heavyweight stuff anyway.Just remember when an SSD fails it is in most cases sudden and complete rather than like HDD which often
gives warning signs.In reply to: How should I set up a sideways ram in my new build?
Hi roland, it would be helpful if you clarify whether you mean an SSD or
RAM-based solid-state drive which has internal battery and controller and
is possibly better used as a swap device.If you have SSD advice from fatmac is solid. In modern purchased sytems the SSD is
also used for swap but with settings for that kind of drive. Intent is to keep data
in RAM rather than swapping early as is more often done on HDD.- This reply was modified 2 years ago by ModdIt.
In reply to: How should I set up a sideways ram in my new build?
fatmac
If you mean an SSD, I’d put the O/S onto it, (less any swap that you may want – put that on a regular HDD).
(I sometimes use an SSD, I only have a / & /home on it.)
Linux (& BSD) since 1999
roland
I have just completed another dual-cpu build PC incorporating 4xhd, 1xdvd, and 16gb ram. Unlike my last attempt I installed a sideways ram or solid disk for the boot drive, 60gb wired to a Sata3 socket. The remaining 3 drives are the usual rotating types.
Can any member offer suggestions how to best install this drive? I am thinking along the lines of :-
Is a swap partition necessary at all? If so what size would be sensible given that this drive is for system files work files and temp files only. If thought necessary where should it be placed in relation to the boot partition, before or after, or is that of small importance? I have taken advantage of release 19.3 which makes it easy to place $home on another drive.
Are there any further observations that I should become aware of regarding sideways ram drives?
Thanks in advance for all suggestions.
In reply to: Computer sleeps every 30 seconds, Acer Aspire One
Lobstercat
Thank you guys so much for your help already! Okay, first for marcelocripe, I did run the command and here are the results:
First, the older version that works:
System:Host: antix1 Kernel: 4.9.212-antix.1-486-smp i686 bits: 32
Desktop: IceWM 1.6.6
Distro: antiX-19.2.1_386-base Hannie Schaft 29 March 2020
Machine:
Type: Other-vm? System: Acer product: Aspire one v: V1.05 serial: <filter>
Mobo: Acer model: Aspire one v: V1.05 serial: <filter> BIOS: Acer v: 1.05
date: 02/20/2009
CPU:
Topology: Single Core model: Intel Atom N270 bits: 32 type: MT
L2 cache: 512 KiB
Speed: 800 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 800 2: 800
Graphics:
Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915
v: kernelDisplay: x11 server: X.Org 1.20.4 driver: intel
unloaded: fbdev,modesetting,vesa resolution: 1024×600~60Hz
OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
Audio:
Device-1: Intel NM10/ICH7 Family High Definition Audio
driver: snd_hda_intel
Sound Server: ALSA v: k4.9.212-antix.1-486-smpNetwork:
Device-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter
driver: ath5k
IF: wlan0 state: up mac: <filter>Device-2: Qualcomm Atheros A R8121/AR8113/AR8114 Gigabit or Fast Ethernet
driver: ATL1E
IF: eth0 state: down mac: <filter>Drives:
Local Storage: total: 298.09 GiB used: 416.1 MiB (0.1%)
ID-1: /dev/sda vendor: Western Digital model: WD3200BPVT-22JJ5T0
size: 298.09 GiB
Partition:
ID-1: / size: 769.0 MiB used: 159.2 MiB (20.7%) fs: overlay
source: ERR-102
ID-2: swap-1 size: 4.87 GiB used: 80 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors:
System Temperatures: cpu: 47.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 147 Uptime: 1h 07m Memory: 991.2 MiB used: 209.6 MiB (21.1%)
Shell: bash inxi: 3.0.36
————————————————————————————————-
Now the updated version that doesn’t work right. Yes I know they are both almost identical but there are a few differences.
System:
Host: antix1 Kernel: 4.9.212-antix.1-486-smp i686 bits: 32
Desktop: IceWM 2.3.2
Distro: antiX-19.2.1_386-base Hannie Schaft 29 March 2020
Machine:
Type: Other-vm? Mobo: Acer model: Aspire one v: V1.05 serial: <filter>
BIOS: Acer v: 1.05 date: 02/20/2009
CPU:
Topology: Single Core model: Intel Atom N270 bits: 32 type: MCP
L2 cache: 512 KiB
Speed: N/A min/max: N/A Core speed (MHz): No speed data found for 1 cores.
Graphics:
Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: N/A
Display: x11 server: X.Org 1.20.4 driver: intel,vesa
unloaded: fbdev,modesetting resolution: 800×600~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
Audio:
Device-1: Intel NM10/ICH7 Family High Definition Audio
driver: snd_hda_intel
Sound Server: ALSA v: k4.9.212-antix.1-486-smp
Network:
Device-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter
driver: ath5k
IF: wlan0 state: down mac: <filter>Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
driver: ATL1E
IF: eth0 state: down mac: <filter>Drives:
Local Storage: total: 298.09 GiB used: 3.7 MiB (0.0%)
ID-1: /dev/sda vendor: Western Digital model: WD3200BPVT-22JJ5T0
size: 298.09 GiB
Partition:
ID-1: / size: 770.0 MiB used: 3.7 MiB (0.5%) fs: overlay source: ERR-102
ID-2: swap-1 size: 4.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors:
System Temperatures: cpu: 46.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 136 Uptime: 8m Memory: 991.2 MiB used: 203.2 MiB (20.5%)
Shell: bash inxi: 3.0.36
———————————————————————————————
As to the note from ModdIt, I am very intrigued by that possibility. There are like a million xserver-xorg packages installed, but looking at the “main” ones, I did notice something. Xserver-xorg is the same version on both, 1:7.7+19, but xserver-xorg-core is slightly different. While all versions are 2:1.20.4-1, the AntiX 19.3 and the troubled 19.2 version both have an added “+deb10u2” so could that be making the difference? Or should I be looking at a different package? Using apt-cache policy, I see all available versions appear to have the +deb thing at the end, so how or where would I go to downgrade that package, if that is the package I should downgrade? If you don’t know all of that part no problem I’m sure I can google it and find out, really just asking if that would be the package I should try changing, if you think that could be the culprit. Thank you all again so much for your help, I really appreciate it!!!
In reply to: Startup problems after wrong antiX shutdown
marcelocripe
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/sda2Presumimos 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>? yesPass 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>? yeshomeantiX: ***** 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: PASSEDGeneral 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 – 0SMART 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMASMART 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: PASSEDGeneral 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 – 0SMART 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMASMART 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: PASSEDGeneral 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 – 0SMART 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMAError 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 = 0Commands 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 DMASMART 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 information45081 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 files42623 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 filesdemo@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
In reply to: Suspend shuts down computer?
rayluo
The issue now is when I go to logout > suspend, it doesn’t suspend but instead shuts the computer down apparently. When I come back later, it’s totally off.
Hi @MCreaves, I happen to encounter an issue which initially looks similar. When I suspend my “new” Thinkpad computer, it would apparently shutdown, and then even automatically reboot.
Interestingly, later I realized that symptom was not exactly “suspend shuts down (and reboot) computer”. With a hint from somewhere else, I turned off the “Automatically turn on via LAN” feature from BIOS. Then, suspending my computer would not cause auto reboot. It seems the suspend is indeed working, because this computer happens to have a breathing light effect in its power button.
But then, the real problem in my case is that I can not successfully wake up the computer. Once wake up, the computer goes into reboot.
I don’t really know much about suspend on Linux since it has pretty much always just worked.
Same here, the suspend behavior works fine on my another two older Thinkpads.
After a lot of research, it seems that the issue might be related to an outdated BIOS
How would you know it is caused by BIOS? I also want to learn how to troubleshoot this.
In my case, Lenovo did a good job on continuing releasing newer BIOS version several times a year. But I want to make sure I have to go that route. I never did any BIOS upgrade before.
PS: My computer.
System: Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 parameters: vga=0x0317 tz=America/Los_Angeles quiet splasht disable=lx zswap.enabled=1 Desktop: IceWM 1.9.1 dm: SLiM 1.3.6 Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop System: LENOVO product: 2342CTO v: ThinkPad T430 serial: <filter> Chassis: type: 10 serial: <filter> Mobo: LENOVO model: 2342CTO v: Win8 STD DPK TPG serial: <filter> UEFI [Legacy]: LENOVO v: G1ET91WW (2.51 ) date: 01/09/2013 Battery: ID-1: BAT0 charge: 17.9 Wh condition: 18.3/47.5 Wh (39%) volts: 12.2/10.8 model: SANYO 45N1001 type: Li-ion serial: <filter> status: Unknown Memory: RAM: total: 15.43 GiB used: 790.3 MiB (5.0%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 16 L2 cache: 3072 KiB bogomips: 20752 Speed: 2602 MHz min/max: 1200/2600 MHz Core speeds (MHz): 1: 2602 2: 2598 3: 2600 4: 2600 Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept erms est f16c flexpriority fpu fsgsbase fxsr ht kaiser lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt pse pse36 pts rdrand rdtscp rep_good sep smep smx ss sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 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: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Vulnerable: No microcode Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GF108M [NVS 5400M] vendor: Lenovo driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0def Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz OpenGL: renderer: NVC1 v: 4.3 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 Device-2: NVIDIA GF108 High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0bea Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp Network: Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 6040 bus ID: 00:19.0 chip ID: 8086:1502 IF: eth0 state: down mac: <filter> Device-2: Intel Centrino Wireless-N 2200 driver: iwlwifi v: kernel port: 5000 bus ID: 03:00.0 chip ID: 8086:0891 IF: wlan0 state: up mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link IF-ID-1: docker0 state: down mac: <filter> IP v4: <filter> scope: global broadcast: <filter> WAN IP: <filter> Drives: Local Storage: total: 169.48 GiB used: 4.62 GiB (2.7%) ID-1: /dev/sda vendor: Intel model: SSDSC2BW180A3L size: 167.68 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: LF1i scheme: GPT ID-2: /dev/sdb type: USB model: USB Flash Disk size: 1.80 GiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.0 scheme: MBR Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ8C0 rev: SB01 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running RAID: Message: No RAID data was found. Partition: ID-1: / raw size: N/A size: 12.29 GiB used: 51.7 MiB (0.4%) fs: overlay source: ERR-102 label: N/A uuid: N/A ID-2: /live/boot-dev raw size: 1.75 GiB size: 1.71 GiB (97.95%) used: 1.21 GiB (70.8%) fs: ext4 dev: /dev/sdb1 label: antiX193x64gvmcd uuid: d7d21374-f867-4fc2-89f2-bf6755613faa ID-3: /live/linux raw size: 1.14 GiB size: <root required> used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A ID-4: /media/LIVE-UEFI raw size: 49.0 MiB size: 48.2 MiB (98.43%) used: 4.2 MiB (8.7%) fs: vfat dev: /dev/sdb2 label: LIVE-UEFI uuid: 2332-E684 ID-5: /media/antiX-Frugal raw size: 12.00 GiB size: 12.00 GiB (100.00%) used: 3.35 GiB (27.9%) fs: btrfs dev: /dev/sda8 label: antiX-Frugal uuid: fa9586e9-344c-4ef0-98f4-6363a14e2c19 ID-6: swap-1 size: 20.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) cache pressure: 50 (default 100) dev: /dev/sda7 label: N/A uuid: 761e7835-77ea-45bf-9e09-ea5f22263bbe Unmounted: ID-1: /dev/sda1 size: 1000.0 MiB fs: ntfs label: WINRE_DRV uuid: 7E94A2F794A2B0D7 ID-2: /dev/sda2 size: 260.0 MiB fs: vfat label: SYSTEM_DRV uuid: 68A5-CC68 ID-3: /dev/sda3 size: 128.0 MiB fs: <root required> label: N/A uuid: N/A ID-4: /dev/sda4 size: 122.54 GiB fs: ntfs label: N/A uuid: 5A8C599C8C59738B ID-5: /dev/sda5 size: 450.0 MiB fs: ntfs label: N/A uuid: ECCA0B3DCA0B0414 ID-6: /dev/sda6 size: 11.34 GiB fs: ntfs label: Lenovo_Recovery uuid: CA369CCE369CBD3F USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 speed: 480 Mb/s chip ID: 8087:0024 Hub: 1-1.2:3 info: Standard Microsystems USB 2.0 Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 0424:2514 Device-1: 1-1.2.1:5 info: Microsoft Optical Mouse with Tilt Wheel type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s chip ID: 045e:00d1 Device-2: 1-1.2.2:6 info: Cooler Master type: Keyboard,HID driver: hid-generic,usbhid interfaces: 3 rev: 1.1 speed: 12 Mb/s chip ID: 2516:0059 Device-3: 1-1.2.4:7 info: MosArt type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s chip ID: 062a:4102 Device-4: 1-1.6:4 info: Chicony Thinkpad T430 camera type: Video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s chip ID: 04f2:b2db Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Hub: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 8087:0024 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Device-5: 3-2:2 info: N/A type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 1845:0105 serial: <filter> Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 77.0 C mobo: N/A gpu: nouveau temp: 70 C Fan Speeds (RPM): cpu: 4112 Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http: //la.mxrepo.com/antix/buster buster main nonfree nosystemd Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 1: deb http: //deb.debian.org/debian buster-backports main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http: //ftp.us.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http: //ftp.us.debian.org/debian/ buster main contrib non-free 2: deb http: //security.debian.org/ buster/updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/docker.list 1: deb [arch=amd64] https: //download.docker.com/linux/debian buster stable Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main No active apt repos in: /etc/apt/sources.list.d/onion.list No active apt repos in: /etc/apt/sources.list.d/various.list Processes: CPU top: 5 1: cpu: 26.0% command: yad pid: 8719 mem: 29.6 MiB (0.1%) 2: cpu: 24.8% command: firefox-esr pid: 6370 mem: 227.5 MiB (1.4%) 3: cpu: 10.2% command: firefox-esr pid: 6196 mem: 372.8 MiB (2.3%) 4: cpu: 1.5% command: xorg pid: 5017 mem: 70.1 MiB (0.4%) 5: cpu: 0.2% command: dockerd pid: 4748 mem: 91.1 MiB (0.5%) Memory top: 5 1: mem: 372.8 MiB (2.3%) command: firefox-esr pid: 6196 cpu: 10.2% 2: mem: 227.5 MiB (1.4%) command: firefox-esr pid: 6370 cpu: 24.8% 3: mem: 138.6 MiB (0.8%) command: firefox-esr pid: 6482 cpu: 0.2% 4: mem: 100.6 MiB (0.6%) command: firefox-esr pid: 6393 cpu: 0.1% 5: mem: 91.1 MiB (0.5%) command: dockerd pid: 4748 cpu: 0.2% Info: Processes: 192 Uptime: 18m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36In reply to: Startup problems after wrong antiX shutdown
marcelocripe
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-UEFIdemo@antix1:~
$ sudo smartctl -s /dev/sdaPresumimos 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: DisabledSMART 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: DisabledSMART 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
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
