Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
ok!? das mit gksudo war mir nicht klar, wo ist das Problem (ich habe jetzt gksudo gezogen)? cdparanoia -A ergibt nach ewiger Wartezeit (hab 10 min gewartet, er hängt immer noch bei der letzten Zeile "MMC style command set") cdparanoia III release 10.2 (September 11, 2008)
Using cdda library version: 10.2
Using paranoia library version: 10.2
Checking /dev/cdrom for cdrom...
Could not stat /dev/cdrom: No such file or directory
Checking /dev/cdroms/cdrom0 for cdrom...
Could not stat /dev/cdroms/cdrom0: No such file or directory
Checking /dev/cdroms/cdroma for cdrom...
Could not stat /dev/cdroms/cdroma: No such file or directory
Checking /dev/cdroms/cdrom1 for cdrom...
Could not stat /dev/cdroms/cdrom1: No such file or directory
Checking /dev/cdroms/cdromb for cdrom...
Could not stat /dev/cdroms/cdromb: No such file or directory
Checking /dev/cdroms/cdrom2 for cdrom...
Could not stat /dev/cdroms/cdrom2: No such file or directory
Checking /dev/cdroms/cdromc for cdrom...
Could not stat /dev/cdroms/cdromc: No such file or directory
Checking /dev/cdroms/cdrom3 for cdrom...
Could not stat /dev/cdroms/cdrom3: No such file or directory
Checking /dev/cdroms/cdromd for cdrom...
Could not stat /dev/cdroms/cdromd: No such file or directory
Checking /dev/hd0 for cdrom...
Could not stat /dev/hd0: No such file or directory
Checking /dev/hda for cdrom...
Could not stat /dev/hda: No such file or directory
Checking /dev/hd1 for cdrom...
Could not stat /dev/hd1: No such file or directory
Checking /dev/hdb for cdrom...
Could not stat /dev/hdb: No such file or directory
Checking /dev/hd2 for cdrom...
Could not stat /dev/hd2: No such file or directory
Checking /dev/hdc for cdrom...
Could not stat /dev/hdc: No such file or directory
Checking /dev/hd3 for cdrom...
Could not stat /dev/hd3: No such file or directory
Checking /dev/hdd for cdrom...
Could not stat /dev/hdd: No such file or directory
Checking /dev/sg0 for cdrom...
Testing /dev/sg0 for SCSI/MMC interface
Could not access device /dev/sg0 to test for SG_IO support: Permission denied
no SG_IO support for device: /dev/sg0
Could not access device /dev/sg0: Permission denied
generic device: /dev/sg0
ioctl device: not found
Could not open generic SCSI device /dev/sg0: Permission denied
Testing /dev/sg0 for cooked ioctl() interface
/dev/sg0 is not a cooked ioctl CDROM.
Checking /dev/sga for cdrom...
Could not stat /dev/sga: No such file or directory
Checking /dev/sg1 for cdrom...
Testing /dev/sg1 for SCSI/MMC interface
Could not access device /dev/sg1 to test for SG_IO support: Permission denied
no SG_IO support for device: /dev/sg1
Could not access device /dev/sg1: Permission denied
generic device: /dev/sg1
ioctl device: not found
Could not open generic SCSI device /dev/sg1: Permission denied
Testing /dev/sg1 for cooked ioctl() interface
/dev/sg1 is not a cooked ioctl CDROM.
Checking /dev/sgb for cdrom...
Could not stat /dev/sgb: No such file or directory
Checking /dev/sg2 for cdrom...
Testing /dev/sg2 for SCSI/MMC interface
SG_IO device: /dev/sg2
CDROM model sensed sensed: MATSHITA BD-CMB UJ-120 1.00
Checking for SCSI emulation...
Drive is ATAPI (using SG_IO host adaptor emulation)
Checking for MMC style command set...
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19610
Wohnort: Schleswig-Holstein
|
Kannst mit Strg+C abbrechen. Lese bei zeiten mal hier wegen sudo 😉 https://wiki.ubuntuusers.de/sudo/ Wir testen mal eine andere Bootoption GRUB_CMDLINE_LINUX_DEFAULT="noplymouth acpi_osi=Linux" Dann wieder sudo update-grub Neustart
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
cdparanoia III release 10.2 (September 11, 2008)
Using cdda library version: 10.2
Using paranoia library version: 10.2
Checking /dev/cdrom for cdrom...
Could not stat /dev/cdrom: No such file or directory
Checking /dev/cdroms/cdrom0 for cdrom...
Could not stat /dev/cdroms/cdrom0: No such file or directory
Checking /dev/cdroms/cdroma for cdrom...
Could not stat /dev/cdroms/cdroma: No such file or directory
Checking /dev/cdroms/cdrom1 for cdrom...
Could not stat /dev/cdroms/cdrom1: No such file or directory
Checking /dev/cdroms/cdromb for cdrom...
Could not stat /dev/cdroms/cdromb: No such file or directory
Checking /dev/cdroms/cdrom2 for cdrom...
Could not stat /dev/cdroms/cdrom2: No such file or directory
Checking /dev/cdroms/cdromc for cdrom...
Could not stat /dev/cdroms/cdromc: No such file or directory
Checking /dev/cdroms/cdrom3 for cdrom...
Could not stat /dev/cdroms/cdrom3: No such file or directory
Checking /dev/cdroms/cdromd for cdrom...
Could not stat /dev/cdroms/cdromd: No such file or directory
Checking /dev/hd0 for cdrom...
Could not stat /dev/hd0: No such file or directory
Checking /dev/hda for cdrom...
Could not stat /dev/hda: No such file or directory
Checking /dev/hd1 for cdrom...
Could not stat /dev/hd1: No such file or directory
Checking /dev/hdb for cdrom...
Could not stat /dev/hdb: No such file or directory
Checking /dev/hd2 for cdrom...
Could not stat /dev/hd2: No such file or directory
Checking /dev/hdc for cdrom...
Could not stat /dev/hdc: No such file or directory
Checking /dev/hd3 for cdrom...
Could not stat /dev/hd3: No such file or directory
Checking /dev/hdd for cdrom...
Could not stat /dev/hdd: No such file or directory
Checking /dev/sg0 for cdrom...
Testing /dev/sg0 for SCSI/MMC interface
Could not access device /dev/sg0 to test for SG_IO support: Permission denied
no SG_IO support for device: /dev/sg0
Could not access device /dev/sg0: Permission denied
generic device: /dev/sg0
ioctl device: not found
Could not open generic SCSI device /dev/sg0: Permission denied
Testing /dev/sg0 for cooked ioctl() interface
/dev/sg0 is not a cooked ioctl CDROM.
Checking /dev/sga for cdrom...
Could not stat /dev/sga: No such file or directory
Checking /dev/sg1 for cdrom...
Testing /dev/sg1 for SCSI/MMC interface
Could not access device /dev/sg1 to test for SG_IO support: Permission denied
no SG_IO support for device: /dev/sg1
Could not access device /dev/sg1: Permission denied
generic device: /dev/sg1
ioctl device: not found
Could not open generic SCSI device /dev/sg1: Permission denied
Testing /dev/sg1 for cooked ioctl() interface
/dev/sg1 is not a cooked ioctl CDROM.
Checking /dev/sgb for cdrom...
Could not stat /dev/sgb: No such file or directory
Checking /dev/sg2 for cdrom...
Could not stat /dev/sg2: No such file or directory
Checking /dev/sgc for cdrom...
Could not stat /dev/sgc: No such file or directory
Checking /dev/sg3 for cdrom...
Could not stat /dev/sg3: No such file or directory
Checking /dev/sgd for cdrom...
Could not stat /dev/sgd: No such file or directory
Checking /dev/cdu31a for cdrom...
Could not stat /dev/cdu31a: No such file or directory
Checking /dev/cdu535 for cdrom...
Could not stat /dev/cdu535: No such file or directory
Checking /dev/sbpcd for cdrom...
Could not stat /dev/sbpcd: No such file or directory
Checking /dev/sbpcd0 for cdrom...
Could not stat /dev/sbpcd0: No such file or directory
Checking /dev/sbpcda for cdrom...
Could not stat /dev/sbpcda: No such file or directory
Checking /dev/sbpcd1 for cdrom...
Could not stat /dev/sbpcd1: No such file or directory
Checking /dev/sbpcdb for cdrom...
Could not stat /dev/sbpcdb: No such file or directory
Checking /dev/sbpcd2 for cdrom...
Could not stat /dev/sbpcd2: No such file or directory
Checking /dev/sbpcdc for cdrom...
Could not stat /dev/sbpcdc: No such file or directory
Checking /dev/sbpcd3 for cdrom...
Could not stat /dev/sbpcd3: No such file or directory
Checking /dev/sbpcdd for cdrom...
Could not stat /dev/sbpcdd: No such file or directory
Checking /dev/sonycd for cdrom...
Could not stat /dev/sonycd: No such file or directory
Checking /dev/mcd for cdrom...
Could not stat /dev/mcd: No such file or directory
Checking /dev/sjcd for cdrom...
Could not stat /dev/sjcd: No such file or directory
Checking /dev/cm206cd for cdrom...
Could not stat /dev/cm206cd: No such file or directory
Checking /dev/gscd for cdrom...
Could not stat /dev/gscd: No such file or directory
Checking /dev/optcd for cdrom...
Could not stat /dev/optcd: No such file or directory
No cdrom drives accessible to albert found.
also kein CDROM? Ich sehe den Test auf /dev/sr0 nicht?
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19610
Wohnort: Schleswig-Holstein
|
Der Test Fragt aber alle Optionen ab, zum gegen Vergleich cdrecord -toc aber meine Hoffnung für dieses Laufwerk schwindet ☹
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
cdparanoia III release 10.2 (September 11, 2008)
Using cdda library version: 10.2
Using paranoia library version: 10.2
Checking /dev/cdrom for cdrom...
Could not stat /dev/cdrom: No such file or directory
Checking /dev/cdroms/cdrom0 for cdrom...
Could not stat /dev/cdroms/cdrom0: No such file or directory
Checking /dev/cdroms/cdroma for cdrom...
Could not stat /dev/cdroms/cdroma: No such file or directory
Checking /dev/cdroms/cdrom1 for cdrom...
Could not stat /dev/cdroms/cdrom1: No such file or directory
Checking /dev/cdroms/cdromb for cdrom...
Could not stat /dev/cdroms/cdromb: No such file or directory
Checking /dev/cdroms/cdrom2 for cdrom...
Could not stat /dev/cdroms/cdrom2: No such file or directory
Checking /dev/cdroms/cdromc for cdrom...
Could not stat /dev/cdroms/cdromc: No such file or directory
Checking /dev/cdroms/cdrom3 for cdrom...
Could not stat /dev/cdroms/cdrom3: No such file or directory
Checking /dev/cdroms/cdromd for cdrom...
Could not stat /dev/cdroms/cdromd: No such file or directory
Checking /dev/hd0 for cdrom...
Could not stat /dev/hd0: No such file or directory
Checking /dev/hda for cdrom...
Could not stat /dev/hda: No such file or directory
Checking /dev/hd1 for cdrom...
Could not stat /dev/hd1: No such file or directory
Checking /dev/hdb for cdrom...
Could not stat /dev/hdb: No such file or directory
Checking /dev/hd2 for cdrom...
Could not stat /dev/hd2: No such file or directory
Checking /dev/hdc for cdrom...
Could not stat /dev/hdc: No such file or directory
Checking /dev/hd3 for cdrom...
Could not stat /dev/hd3: No such file or directory
Checking /dev/hdd for cdrom...
Could not stat /dev/hdd: No such file or directory
Checking /dev/sg0 for cdrom...
Testing /dev/sg0 for SCSI/MMC interface
Could not access device /dev/sg0 to test for SG_IO support: Permission denied
no SG_IO support for device: /dev/sg0
Could not access device /dev/sg0: Permission denied
generic device: /dev/sg0
ioctl device: not found
Could not open generic SCSI device /dev/sg0: Permission denied
Testing /dev/sg0 for cooked ioctl() interface
/dev/sg0 is not a cooked ioctl CDROM.
Checking /dev/sga for cdrom...
Could not stat /dev/sga: No such file or directory
Checking /dev/sg1 for cdrom...
Testing /dev/sg1 for SCSI/MMC interface
Could not access device /dev/sg1 to test for SG_IO support: Permission denied
no SG_IO support for device: /dev/sg1
Could not access device /dev/sg1: Permission denied
generic device: /dev/sg1
ioctl device: not found
Could not open generic SCSI device /dev/sg1: Permission denied
Testing /dev/sg1 for cooked ioctl() interface
/dev/sg1 is not a cooked ioctl CDROM.
Checking /dev/sgb for cdrom...
Could not stat /dev/sgb: No such file or directory
Checking /dev/sg2 for cdrom...
Testing /dev/sg2 for SCSI/MMC interface
SG_IO device: /dev/sg2
CDROM model sensed sensed: MATSHITA BD-CMB UJ-120 1.00
Checking for SCSI emulation...
Drive is ATAPI (using SG_IO host adaptor emulation)
Checking for MMC style command set...
Drive is MMC style
DMA scatter/gather table entries: 167
table entry size: 131072 bytes
maximum theoretical transfer: 9185 sectors
Setting default read size to 27 sectors (63504 bytes).
Verifying CDDA command set...
Expected command set FAILED!
Performing full probe for CDDA command set...
test -> density: [none ] command: [28 0x,00]
Drive rejected read command packet(s)
test -> density: [yes/0x00] command: [28 0x,00]
Drive rejected read command packet(s)
test -> density: [yes/0x04] command: [28 0x,00]
Drive rejected density set
test -> density: [yes/0x82] command: [28 0x,00]
Drive rejected density set
test -> density: [yes/0x81] command: [28 0x,00]
Drive rejected density set
test -> density: [none ] command: [a8 0x,00]
Drive rejected read command packet(s)
test -> density: [yes/0x00] command: [a8 0x,00]
Drive rejected read command packet(s)
test -> density: [yes/0x04] command: [a8 0x,00]
Drive rejected density set
test -> density: [yes/0x82] command: [a8 0x,00]
Drive rejected density set
test -> density: [yes/0x81] command: [a8 0x,00]
Drive rejected density set
test -> density: [none ] command: [be 02,10]
Drive rejected read command packet(s)
test -> density: [none ] command: [be 02,f8]
Drive rejected read command packet(s)
test -> density: [none ] command: [be 06,f8]
^C
dort hings er seitdem wieder...habe mit CTRL-C abgebrochen zweiter Terminal, cdrecord-toc ergab wieder
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/sr0
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19610
Wohnort: Schleswig-Holstein
|
Mal eine "ganz Blöde" abfrage dpkg -l | grep libsgutils2
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
ii libsgutils2-2 1.40-0ubuntu1 amd64 utilities for devices using the SCSI command set (shared libraries)
habe die CD wieder rausgenommen: aus dem Lauferks-tool verschwindet der Eintrag des "Blockmediums"
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19610
Wohnort: Schleswig-Holstein
|
Wäre ja auch zu schön gewesen ☹ Ok,muss mich mal versuchen schlau zu machen,melde mich denn.Ist der Pc denn so nutzbar?
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
jau bis auf die Endlosschleife im Hintergrund und das CD Laufwerk alles Bestens - habe natürlich noch nichts getestet. Internet, Office Libre, Terminal, Rhythmbox usw. geht alles flüssig bzw. mit grosser Leichtigkeit (im Vergleich zum Windows vorher) Danke nochmal! Und gute Nacht erst mal ☺
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19610
Wohnort: Schleswig-Holstein
|
Wünsche ich auch ☺ Irgendwie müssen wir die Firmware 1.04 da mal drauf dreschen 😬
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19610
Wohnort: Schleswig-Holstein
|
Versuchen wir vorher noch mal diese Bootopion GRUB_CMDLINE_LINUX_DEFAULT="noplymouth edd=on" sowie GRUB_CMDLINE_LINUX="elevator=cfq" wieder sudo update-grub Neustart
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
Mist jabe ich zu spät gesehen - wollte nochmal schauen, wie es mit dem Kabel aussieht (auch wenn das Laufwerk ja problemlos unter Windows läuft). Der Ausbau ist nahe an unmöglich mit Heimmitteln. Ich habe hier jetzt die Eingewiede rumliegen und muss grad zum Laden um Wärmeleitpaste zu kaufen (...nicht fragen bitte) bevor ich den Rechner wieder anwerfen kann. Wird wohl heute abend. Weiss jemand wo ich so ein Sata Kabel herkriegte? In der Kombination (beide Enden Buchse) habe ich im Web nichts gefunden. Die Platte ist eine WD3200BEVT, SN WXEZ08SE6305
- Bilder
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
Ok, Rechner läuft wie vor dem Zerlegen - Conrad hatte das Sata Kabel nicht. grub sieht jetzt so aus: # If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth edd=on"
GRUB_CMDLINE_LINUX="elevator=cfq"
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480 und der update ergab identischen output. Also alles beim alten: das System flutscht, die Endlosschleife im Hintergrund und das LAufwerk sehe ich nicht.
|
Dogeater
Anmeldungsdatum: 16. Juni 2015
Beiträge: 3381
|
Wie mein ein paar Seiten vorheriggehend geposteter Link andeutet, brauchst du einen zweiten Sata-Controller, damit du meine Problemlösung nachstellen kannst. Die Stelle, wo ich... ja deswegen hatte ich gesagt, werf das Gerät in die Tonne. Sorry, bin manchmal etwas enthusiastisch. Ich glaube das sieht schlecht aus für deinen Lappi. Der kann mit Windows, ... aber er kann wohl nicht anders. Interessant wäre aber jetzt:
Selbe HDD + Selbes BD-Rom + ECHTES Mainboard + NEUES Satakabel.
Achja, und es kann eben DOCH auch ein unerkannter bad sector sein.
https://www.youtube.com/watch?v=Z0QhVIR2gtE Möglicherweise verursacht durch Fly errors, die durch eine Unwucht im Motor ausgelöst werden, deswegen fragte ich nach den Daten aus dem SMART. Aber im Windows die Smartwerte auslesen, das ist ja zuuu schwierig. CrystalDiskInfo ist ganz, ganz schwer zu bedienen. Davon ab, dass es smartctl und GSmartControl auch für Windows gibt. Hier: http://www.chip.de/downloads/Smartmontools_13014927.html Ist schon ok, dein Kopf war mit tausend Dingen schon voll. Dennoch.. auch dies kannst du nun nachholen. Wenn du magst.
|
Korkenzieher
(Themenstarter)
Anmeldungsdatum: 17. April 2017
Beiträge: 59
|
Habe jetzt smartctl installiert, anbei der output. Was ich interessant fand, ist das Gsmart sofort das CD Laufwerk anzeigt, d.h. das Laufwerk an sich wird vom System ja "gesehen". Außer der etwas hohen HD Temperatur fiel mir nichts ungewöhnliches auf, die letzten 5 Fehler sind alle ewig her. Ich werde mir noch das HD Diagnosetool von WD besorgen (Windows) und schauen ob damit weitere Infos zu kriegen sind (denke aber nicht). Das mit der Option offline data collection ist mir noch nicht ganz klar: kann man da weitere Tests durchführen oder ist das eher gedacht für ein echtes monitoring, Tests in regelmässigen Intervallen (z.B. alle x Stunden) für die reguläre Festplattenwartung? smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.8.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD3200BEVT-22ZCT0
Serial Number: WD-WXEZ08SE6305
LU WWN Device Id: 5 0014ee 257c1538b
Firmware Version: 11.01A11
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.5, 3.0 Gb/s
Local Time is: Sun May 21 10:46:56 2017 CEST
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: ( 9960) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 118) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 118
3 Spin_Up_Time 0x0027 187 186 021 Pre-fail Always - 1625
4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3446
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5614
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3367
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 457
193 Load_Cycle_Count 0x0032 157 157 000 Old_age Always - 131788
194 Temperature_Celsius 0x0022 096 091 000 Old_age Always - 51
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 102 (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 102 occurred at disk power-on lifetime: 3699 hours (154 days + 3 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 d1 61 9d 40 Error: WP at LBA = 0x009d61d1 = 10314193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 20 38 36 00 00 00 03:34:47.058 WRITE FPDMA QUEUED
61 08 98 60 82 60 00 00 03:34:47.057 WRITE FPDMA QUEUED
60 08 90 c8 f9 24 17 00 03:34:47.057 READ FPDMA QUEUED
60 08 88 b8 04 78 10 00 03:34:47.057 READ FPDMA QUEUED
60 08 80 68 86 26 17 00 03:34:47.057 READ FPDMA QUEUED
Error 101 occurred at disk power-on lifetime: 3699 hours (154 days + 3 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 d1 61 9d 40 Error: WP at LBA = 0x009d61d1 = 10314193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 98 10 48 a4 11 00 03:34:43.636 WRITE FPDMA QUEUED
61 08 98 40 99 08 00 00 03:34:43.635 WRITE FPDMA QUEUED
60 08 90 c8 f9 24 17 00 03:34:43.635 READ FPDMA QUEUED
60 08 88 b8 04 78 10 00 03:34:43.635 READ FPDMA QUEUED
60 08 80 68 86 26 17 00 03:34:43.635 READ FPDMA QUEUED
Error 100 occurred at disk power-on lifetime: 3699 hours (154 days + 3 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 d1 61 9d 40 Error: WP at LBA = 0x009d61d1 = 10314193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 88 78 9b 08 00 00 03:34:40.091 WRITE FPDMA QUEUED
61 08 90 78 9b 08 00 00 03:34:40.090 WRITE FPDMA QUEUED
61 08 88 08 48 a4 11 00 03:34:40.090 WRITE FPDMA QUEUED
61 18 90 48 99 08 00 00 03:34:40.090 WRITE FPDMA QUEUED
61 08 88 18 48 a4 11 00 03:34:40.090 WRITE FPDMA QUEUED
Error 99 occurred at disk power-on lifetime: 3699 hours (154 days + 3 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 d1 61 9d 40 Error: UNC at LBA = 0x009d61d1 = 10314193
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 80 30 e0 52 9d 1d 00 03:34:36.701 READ FPDMA QUEUED
61 20 90 c0 9a 08 00 00 03:34:36.701 WRITE FPDMA QUEUED
61 20 88 48 8b a4 11 00 03:34:36.701 WRITE FPDMA QUEUED
60 08 80 68 86 26 17 00 03:34:36.701 READ FPDMA QUEUED
60 00 78 60 69 9d 1d 00 03:34:36.701 READ FPDMA QUEUED
Error 98 occurred at disk power-on lifetime: 3699 hours (154 days + 3 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 d1 61 9d 40 Error: WP at LBA = 0x009d61d1 = 10314193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 88 10 48 a4 11 00 03:34:33.424 WRITE FPDMA QUEUED
61 08 88 40 99 08 00 00 03:34:33.424 WRITE FPDMA QUEUED
60 08 80 68 86 26 17 00 03:34:33.424 READ FPDMA QUEUED
60 00 78 60 69 9d 1d 00 03:34:33.423 READ FPDMA QUEUED
60 00 70 60 68 9d 1d 00 03:34:33.423 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 5614 -
# 2 Short offline Completed without error 00% 5612 -
# 3 Short offline Completed without error 00% 5604 -
# 4 Extended offline Aborted by host 90% 5604 -
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. Edit:
Die Info von CrystalDisk habe ich per screenshot angehängt und liefert exakt die gleiche Info wie das Ubuntu-onboard-tool "Laufwerke" die ich vorher schon gepostet hatte - es liess sich lediglich schön sehen das während des 2-h-Tests die Temperatur anstieg, insofern mache ich mir keine Gedanken über die 51°C die smartctl ausspuckte. Auch das offizielle WD Diagnosetool brachte keinen neue Info zutage. Für beides habe ich screenshots angehängt. Insgesamt liefen jetzt 2 intensive 2-h-Tests und 3 kurze Tests über die Platte, alle ohne irgendeinen Befund.
- Bilder
|