Ubuntu Suomen keskustelualueet
Ubuntun käyttö => Ubuntu tietokoneissa => Aiheen aloitti: jarmala - 06.08.21 - klo:18.12
-
Mistähän voisi johtua sellainen runsaat viikko sitten ilmaantunut ilmiö, että levyt paahtavat täysillä 100 %:n teholla n. 10 minuutin välein 10-20 sekunnin ajan? Tämän huomaa esim. videoita katsoessa, kun video pysähtyy 10 - 20 sekunnin ajaksi jatkuakseen sen jälkeen tai useimmiten TV:hen liitetty tv-boksi ja sen videotoistin (Kodi) heittää pyyhkeen kehään ja kaatuu.
Millä keinoilla syytä voisi alkaa jäljittää? Olen kyllä kokeillut ajaa iotop:ia ja katsoa siitä, mitkä ohjelmat ovat eniten ajossa noiden 20 sekunnin aikana. Ehdin nähdä ainakin init_splash:in ja jonkin systemd_journald:n...
Pitäisikö yrittää katsoa, mitä ajastettuja ohjelmia ajetaan 10 minuutin välein? Miten ne näkee? crontabistä? Vai missä muualla niitä määritellään? Crontab sanoo: no crontab for ari. Sudolla ajettaessa se sanoo: no crontab for root.
Käytössä Ubuntu 18.04.
-
Tämä nyt on ihan heitto, mutta jotenkin kuulostaisi siltä, että olisiko kyseessä välimuistiin liittyvä asia? Eikös suurimmassa osassa "task managereita" näe välimuistin osuuden suoraan vaikka graafisesti. Sieltä kait helpoin viitteen tuohon saisi?
-
Syslogista vois yrittää katsoa mitä juuri tuolla pysähtely hetkellä tapahtuu .
-
Syslogista vois yrittää katsoa mitä juuri tuolla pysähtely hetkellä tapahtuu .
dmesg sanoo:
[235280.564951] ata2.00: link is slow to respond, please be patient (ready=0)
[235289.988778] ata2.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[235289.988794] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[235290.082189] ata2.00: configured for UDMA/133
[235290.087022] ata2.01: configured for UDMA/133
[235290.087049] ata2: EH complete
[235854.739392] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[235854.739399] ata2.00: failed command: SMART
[235854.739405] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[235854.739409] ata2.00: status: { DRDY }
[235854.739417] ata2.00: hard resetting link
[235855.053623] ata2.01: hard resetting link
[235860.567239] ata2.00: link is slow to respond, please be patient (ready=0)
[235864.767144] ata2.00: SRST failed (errno=-16)
[235864.767154] ata2.00: hard resetting link
[235865.081711] ata2.01: hard resetting link
[235870.607014] ata2.00: link is slow to respond, please be patient (ready=0)
[235874.806956] ata2.00: SRST failed (errno=-16)
[235874.806966] ata2.00: hard resetting link
[235875.121343] ata2.01: hard resetting link
[235880.630797] ata2.00: link is slow to respond, please be patient (ready=0)
[235889.878627] ata2.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[235889.878642] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[235889.968018] ata2.00: configured for UDMA/133
[235889.972897] ata2.01: configured for UDMA/133
[235889.972918] ata2: EH complete
[236454.785425] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[236454.785433] ata2.00: failed command: SMART
[236454.785440] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[236454.785443] ata2.00: status: { DRDY }
[236454.785452] ata2.00: hard resetting link
[236455.099697] ata2.01: hard resetting link
[236460.613234] ata2.00: link is slow to respond, please be patient (ready=0)
[236464.817130] ata2.00: SRST failed (errno=-16)
[236464.817140] ata2.00: hard resetting link
[236465.131566] ata2.01: hard resetting link
[236470.640985] ata2.00: link is slow to respond, please be patient (ready=0)
[236474.848920] ata2.00: SRST failed (errno=-16)
[236474.848930] ata2.00: hard resetting link
[236475.163345] ata2.01: hard resetting link
[236480.672758] ata2.00: link is slow to respond, please be patient (ready=0)
[236490.760580] ata2.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[236490.760596] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[236490.849904] ata2.00: configured for UDMA/133
[236490.854803] ata2.01: configured for UDMA/133
[236490.854824] ata2: EH complete
Mitähän se tahtoo tarkoittaa?
-
Kernelin lokin mukaan levyohjaimessa tai jommassakummassa levyssä on vikaa. Kannattaa kuitenkin ensin tarkistaa kytkennät ja kokeilla levyjä eri SATA-porteissa.
-
Kernelin lokin mukaan levyohjaimessa tai jommassakummassa levyssä on vikaa. Kannattaa kuitenkin ensin tarkistaa kytkennät ja kokeilla levyjä eri SATA-porteissa.
Tutkin asiaa netistä löytämälläni komennolla:
ari@ari:~$ sudo smartctl -a /dev/sdc1
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-151-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-1CH166
Serial Number: W1F5D5F7
LU WWN Device Id: 5 000c50 077da9757
Firmware Version: CC29
User Capacity: 3 000 592 982 016 bytes [3,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Aug 7 13:22:23 2021 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Read SMART Data failed: scsi error badly formed scsi parameters
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
SMART Error Log Version: 1
ATA Error Count: 76 (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 76 occurred at disk power-on lifetime: 58340 hours (2430 days + 20 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
-- -- -- -- -- -- --
40 51 00 50 98 ff 05 Error: UNC at LBA = 0x05ff9850 = 100636752
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 08 4a 98 ff e5 00 1d+20:25:24.831 READ DMA
27 00 00 00 00 00 e0 00 1d+20:25:24.825 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 1d+20:25:24.822 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 1d+20:25:24.820 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 1d+20:25:24.796 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 75 occurred at disk power-on lifetime: 58340 hours (2430 days + 20 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
-- -- -- -- -- -- --
40 51 00 50 98 ff 05 Error: UNC at LBA = 0x05ff9850 = 100636752
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 08 4a 98 ff e5 00 1d+20:25:21.106 READ DMA
c8 00 08 42 98 ff e5 00 1d+20:25:21.105 READ DMA
c8 00 08 2a 98 ff e5 00 1d+20:25:21.100 READ DMA
c8 00 08 22 98 ff e5 00 1d+20:25:20.970 READ DMA
35 00 08 ff ff ff ef 00 1d+20:25:20.970 WRITE DMA EXT
Error 74 occurred at disk power-on lifetime: 58340 hours (2430 days + 20 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
-- -- -- -- -- -- --
40 51 00 50 98 ff 05 Error: UNC at LBA = 0x05ff9850 = 100636752
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 22 98 ff e5 00 1d+20:25:16.004 READ DMA EXT
25 00 00 22 96 ff e5 00 1d+20:25:16.003 READ DMA EXT
25 00 00 22 94 ff e5 00 1d+20:25:15.965 READ DMA EXT
25 00 00 22 92 ff e5 00 1d+20:25:15.539 READ DMA EXT
25 00 00 22 90 ff e5 00 1d+20:25:15.105 READ DMA EXT
Error 73 occurred at disk power-on lifetime: 58340 hours (2430 days + 20 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
-- -- -- -- -- -- --
40 51 00 80 17 74 04 Error: UNC at LBA = 0x04741780 = 74717056
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 08 7a 17 74 e4 00 1d+20:18:53.434 READ DMA
27 00 00 00 00 00 e0 00 1d+20:18:53.428 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 1d+20:18:53.425 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 1d+20:18:53.423 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 1d+20:18:53.423 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 72 occurred at disk power-on lifetime: 58340 hours (2430 days + 20 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
-- -- -- -- -- -- --
40 51 00 80 17 74 04 Error: UNC at LBA = 0x04741780 = 74717056
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 08 7a 17 74 e4 00 1d+20:18:48.817 READ DMA
c8 00 08 72 17 74 e4 00 1d+20:18:48.815 READ DMA
c8 00 08 6a 17 74 e4 00 1d+20:18:48.811 READ DMA
c8 00 08 62 17 74 e4 00 1d+20:18:48.808 READ DMA
c8 00 08 5a 17 74 e4 00 1d+20:18:48.806 READ DMA
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Selective Self-tests/Logging not supported
Eli tuollaisia virheilmoituksia tulee vain levystä sdc1. Muut levyt sda1, sda5 ja sdd vaikuttavat olevan virheettömiä.
Tuo sdc1 on se vanha 3 TB levy, jonka tiedot on jo siirretty levylle sdd. Jospa umounttaan sen sdc1:n?
-
Onkos sulla minkä aikakauden lankku koneessa? Itse täällä kirjoittelen P67 lankkuisella koneella ja siihen olisi ollut takaisinkutsu SATA-porttien osalta, mutta itsellä ei ole koskaan tullut ongelmia.
https://www.pcstats.com/articles/2589/index.html
Itse en reagoinut tuohon kummemmin. Ajattelin että laitan sitten erillisen SATA-kortin jos sattuu tarvis tuleen. Huomattavaa siis on, että kyseinen vika ei yleensä koske kaikkia portteja, vaan yleensä paria porttia.
-
Ja dmesg:istä vielä: SATA link speed:
[242105.367379] ata2.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[242105.367394] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[242147.974421] ata2.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[242147.974435] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[242168.581910] ata2.00: limiting SATA link speed to 3.0 Gbps
[242191.769457] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[242191.769472] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[268504.437644] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[268504.437660] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[268854.908080] ata2.00: limiting SATA link speed to 1.5 Gbps
[268890.207457] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[268890.207473] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[269322.942208] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[269322.942224] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
Onkohan tämä vakavaa? Mitä kannattaisi asialle tehdä? Eli SATA -levyjen siirtonopeus alenee koko ajan? Hmm? Emolevy hajoaa?
-
Onkos sulla minkä aikakauden lankku koneessa?
Mobo: Gigabyte model: H77-DS3H v: x.x serial: N/A BIOS: American Megatrends v: F9 date: 07/31/2013
Että sellainen.
-
Syslog kertoo:
Aug 7 06:08:06 ari udisksd[1407]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_W1F5D5F7: Error updating SMART data: sk_disk_smart_read_data: Input/output error (udisks-error-quark, 0)
Aug 7 06:08:06 ari kernel: [216091.615410] ata2.01: configured for UDMA/133
Aug 7 06:08:06 ari kernel: [216091.615434] ata2: EH complete
Se sanoo, että umountatun levyn siivous ei toimi... Onpa se nyt tarkkaa - eikö umount riitä? Hmm. Pitääkö tuo levy tosiaan irrottaa ihan fyysisesti pois koneesta?
-
Pitääkö tuo levy tosiaan irrottaa ihan fyysisesti pois koneesta?
Juu, pitää. Nappasin levystä SATA -piuhan irti, niin johan lakkasi koneen hidastelu. Eli kepillä sitten, jos ei porkkana auta...