Wednesday, January 11, 2023

Seagate ST980813ASG SMART

smartctl --all /dev/sda                    (Prints all SMART information)


smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.0-15-generic] (local build)

Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org


=== START OF INFORMATION SECTION ===

Model Family:     Seagate Momentus 7200.2

Device Model:     ST980813ASG

Serial Number:    ########

Firmware Version: 3.ADD

User Capacity:    80,026,361,856 bytes [80.0 GB]

Sector Size:      512 bytes logical/physical

Device is:        In smartctl database 7.3/5319

ATA Version is:   ATA/ATAPI-7 (minor revision not indicated)

Local Time is:    Wed Jan 11 17:43:23 2023 UTC

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: FAILED!

Drive failure expected in less than 24 hours. SAVE ALL DATA.

See vendor-specific Attribute list for failed Attributes.


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:      ( 119) The previous self-test completed having

the read element of the test failed.

Total time to complete Offline 

data collection: (  426) seconds.

Offline data collection

capabilities: (0x5b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities:            (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability:        (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine 

recommended polling time: (   2) minutes.

Extended self-test routine

recommended polling time: (  84) minutes.

SCT capabilities:        (0x0035) SCT Status supported.

SCT Feature Control supported.

SCT Data Table supported.


SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0

  3 Spin_Up_Time            0x0003   099   099   085    Pre-fail  Always       -       0

  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1480

  5 Reallocated_Sector_Ct   0x0033   001   001   036    Pre-fail  Always   FAILING_NOW 31952

  7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       8853334264

  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       17405

 10 Spin_Retry_Count        0x0013   100   100   034    Pre-fail  Always       -       0

 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       2079

187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       5259

189 High_Fly_Writes         0x003a   098   098   000    Old_age   Always       -       2

190 Airflow_Temperature_Cel 0x0022   060   031   045    Old_age   Always   In_the_past 40 (Min/Max 24/43)

191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       10

192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1844

193 Load_Cycle_Count        0x0022   001   001   000    Old_age   Always       -       234936

194 Temperature_Celsius     0x001a   040   069   000    Old_age   Always       -       40 (0 12 0 0 0)

195 Hardware_ECC_Recovered  0x0012   073   061   000    Old_age   Always       -       137350076

197 Current_Pending_Sector  0x0010   100   097   000    Old_age   Offline      -       11

198 Offline_Uncorrectable   0x003e   100   097   000    Old_age   Always       -       11

199 UDMA_CRC_Error_Count    0x0000   200   200   000    Old_age   Offline      -       1

200 Multi_Zone_Error_Rate   0x0032   100   253   000    Old_age   Always       -       0

202 Data_Address_Mark_Errs  0x0000   100   253   000    Old_age   Offline      -       0

240 Head_Flying_Hours       0x0000   000   000   000    Old_age   Offline      -       17217 (111 247 0)

241 Total_LBAs_Written      0x0000   000   000   000    Old_age   Offline      -       11734329995

242 Total_LBAs_Read         0x0000   000   000   000    Old_age   Offline      -       170874401

254 Free_Fall_Sensor        0x0000   001   001   000    Old_age   Offline      -       513


SMART Error Log Version: 1

ATA Error Count: 6887 (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 6887 occurred at disk power-on lifetime: 17395 hours (724 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

  -- -- -- -- -- -- --

  40 51 01 f5 d0 4f e0  Error: UNC at LBA = 0x004fd0f5 = 5230837


  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  42 00 01 f5 d0 4f e0 00      00:43:10.020  READ VERIFY SECTOR(S) EXT

  42 00 01 f4 d0 4f e0 00      00:43:10.005  READ VERIFY SECTOR(S) EXT

  42 00 02 f4 d0 4f e0 00      00:43:09.596  READ VERIFY SECTOR(S) EXT

  42 00 04 f4 d0 4f e0 00      00:43:09.194  READ VERIFY SECTOR(S) EXT

  42 00 04 f0 d0 4f e0 00      00:43:09.179  READ VERIFY SECTOR(S) EXT


Error 6886 occurred at disk power-on lifetime: 17395 hours (724 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

  -- -- -- -- -- -- --

  40 51 01 f4 d0 4f e0  Error: UNC at LBA = 0x004fd0f4 = 5230836


  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  42 00 01 f4 d0 4f e0 00      00:43:10.020  READ VERIFY SECTOR(S) EXT

  42 00 02 f4 d0 4f e0 00      00:43:10.005  READ VERIFY SECTOR(S) EXT

  42 00 04 f4 d0 4f e0 00      00:43:09.596  READ VERIFY SECTOR(S) EXT

  42 00 04 f0 d0 4f e0 00      00:43:09.194  READ VERIFY SECTOR(S) EXT

  42 00 08 f0 d0 4f e0 00      00:43:09.179  READ VERIFY SECTOR(S) EXT


Error 6885 occurred at disk power-on lifetime: 17395 hours (724 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

  -- -- -- -- -- -- --

  40 51 02 f4 d0 4f e0  Error: UNC at LBA = 0x004fd0f4 = 5230836


  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  42 00 02 f4 d0 4f e0 00      00:43:10.020  READ VERIFY SECTOR(S) EXT

  42 00 04 f4 d0 4f e0 00      00:43:10.005  READ VERIFY SECTOR(S) EXT

  42 00 04 f0 d0 4f e0 00      00:43:09.596  READ VERIFY SECTOR(S) EXT

  42 00 08 f0 d0 4f e0 00      00:43:09.194  READ VERIFY SECTOR(S) EXT

  42 00 10 f0 d0 4f e0 00      00:43:09.179  READ VERIFY SECTOR(S) EXT


Error 6884 occurred at disk power-on lifetime: 17395 hours (724 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

  -- -- -- -- -- -- --

  40 51 04 f4 d0 4f e0  Error: UNC at LBA = 0x004fd0f4 = 5230836


  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  42 00 04 f4 d0 4f e0 00      00:43:10.020  READ VERIFY SECTOR(S) EXT

  42 00 04 f0 d0 4f e0 00      00:43:10.005  READ VERIFY SECTOR(S) EXT

  42 00 08 f0 d0 4f e0 00      00:43:09.596  READ VERIFY SECTOR(S) EXT

  42 00 10 f0 d0 4f e0 00      00:43:09.194  READ VERIFY SECTOR(S) EXT

  42 00 10 e0 d0 4f e0 00      00:43:09.179  READ VERIFY SECTOR(S) EXT


Error 6883 occurred at disk power-on lifetime: 17395 hours (724 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

  -- -- -- -- -- -- --

  40 51 04 f4 d0 4f e0  Error: UNC at LBA = 0x004fd0f4 = 5230836


  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  42 00 08 f0 d0 4f e0 00      00:43:07.134  READ VERIFY SECTOR(S) EXT

  42 00 10 f0 d0 4f e0 00      00:43:07.129  READ VERIFY SECTOR(S) EXT

  42 00 10 e0 d0 4f e0 00      00:43:09.596  READ VERIFY SECTOR(S) EXT

  42 00 20 e0 d0 4f e0 00      00:43:09.194  READ VERIFY SECTOR(S) EXT

  42 00 20 c0 d0 4f e0 00      00:43:09.179  READ VERIFY SECTOR(S) EXT


SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline       Completed: read failure       70%     11805         116337475

# 2  Short offline       Interrupted (host reset)      10%       330         -

# 3  Short offline       Completed without error       00%         1         -

# 4  Short offline       Completed without error       00%         0         -


SMART Selective self-test log data structure revision number 1

 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

    1        0        0  Not_testing

    2        0        0  Not_testing

    3        0        0  Not_testing

    4        0        0  Not_testing

    5        0        0  Not_testing

Selective self-test flags (0x0):

  After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay. 

Windows Command Prompt

shutdown –r –t 10 => reboot in 10 sec

shutdown –s –t 30 => shutdown after 30 sec

Tuesday, January 10, 2023

Error code 0x80070035 the network path not found solution

https://thegeekpage.com/turn-windows-features-on-or-off-blank-or-empty/

https://softwarekeep.com/help-center/how-to-fix-windows-resource-protection-could-not-start-the-repair-service


C:\Windows\system32>sfc /scannow

Windows Resource Protection could not start the repair service.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.

Verification 33% complete.


C:\Windows\system32>Dism /online /Get-Features /format:table | find "SMB1Protocol"

SMB1Protocol                                 | Enabled

SMB1Protocol-Client                          | Enabled

SMB1Protocol-Server                          | Enabled

SMB1Protocol-Deprecation                     | Enabled

SMB1Protocol can be enabled in Turn Windows Features On / Off.

Enabled SMB 1.0/CIFS Client, which made Windows 10 see all network PCs with Error code 0x80070035.

FOLLOWING COMMAND SOLVED the problem and gave access to shares:

C:\Windows\system32>

reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /f 


https://winitpro.ru/index.php/2018/05/16/0x80070035-ne-najden-setevoj-put-windows-10/

Sunday, January 8, 2023

Flash Asus H170 PRO GAMING BIOS with flashrom

sudo flashrom -p internal

flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)

flashrom is free software, get the source code at https://flashrom.org


Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found chipset "Intel H170".

This chipset is marked as untested. If you are using an up-to-date version

of flashrom *and* were (not) able to successfully update your firmware with it,

then please email a report to flashrom@flashrom.org including a verbose (-V) log.

Thank you!

Enabling flash write... Warning: BIOS region SMM protection is enabled!

Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.

New value is 0xaa.

SPI Configuration is locked down.

FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.

FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.

Not all flash regions are freely accessible by flashrom. This is most likely

due to an active ME. Please see https://flashrom.org/ME for details.

At least some flash regions are read protected. You have to use a flash

layout and include only accessible regions. For write operations, you'll

additionally need the --noverify-all switch. See manpage for more details.

Enabling hardware sequencing because some important opcode is locked.

PROBLEMS, continuing anyway

Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

No operations were specified.


-------------------------------------------------------------------------------

sudo flashrom -p internal -r /home/bk1.bin

flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)

flashrom is free software, get the source code at https://flashrom.org


Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found chipset "Intel H170".

This chipset is marked as untested. If you are using an up-to-date version

of flashrom *and* were (not) able to successfully update your firmware with it,

then please email a report to flashrom@flashrom.org including a verbose (-V) log.

Thank you!

Enabling flash write... Warning: BIOS region SMM protection is enabled!

Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.

New value is 0xaa.

SPI Configuration is locked down.

FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.

FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.

Not all flash regions are freely accessible by flashrom. This is most likely

due to an active ME. Please see https://flashrom.org/ME for details.

At least some flash regions are read protected. You have to use a flash

layout and include only accessible regions. For write operations, you'll

additionally need the --noverify-all switch. See manpage for more details.

Enabling hardware sequencing because some important opcode is locked.

PROBLEMS, continuing anyway

Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

Reading flash... Transaction error between offset 0x00003000 and 0x0000303f (= 0x00003000 + 63)!

Read operation failed!

FAILED.


-------------------------------------------------------------------------------

sudo flashrom --programmer internal -r /home/bk1.bin -i bios --ifd

sudo flashrom -p internal -r /home/bk2.bin -i bios --ifd

sudo flashrom -p internal -r /home/bk3.bin -i bios --ifd

sudo flashrom -p internal -r /home/bk4.bin -i bios --ifd


sudo flashrom -p internal -v /home/bk4.bin -i bios --ifd


md5sum bk1.bin bk2.bin bk3.bin bk4.bin a3403.bin

8dccbad887dc112574a8999713029b7a  bk1.bin

8dccbad887dc112574a8999713029b7a  bk2.bin

8dccbad887dc112574a8999713029b7a  bk3.bin

8dccbad887dc112574a8999713029b7a  bk4.bin

058bce361fd03ef3f9de2285dd12e5b4  a3403.bin

-------------------------------------------------------------------------------


sudo flashrom -p internal -w /home/a3403.bin -i bios --ifd --noverify-all

flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)

flashrom is free software, get the source code at https://flashrom.org


Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found chipset "Intel H170".

This chipset is marked as untested. If you are using an up-to-date version

of flashrom *and* were (not) able to successfully update your firmware with it,

then please email a report to flashrom@flashrom.org including a verbose (-V) log.

Thank you!

Enabling flash write... Warning: BIOS region SMM protection is enabled!

Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.

New value is 0xaa.

SPI Configuration is locked down.

FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.

FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.

Not all flash regions are freely accessible by flashrom. This is most likely

due to an active ME. Please see https://flashrom.org/ME for details.

At least some flash regions are read protected. You have to use a flash

layout and include only accessible regions. For write operations, you'll

additionally need the --noverify-all switch. See manpage for more details.

Enabling hardware sequencing because some important opcode is locked.

PROBLEMS, continuing anyway

Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

Reading ich descriptor... done.

Using region: "bios".

Reading old flash chip contents... done.

Erasing and writing flash chip... Transaction error between offset 0x00280000 and 0x00280fff (= 0x00280000 + 4095)!

Reading current flash chip contents... done. Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

No usable erase functions left.

FAILED!

Uh oh. Erase/write failed.

Your flash chip is in an unknown state.

Get help on IRC at chat.freenode.net (channel #flashrom) or

mail flashrom@flashrom.org with the subject "FAILED: <your board name>"!

-------------------------------------------------------------------------------

DO NOT REBOOT OR POWEROFF!

root@kubuntu:/home#


https://x86sec.com/posts/2022/09/08/removing-intel-ME-on-x1-carbon/

Flash BIOS with flashrom on Linux

Boot Kubuntu from USB drive.

sudo dmidecode -s bios-release-date

sudo dmidecode -s bios-revision

sudo dmidecode -s bios-vendor

sudo dmidecode -s bios-version

sudo apt install flashrom

-r dump1.bin => read chip and save content into file

-r dump2.bin

-r dump3.bin

md5sum dump1.bin dump2.bin dump3.bin

Hashes SHOULD BE identical.

-E => erase chip content

-w firmware.bin => write file content to chip

flashrom -p ch341a_spi -c GD25B128ACPIG -w firmware.bin

Friday, January 6, 2023

Asus H170 PRO GAMING BIOS is not displayed

Current BIOS: H170-PRO-GAMING-ASUS-3403

https://www.asus.com/supportonly/h170_pro_gaming/helpdesk_bios/

Problem: BIOS is not displayed, can’t enter BIOS, cursor/underscore on black screen.

Cause: unknown. PC stayed some time unused and then this… Power on PC and it shows black screen with non-blinking cursor, then monitor blinks and you get same black screen with non-blinking cursor. Tried on old and new TFT monitors with DP, HDMI, VGA, DVI-D – same. Tried on discrete video – same.

Potential cause: low CMOS KTS battery - 2.6 V - may have corrupted BIOS.


I can boot from USB WinPE without any problems and see hardware with utilities, if no OS is installed on any HDD or SSD.

Windows PE => CMD with admin rights => shutdown /r /fw /f /t 0 

I can boot from Win 10 USB and install Windows 10 on HDD or M.2 SSD, but after install Windows won’t boot. You get same black screen with non-blinking cursor.

I can’t enter BIOS by pressing F2 or Del, but Ctrl+Alt+Del reboots PC without problems.

When entering UEFI BIOS from Kubuntu USB GRUB menu PC turns off and then restarts.


I can’t flash BIOS with BUPDATER or AFUDOS.

With BUPDATER PC simply reboots or proposes to secure flash and reboots.

With AFUDOS I get message that BIOS is write protected. Can’t backup it and can’t flash it.

I changed battery, unplugged devices, removed CPU, tried another PSU, changed memory modules, reset CMOS many times but nothing helps. Looks like BIOS is working because with service utilities booted from USB drive I can see sensors, all specs, test video and cpu, hdd and ssd are visible, etc… But I can't enter BIOS.

BIOS chip flash solved the problem. Used buggy CH341A black USB 5V adapter, CH341-USB/CH341WDM.INF driver, UEFITool.exe, AsProgrammer_2.0.3a, Windows 7.

AFTER 3805 BIOS flash LAN Intel Ethernet Connection (2) I219-LM  stopped working!!!

Flashed 3403 BIOS again!

Asus H170 PRO GAMING BIOS chip model: GD25B128CPIG E6S556 AH1644

Asus H170 PRO GAMING BIOS chip photo:

Asus H170 PRO GAMING BIOS photo image


https://forums.overclockers.ru/viewtopic.php?f=89&t=624998&sid=a223bad92cdc077b857d1b7c0b16eb3f&start=20

https://forums.mydigitallife.net/threads/ami-bios-seems-write-protected-how-to-disable-or-circumvent-this.23932/

https://rog.asus.com/forum/showthread.php?99490-Flash-any-most-Asus-motherboard-Bios-in-DOS-with-USB-tutorial-Intel-AMD-roll-back

https://winraid.level1techs.com/t/asus-h170-pro-bios-recovery/31530

https://www.youtube.com/watch?v=BYXKOo4sJqM

https://www.youtube.com/watch?v=dpjs4-B7HPU

https://www.youtube.com/watch?v=Z9IuCtNuakE

https://github.com/corna/me_cleaner/issues/98

https://www.cryptoprofi.info/?p=10901

https://i2hard.ru/publications/30697/

https://greentechreviews.ru/2020/09/09/vosstanovlenie-bios-v-domashnih-i-okolo-togo-usloviyah/

https://www.wimsbios.com/amiflasher.jsp#gsc.tab=0

https://robotchip.ru/obzor-programmatora-dlya-flash-i-eeprom-na-ch341a/

https://forums.overclockers.ru/viewtopic.php?f=1&t=23980&start=9260

Install CH341A drivers and AsProgrammer_2.0.3a on Windows.

Install flashrom on Linux. [ You may also need libftdi1-2, libusb-0.1-4 ]

3200Mhz XMP RAM issue with CPU cooler going loud

Після зміни частоти памяті чи ввімкнення профілю XMP оперативної памяті, вентилятор процесора підвищив оберти і став шалено шуміти.

Змінивши профіль, перейдіть у Hardware Monitor і настройте криві кулера чи просто змініть до значень за замовчуванням, в даному випадку клавішею D.