Proponowałbym uważne czytanie co autor tematu w pierwszym poście napisał zamiast pisania tego
Ale nie wiemy czy DVD oryginalne z pudełka MS czy jakaś esperanza za 1 polski złoty nagrana w piwniczance…
A co to za różnica skoro jak twierdzi “pacjent”, nie działa.
Z tego co jest napisane, jest to sprzęt Della. Jesli, co podałem w linkach, próby naprawy nie przynoszą rezultatu to producent sugeruje skontaktowanie sie z nim.
Czy to dysk nie wiem ale skoro dwa zewnętrzne programy diagnostyczne, pierwszy uruchamiany z biosu a drugi z cd, nie potwierdziły awarii sprzętowej to pozostaje tylko sprawdzenie czy mozna wejśc w tryb awaryjny i z jego pozycji próbowac naprawy a jesli to niemożliwe to kontakt z producentem bo to on wie co on tam namotał w biosie i systemie. No i choćby po to by otrzymac sprawny instalator
Sprzęt na gwarancji czy już po?
Płyta DVD (za około 1zł) nagrywalna, kilkuletnia - inicjuje się proces otwierania instalatora ale nie wstaje. Kończy się czarnym tłem bez napisów.
Stara nagrywana , tania (1zł - 50gr) płyta CD z Windows XP bootuje się i otwiera instalator. Z tym, że ja nie chcę tu instalować XP bo to raczej zły pomysł.
Po gwarancji. 4 letni. Nowe to nie jest ale to chyba jeszcze nie taki straszny zabytek.
Ale tego nie zrobi, i jeszcze będzie masa wpisów, zamiast przywrócić tablice partycji.
ubuntu-mate@ubuntu-mate:~$ journalctl -q -b -p 3
kwi 07 13:05:54 ubuntu-mate kernel: sd 4:0:0:0: [sdb] No Caching mode page found
kwi 07 13:05:54 ubuntu-mate kernel: sd 4:0:0:0: [sdb] Assuming drive cache: wri>
kwi 07 13:05:54 ubuntu-mate kernel: ata1.00: exception Emask 0x0 SAct 0x1000 SE>
kwi 07 13:05:54 ubuntu-mate kernel: ata1.00: irq_stat 0x40000008
kwi 07 13:05:54 ubuntu-mate kernel: ata1: SError: { CommWake }
kwi 07 13:05:54 ubuntu-mate kernel: ata1.00: failed command: READ FPDMA QUEUED
kwi 07 13:05:54 ubuntu-mate kernel: ata1.00: cmd 60/40:60:f8:96:86/00:00:73:00:>
res 41/40:40:28:97:86/00:00:73:00:>
kwi 07 13:05:54 ubuntu-mate kernel: ata1.00: status: { DRDY ERR }
kwi 07 13:05:54 ubuntu-mate kernel: ata1.00: error: { UNC }
kwi 07 13:05:54 ubuntu-mate kernel: blk_update_request: I/O error, dev sda, sec>
kwi 07 13:05:54 ubuntu-mate systemd[1]: Failed unmounting /cdrom.
kwi 07 13:05:55 ubuntu-mate kernel: snd_hda_intel 0000:08:00.1: no codecs found!
kwi 07 13:05:56 ubuntu-mate kernel: Bluetooth: hci0: unexpected event for opcod>
kwi 07 13:06:22 ubuntu-mate pulseaudio[1924]: Failed to find a working profile.
kwi 07 13:06:22 ubuntu-mate pulseaudio[1924]: Failed to load module "module-als>
kwi 07 13:06:44 ubuntu-mate ubiquity[2038]: log-output -t ubiquity debconf-copy>
kwi 07 13:06:44 ubuntu-mate ubiquity[2038]: log-output -t ubiquity debconf-copy>
kwi 07 13:06:44 ubuntu-mate ubiquity[2038]: log-output -t ubiquity debconf-copy>
kwi 07 13:06:49 ubuntu-mate pulseaudio[1924]: Error opening PCM device front:1:>
kwi 07 13:06:49 ubuntu-mate pulseaudio[1924]: Error opening PCM device front:1:>
kwi 07 13:06:51 ubuntu-mate pulseaudio[4644]: Failed to find a working profile.
kwi 07 13:06:51 ubuntu-mate pulseaudio[4644]: Failed to load module "module-als>
lines 1-23
ubuntu-mate@ubuntu-mate:~$ journalctl -q -b -p 4…4
kwi 07 13:05:54 ubuntu-mate kernel: ACPI: NMI not connected to LINT 1!
kwi 07 13:05:54 ubuntu-mate kernel: ACPI: NMI not connected to LINT 1!
kwi 07 13:05:54 ubuntu-mate kernel: ACPI: NMI not connected to LINT 1!
kwi 07 13:05:54 ubuntu-mate kernel: ACPI: NMI not connected to LINT 1!
kwi 07 13:05:54 ubuntu-mate kernel: MDS CPU bug present and SMT on, data leak p>
kwi 07 13:05:54 ubuntu-mate kernel: #3
kwi 07 13:05:54 ubuntu-mate kernel: ENERGY_PERF_BIAS: Set to ‘normal’, was 'per>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: EISA: Cannot allocate reso>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: platform eisa.0: Cannot allocate resource f>
kwi 07 13:05:54 ubuntu-mate kernel: wmi_bus wmi_bus-PNP0C14:01: WQBC data block>
kwi 07 13:05:54 ubuntu-mate kernel: i2c_hid i2c-DLLC6AE:00: supply vdd not foun>
kwi 07 13:05:54 ubuntu-mate kernel: i2c_hid i2c-DLLC6AE:00: supply vddl not fou>
kwi 07 13:05:54 ubuntu-mate kernel: r8169 0000:07:00.0: can’t disable ASPM; OS >
kwi 07 13:05:54 ubuntu-mate kernel: MXM: GUID detected in BIOS
kwi 07 13:05:54 ubuntu-mate kernel: ACPI Warning: _SB.PCI0.RP05.PEGP._DSM: Arg>
kwi 07 13:05:54 ubuntu-mate kernel: i915 0000:00:02.0: can’t derive routing for>
lines 1-23
ubuntu-mate@ubuntu-mate:~$ smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.0-43-generic] (local build)
Copyright © 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Smartctl open device: /dev/sda failed: Permission denied
ubuntu-mate@ubuntu-mate:~$
ubuntu-mate@ubuntu-mate:~$ smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.0-43-generic] (local build)
Copyright © 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Smartctl open device: /dev/sda failed: Permission denied
ubuntu-mate@ubuntu-mate:~$
Najpierw ta komenda:
sudo su -Potem:
smartctl -a /dev/sdaCoś jest nie tak…
ubuntu-mate@ubuntu-mate:~$ sudo su -
root@ubuntu-mate:~# smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.0-43-generic] (local build)
Copyright © 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD…
Device Model: TOSHIBA MQ01ABD100
Serial Number: 251TT9SCT
LU WWN Device Id: 5 000039 611e004a7
Firmware Version: AX0P2D
User Capacity: 1 000 204 886 016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Apr 7 17:08:21 2021 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: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 120) 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: ( 246) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 128
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1691
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 5500
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1184
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 11
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 51
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 2890
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 29 (Min/Max 16/44)
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 179658833
200 Multi_Zone_Error_Rate 0x0032 100 100 000 Old_age Always - 598256021
240 Head_Flying_Hours 0x0032 087 087 000 Old_age Always - 5277
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 44268715577
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 67709225433
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 18269 (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 18269 occurred at disk power-on lifetime: 5500 hours (229 days + 4 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 41 18 a8 be 3f 40 Error: UNC at LBA = 0x003fbea8 = 4177576
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 18 a8 be 3f 40 00 03:59:46.785 READ FPDMA QUEUED
e5 00 00 00 00 00 00 00 03:59:45.950 CHECK POWER MODE
e5 00 00 00 00 00 00 00 03:59:40.947 CHECK POWER MODE
e5 00 00 00 00 00 00 00 03:59:35.949 CHECK POWER MODE
e5 00 00 00 00 00 00 00 03:59:30.950 CHECK POWER MODE
Error 18268 occurred at disk power-on lifetime: 5500 hours (229 days + 4 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 41 40 a8 be 3f 40 Error: UNC at LBA = 0x003fbea8 = 4177576
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 40 a8 be 3f 40 00 03:52:37.049 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:52:37.049 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 03:52:37.049 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 03:52:37.048 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 03:52:37.048 SET FEATURES [Set transfer mode]
Error 18267 occurred at disk power-on lifetime: 5500 hours (229 days + 4 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 41 28 a8 be 3f 40 Error: UNC at LBA = 0x003fbea8 = 4177576
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 28 a8 be 3f 40 00 03:52:33.208 READ FPDMA QUEUED
60 08 20 a8 37 a6 40 00 03:52:33.195 READ FPDMA QUEUED
60 08 18 b8 bc a9 40 00 03:52:33.181 READ FPDMA QUEUED
60 08 10 68 4f a4 40 00 03:52:33.155 READ FPDMA QUEUED
60 08 08 50 ac 2c 40 00 03:52:33.150 READ FPDMA QUEUED
Error 18266 occurred at disk power-on lifetime: 5496 hours (229 days + 0 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 41 60 28 97 86 40 Error: UNC at LBA = 0x00869728 = 8820520
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 40 60 f8 96 86 40 00 00:03:47.669 READ FPDMA QUEUED
60 20 58 d8 96 86 40 00 00:03:47.669 READ FPDMA QUEUED
60 08 50 d0 96 86 40 00 00:03:47.645 READ FPDMA QUEUED
60 08 48 60 29 82 40 00 00:03:47.645 READ FPDMA QUEUED
60 08 40 58 29 82 40 00 00:03:47.645 READ FPDMA QUEUED
Error 18265 occurred at disk power-on lifetime: 5496 hours (229 days + 0 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 41 60 58 0c 6d 40 Error: UNC at LBA = 0x006d0c58 = 7146584
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 60 58 0c 6d 40 00 00:03:05.000 READ FPDMA QUEUED
60 08 58 50 0c 6d 40 00 00:03:05.000 READ FPDMA QUEUED
60 08 50 48 0c 6d 40 00 00:03:05.000 READ FPDMA QUEUED
60 08 48 40 0c 6d 40 00 00:03:04.999 READ FPDMA QUEUED
60 08 40 38 0c 6d 40 00 00:03:04.999 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed without error 00% 5495 -
2 Short offline Completed without error 00% 5493 -
3 Short offline Aborted by host 90% 5493 -
4 Short offline Completed without error 00% 5493 -
5 Short offline Aborted by host 90% 5472 -
6 Short offline Completed without error 00% 5472 -
7 Short offline Aborted by host 40% 5471 -
8 Short offline Completed without error 00% 5471 -
9 Short offline Completed without error 00% 5470 -
#10 Short offline Completed without error 00% 97 -
#11 Short offline Completed without error 00% 81 -
#12 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.
root@ubuntu-mate:~#
jakie sudo su, jak odpalił live. pomyśl
popatrzę jak idzie.
może potem pomogę jak staniecie 
Smartctl open device: /dev/sda failed: Permission denied
Przeczytaj od początku 
Co wpisał po su? w live
jak te ubuntowate pozwalają na takie numery.
To OK
System z patyka i wchodzisz jak chcesz?
Myślnik “hyphen” powoduje zmianę zmiennych środowiskowych na te użytkownika, na którego się logujesz. W tym przypadku nieistotne, ale warto wiedzieć.
Tex nie lubi sudo, ale w repo chyba jest.
No a ja nie mam sudo
Nagrałem Film ----> https://www.youtube.com/watch?v=oPvP43gjEuw
Może są jeszcze inne narzędzia linuksowe do testu hdd ?