frank80
-
Posts
59 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by frank80
-
-
Hallo mgutt,
ich habe die „defekte“ HDD durch eine neue identische HDD ersetzt.
Hier bin ich nach der Anleitung aus dem Link von cz13 inkl. Punkt 7 vorgegangen.
SpoilerTo replace a failed disk or disks:
1. Stop the array.
2. Power down the unit.
3. Replace the failed disk(s) with a new one(s).
4. Power up the unit.
5. Assign the replacement disk(s) using the Unraid webGui.
6. Click the checkbox that says Yes I want to do this
7. (optional) Tick the box to start in Maintenance mode. If you start the array in Maintenance mode you will need to press the Sync button to trigger the rebuild. The advantage of doing this in Maintenance mode is that nothing else can write to the array while the rebuild is running which maximises speed. The disadvantage is that you cannot use the array in the meantime and until you return to normal mode cannot see what the contents of the disk being rebuilt will look like.
8. Click Start.to initiate the rebuild process.and the system will reconstruct the contents of the emulated didk(s) onto the new disk(s) and, if the new disk(s) is/are bigger, expand the file system.
1 hour ago, mgutt said:Mit einem klassischen Rebuild mit Disk Tausch stellt man sonst evtl einfach nur das kaputte Dateisystem wieder her.
Ich vermute, dass genau das passiert ist.
Die ausgebaute HDD habe ich einmal testweise per USB an meine Synology DS gestöpselt.
Hier kann ich auf alle Daten zugreifen und auch die vdiks löschen, die in unraid auf Read-Only standen.
Gruß Frank
-
Hallo zusammen,
so, hier ein ernüchterndes Update... 🙈
Das Rebuild ist fertig und ich habe unraid neu gestartet, nach ca. 10 Min. hatte ich die ersten Benachrichtigungen.
Die Fehler kamen in Dauerschleife bei Zugriff auf die Daten..
Feb 7 19:02:38 unraid kernel: BTRFS critical (device md1: state EA): unable to find logical 9455870400099729408 length 4096 Feb 7 19:02:38 unraid kernel: BTRFS critical (device md1: state EA): unable to find logical 9455870400099729408 length 16384 Feb 7 19:02:38 unraid kernel: BTRFS critical (device md1: state EA): unable to find logical 9455870400099729408 length 4096 Feb 7 19:02:38 unraid kernel: BTRFS critical (device md1: state EA): unable to find logical 9455870400099729408 length 16384 Feb 7 19:02:38 unraid kernel: BTRFS critical (device md1: state EA): unable to find logical 9455870400099729408 length 4096 Feb 7 19:02:38 unraid kernel: BTRFS critical (device md1: state EA): unable to find logical 9455870400099729408 length 16384Fix Common Problems
Feb 7 19:08:06 unraid root: Fix Common Problems: Error: Unable to write to disk1Was kann ich jetzt noch machen?
Gruß Frank
-
Hallo cz13,
danke für den Link!!
Das Rebuild läuft und ich habe mich für das "Normal replacement" mit der Option 7 entschieden.
Gruß und danke
Frank
-
Hallo zusammen,
ein kurzes Update.
Leider geht aktuell nicht mehr viel. Ich habe noch einmal eine Rsync-Sicherung gestartet, nach ca. 5 Std. war unraid nicht mehr erreichbar und ich musste den Rechner hart neu starten.
Als unraid wieder hochgefahren war, hat der Parity Check begonnen, was ebenfalls dazu geführt hat, dass unraid nach ein paar Stunden nicht mehr erreichbar war und ich wieder hart neu starten musste.
Was mir ebenfalls aufgefallen ist, es waren nicht nur die 2 vdisks, sondern mehrere Dateien die Read-Only sind.
So, heute ist meine neue HDD gekommen (brauchte sowieso eine), wie würdet ihr jetzt am besten vorgehen?
Array stop > HDD Defekt raus > Array start > Array stop > HDD neu rein > Array start ?
Gruß Frank
-
ich habe nur diesen Eintrag
Jan 30 21:25:10 unraid ool www[5434]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/disk1' '' -
Hallo mgutt,
20 hours ago, mgutt said:Dann ist vermutlich das Dateisystem hinüber
Das befürchte ich auch 😩
Hier das Log
SpoilerJan 29 13:24:30 unraid kernel: ata4: SATA max UDMA/133 abar m2048@0x51535000 port 0x51535280 irq 128
Jan 29 13:24:30 unraid kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 29 13:24:30 unraid kernel: ata4.00: ATA-10: TOSHIBA MG08ACA16TE, 0102, max UDMA/133
Jan 29 13:24:30 unraid kernel: ata4.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 32), AA
Jan 29 13:24:30 unraid kernel: ata4.00: Features: NCQ-prio
Jan 29 13:24:30 unraid kernel: ata4.00: configured for UDMA/133
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] 4096-byte physical blocks
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] Write Protect is off
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] Preferred minimum I/O size 4096 bytes
Jan 29 13:24:30 unraid kernel: sde: sde1
Jan 29 13:24:30 unraid kernel: sd 4:0:0:0: [sde] Attached SCSI disk
Jan 29 13:24:30 unraid kernel: BTRFS: device fsid 0c6db0b0-7bd0-48bd-890b-a9aab341325f devid 1 transid 203797 /dev/sde1 scanned by udevd (687)
Jan 29 13:26:43 unraid emhttpd: TOSHIBA_MG08ACA16TE_91T0A2J8FVGG (sde) 512 31251759104
Jan 29 13:26:43 unraid kernel: mdcmd (2): import 1 sde 64 15625879500 0 TOSHIBA_MG08ACA16TE_91T0A2J8FVGG
Jan 29 13:26:43 unraid kernel: md: import disk1: (sde) TOSHIBA_MG08ACA16TE_91T0A2J8FVGG size: 15625879500
Jan 29 13:26:43 unraid emhttpd: read SMART /dev/sde
Jan 29 13:44:42 unraid emhttpd: spinning down /dev/sde
Jan 29 13:57:01 unraid emhttpd: read SMART /dev/sde
Jan 29 14:12:14 unraid emhttpd: spinning down /dev/sde
Jan 29 14:23:30 unraid emhttpd: read SMART /dev/sde
Jan 29 14:38:31 unraid emhttpd: spinning down /dev/sde
Jan 29 15:00:01 unraid emhttpd: read SMART /dev/sde
Jan 29 15:16:02 unraid emhttpd: spinning down /dev/sde
Jan 29 15:33:06 unraid emhttpd: read SMART /dev/sde
Jan 29 15:48:07 unraid emhttpd: spinning down /dev/sde
Jan 29 17:04:32 unraid emhttpd: read SMART /dev/sde
Jan 29 17:29:50 unraid emhttpd: spinning down /dev/sde
Jan 29 20:25:00 unraid emhttpd: read SMART /dev/sde
Jan 29 20:40:13 unraid emhttpd: spinning down /dev/sde
Jan 29 23:30:26 unraid emhttpd: read SMART /dev/sde
Jan 29 23:45:41 unraid emhttpd: spinning down /dev/sde
Jan 30 00:31:23 unraid emhttpd: read SMART /dev/sde
Jan 30 00:46:24 unraid emhttpd: spinning down /dev/sde
Jan 30 07:45:52 unraid emhttpd: read SMART /dev/sde
Jan 30 08:11:56 unraid emhttpd: spinning down /dev/sde
Jan 30 11:40:00 unraid emhttpd: read SMART /dev/sde
Jan 30 11:55:01 unraid emhttpd: spinning down /dev/sde
Jan 30 14:40:01 unraid emhttpd: read SMART /dev/sde
Jan 30 14:55:02 unraid emhttpd: spinning down /dev/sde
Jan 30 19:27:57 unraid emhttpd: read SMART /dev/sde
Jan 30 19:43:11 unraid emhttpd: spinning down /dev/sde
Jan 30 19:53:18 unraid emhttpd: read SMART /dev/sde
Jan 30 20:15:11 unraid emhttpd: spinning down /dev/sde
Jan 30 20:18:06 unraid emhttpd: read SMART /dev/sde** Press ANY KEY to close this window **
20 hours ago, mgutt said:Jedenfalls wäre der erste Schritt ein Backup zu machen. Dann auf die Disk klicken und eine Reparatur versuchen (scrub).
Ein Backup habe ich gemacht.
Der scrub aus der GUI bringt keine Fehler, aber irgendwie glaube ich nicht das er funktioniert, weil er nach dem klick eigentlich auch schon wieder fertig ist.
UUID: 0c6db0b0-7bd0-48bd-890b-a9aab341325f Scrub started: Mon Jan 30 20:22:01 2023 Status: aborted Duration: 0:00:00 Total to scrub: 8.06TiB Rate: 0.00B/s Error summary: no errors found20 hours ago, mgutt said:Ist dir der Server mal abgeschmiert / hart ausgeschaltet? BTRFS ist da was empfindlich.
Ja, mir ist auch aufgefallen, dass unraid sich meistens beim Backup auf meine Unraid-Backupserver mit deinem Rsync-Script oder beim Backup auf den PBS verabschiedet.
-
Hallo mgutt,
Voll auf keinen Fall, ich habe noch über 6 TB frei.
root@unraid:~# df -h Filesystem Size Used Avail Use% Mounted on rootfs 16G 1.1G 15G 7% / tmpfs 32M 848K 32M 3% /run /dev/sda1 29G 3.7G 25G 13% /boot overlay 16G 1.1G 15G 7% /lib/firmware overlay 16G 1.1G 15G 7% /lib/modules devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 16G 0 16G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 684K 128M 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1 15T 8.1T 6.5T 56% /mnt/disk1 /dev/nvme0n1p1 932G 67G 865G 8% /mnt/cache /dev/sdb1 472G 86G 380G 19% /mnt/vm shfs 15T 8.1T 6.5T 56% /mnt/user0 shfs 15T 8.1T 6.5T 56% /mnt/user /dev/sdg1 932G 158G 774G 17% /mnt/disks/PBS-Backup /dev/loop2 30G 17G 13G 57% /var/lib/docker /dev/loop3 1.0G 5.0M 904M 1% /etc/libvirt tmpfs 3.2G 0 3.2G 0% /run/user/0 root@unraid:~#Löschen würde ich gerne, die vdisk´s sind halt Read-only.
root@unraid:/mnt/user/06_Backup# rm -r 11_ProxmoxBackupServer rm: cannot remove '11_ProxmoxBackupServer/Debian/vdisk2.img': Read-only file system rm: cannot remove '11_ProxmoxBackupServer/PBS/vdisk2.img': Read-only file system root@unraid:/mnt/user/06_Backup#1 hour ago, mgutt said:Und warum ist deine Vdisk 1TB groß?!?!
Ich habe eine VM mit Proxmox Backup Server für meine Proxmox VE Server.
Da meine PVE`s auch je 1 TB haben und ich noch genug TB´s habe, warum nicht?
Gruß Frank
-
Hallo liebes Forum,
ich brauche mal eure Hilfe.
Fix Common Problems hatte mir gestern eine rote Fehlermeldung angezeigt.
Unable to write to disk1Ich glaube, es handelt sich um 2 vdisk Dateien.
root@unraid:/mnt/user/06_Backup/11_ProxmoxBackupServer/Debian# ls -lh total 4.0K -rwxrwxrwx 1 nobody users 1.0T Feb 27 2022 vdisk2.img* ----------- root@unraid:/mnt/user/06_Backup/11_ProxmoxBackupServer/PBS# ls -lh total 337G -rwxrwxrwx 1 root users 1.0T Jan 26 01:50 vdisk2.img*Die VM´s habe ich gesichert und die vdisks könnte man löschen.
Kann mir jemand sagen, wie ich das Problem lösen kann?
Gruß Frank
-
Wenn der USB-Stick eine Macke hätte, müsste ich dann nicht auch andere Probleme haben.
Das System läuft ca. 1 Jahr und als Stick habe ich einen SanDisk Cruzer Fit USB-2.0 mit 32Gbit.
Kann man den Stick prüfen?
-
Die HDD ist über einen Wechselrahmen im Servergehäuse angeschlossen, also schon über SATA.
-
Hallo mgutt,
22 minutes ago, mgutt said:Hast du das Passwort in den UD Einstellungen hinterlegt? Das ist unabhängig vom Array Passwort.
das Passwort habe ich in UD hinterlegt. Mein Array ist nicht verschlüsselt.
20 minutes ago, mgutt said:Und ist das das Keyfile was UD lädt?
Scheinbar nicht.
Ich habe schon mehrere Stunden damit verbracht, eine Lösung zu finden und mich danach durchgehangelt.
Das YT-Video ist von 2019, ich glaube, da konnte man noch nicht über UD verschlüsseln. (mein Englisch ist nicht sonderlich gut)
26 minutes ago, mgutt said:Enthält dein Passwort Zeichen, welche auf einer englischen Tastatur woanders liegen könnten?
Erst hatte ich einen Passwortgenerator benutzt, nach der zweiten Formatierung hat das Passwort Buchstaben, Zahlen, @ und _.
Ich konnte die HDD vor dem Reboot mounten und unmounten. Dann sollten das Passwort funktionieren, denke ich.
29 minutes ago, mgutt said:Hast du das Dateisystem über Unraid verschlüsselt und wenn ja warum nutzt du für die Entschlüsselung die Kommandozeile?
Ja, die HDD ist über unRAID formatiert und verschlüsselt.
Auf die Kommandozeile bin ich erst im Video gekommen, dort hat es so funktioniert.
Gruß Frank
-
Hallo zusammen,
ich habe ein ähnliches Problem.
Ich habe meine Backupstrategie etwas geändert, bzw. teste gerade meinen besten Weg.In meine unRaid-Server habe ich ein Wechselrahmen mit einer HDD, diese ist mit btrfs-encrypt formatiert, mit einem Passwort verschlüsselt und in Unassigned Devices-Plugin eingetragen.
Wird unRAID neu gestartet, kann ich die HDD nicht mehr mounten. Erst dachte ich, dass ich ein falsches Passwort eingegeben habe.
Also habe ich die HDD neu formatiert und ein neues Passwort vergeben und im Plugin eingetragen.
Mount und unmount funktioniert, wieder die Daten mit dem Script von mgutt angestoßen und 2 Tage gewartet.
Nach einem Reboot kann ich die HDD wieder nicht mounten.
Nov 13 11:42:26 unraid unassigned.devices: Adding partition 'BackupHDD'... Nov 13 11:42:26 unraid unassigned.devices: Mounting partition 'BackupHDD' at mountpoint '/mnt/disks/BackupHDD'... Nov 13 11:42:26 unraid unassigned.devices: Using disk password to open the 'crypto_LUKS' device. Nov 13 11:42:28 unraid unassigned.devices: luksOpen result: No key available with this passphrase. Nov 13 11:42:28 unraid unassigned.devices: Partition 'X1X0A0U7FVGG' cannot be mounted.In einem YT-Video habe ich gesehen, dass man das keyfile neu erstellen kann (/root/keyfile).
root@unraid:~# echo -n "Passwort" > keyfile #Ausgabe... root@unraid:~# cat keyfile Passwort@unraid:~#Leider alles ohne Erfolg.
Das habe ich ebenfalls ohne Erfolg versucht...
root@unraid:~# /usr/sbin/cryptsetup luksOpen /dev/sdh1 BackupHDD --allow-discards --key-file=/root/keyfile No key available with this passphrase. ## /usr/local/sbin/emcmd 'cmdCryptsetup=luksOpen /dev/sdh1 BackupHDD --allow-discards'Habt Ihr noch eine Idee?
Gruß Frank
-
Hallo,
ich habe die HDD jetzt noch einmal mit diesem Befehl überschrieben. (sdX natürlich angepasst)
dd if=/dev/zero of=/dev/sdX bs=4096 status=progressOn 10/5/2022 at 10:59 AM, DataCollector said:unraid (encrypted)
habe ich bei mir nicht gemacht.
Danke noch einmal für eure Hilfe 👍
-
Guten Morgen zusammen,
wie löscht oder nullt ihr HDD´s richtig?
Ich habe jetzt 3 Durchgänge mit Eraser und 1 Durchgang mit WipeDisk.
EaseUS data Recovery findet immer noch Dateien.
-noVNCMozillaFirefox.png.353e31f293e09f296512af419236b829.png)
-
Hallo mgutt,
danke für die Info, ich habe Syslog jetzt aktiviert.
Gestern Morgen war unraid auch nicht mehr erreichbar, auch direkt am Monitor hatte ich keine Reaktion.
Es half nur noch ein Reset, dann kam der Parity-Check, als dieser heute fertig war, hat er ihn noch einmal gestartet.
Bei der Platte habe ich aktuell wieder keine Fehler, das ist echt verrückt.
Ich hoffe, ich bekomme die Platte ohne Probleme getauscht.
Spoilerroot@unraid:~# smartctl -a /dev/sdd
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG08ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG08ACA16TE
Serial Number: X1N0A0KSFVGG
LU WWN Device Id: 5 000039 b38da0a4f
Firmware Version: 0102
User Capacity: 16,000,900,661,248 bytes [16.0 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-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Sep 26 18:51:24 2022 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: 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: ( 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: (1428) 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: 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 0x000b 100 095 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8188
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1614
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 5463
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 91
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 28
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1903
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 39 (Min/Max 20/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 001 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 218759176
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1464
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 528
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 5193 hours (216 days + 9 hours)
When the command that caused the error occurred, the device was in standby mode.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 43 18 c8 e2 01 40 Error: UNC at LBA = 0x0001e2c8 = 123592Commands 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 a0 90 f8 01 40 00 7d+00:14:44.584 READ FPDMA QUEUED
60 40 98 50 f3 01 40 00 7d+00:14:42.334 READ FPDMA QUEUED
60 40 90 10 ee 01 40 00 7d+00:14:42.331 READ FPDMA QUEUED
60 40 88 d0 e8 01 40 00 7d+00:14:42.326 READ FPDMA QUEUED
60 40 80 90 e3 01 40 00 7d+00:14:42.323 READ FPDMA QUEUEDSMART 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% 5367 -
# 2 Extended captive Interrupted (host reset) 90% 5267 -
# 3 Extended offline Interrupted (host reset) 90% 5267 -
# 4 Extended offline Aborted by host 90% 5232 -
# 5 Short offline Completed without error 00% 5228 -
# 6 Short offline Completed without error 00% 5191 -
# 7 Extended offline Aborted by host 90% 5180 -
# 8 Short offline Completed without error 00% 5179 -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. -
2 minutes ago, hawihoney said:
Du hast offensichtlich eine sehr hohe Leidens-Toleranz was Deine Platte(n) angeht
Naja, wie man es nimmt, ich habe aktuell ziemlich viel um die Ohren, das lenkt etwas ab 😅
Ich habe jetzt ein Reset gemacht und unraid ist wieder da.
Aktuell läuft der Parity-Check.
Ich habe die Platte beim Händler reklamiert, ist ja bis 2026 Garantie drauf!
Gruß und danke für eure Hilfe!
-
Hallo,
nein. Er hängt beim booten, wie man auf dem Bild sieht.
Ich glaube da hilft nur noch ein Reset?!
-
Hallo,
wie lange geht so eine diagnostics collection, seit Donnerstag habe ich immer noch das gleiche Bild wie oben gepostet?
Auf die Tastatur wird nicht reagiert. -
Hallo Members,
ja, das ist die gleiche Platte.
Also doch Toshiba anschreiben.
Unraid hat sich wenigstens am Schalter ausschalten lassen.
Jetzt hängt er zwar an Starting diagnostics collection, würde aber mal abwarten was passiert.
-
Hallo zusammen,
ich glaube, ich habe mich zu frühe gefreut.
Jetzt habe ich diesen Fehler und unRAID ist aktuell nicht erreichbar 😩
198 Offline_Uncorrectable 0x0030 001 001 000 Old_age Offline - 418Spoilerroot@unraid:~# smartctl -a /dev/sdd
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG08ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG08ACA16TE
Serial Number: X1N0A0KSFVGG
LU WWN Device Id: 5 000039 b38da0a4f
Firmware Version: 0102
User Capacity: 16,000,900,661,248 bytes [16.0 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-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Sep 22 20:23:23 2022 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: PASSEDGeneral SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: ( 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: (1428) 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: 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 0x000b 100 095 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8188
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1614
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 5369
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 91
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 28
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1902
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 33 (Min/Max 20/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 001 001 000 Old_age Offline - 418
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 119668737
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1373
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 535
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 5193 hours (216 days + 9 hours)
When the command that caused the error occurred, the device was in standby mode.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 43 18 c8 e2 01 40 Error: UNC at LBA = 0x0001e2c8 = 123592Commands 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 a0 90 f8 01 40 00 7d+00:14:44.584 READ FPDMA QUEUED
60 40 98 50 f3 01 40 00 7d+00:14:42.334 READ FPDMA QUEUED
60 40 90 10 ee 01 40 00 7d+00:14:42.331 READ FPDMA QUEUED
60 40 88 d0 e8 01 40 00 7d+00:14:42.326 READ FPDMA QUEUED
60 40 80 90 e3 01 40 00 7d+00:14:42.323 READ FPDMA QUEUEDSMART 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% 5367 -
# 2 Extended captive Interrupted (host reset) 90% 5267 -
# 3 Extended offline Interrupted (host reset) 90% 5267 -
# 4 Extended offline Aborted by host 90% 5232 -
# 5 Short offline Completed without error 00% 5228 -
# 6 Short offline Completed without error 00% 5191 -
# 7 Extended offline Aborted by host 90% 5180 -
# 8 Short offline Completed without error 00% 5179 -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. -
Ok, danke euch für die Hilfe!!
-
Hallo,
bis jetzt habe ich keine Fehler mehr erhalten.
Ich habe vorgestern einen smartctl long Test gestartet.
Hier werden, bis auf den
Error 1 occurred at disk power-on lifetime: 5193 hours (216 days + 9 hours)keine Fehler mehr angezeigt.
Spoilerroot@unraid:~# smartctl -a /dev/sdd
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG08ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG08ACA16TE
Serial Number: X1N0A0KSFVGG
LU WWN Device Id: 5 000039 b38da0a4f
Firmware Version: 0102
User Capacity: 16,000,900,661,248 bytes [16.0 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-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Sep 19 22:06:19 2022 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: PASSEDGeneral SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 41) The self-test routine was interrupted
by the host with a hard or soft reset.
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: (1428) 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: 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 0x000b 100 095 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8206
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1591
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 5299
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 91
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 28
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1879
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 25 (Min/Max 20/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 119668737
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1356
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 536
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 5193 hours (216 days + 9 hours)
When the command that caused the error occurred, the device was in standby mode.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 43 18 c8 e2 01 40 Error: UNC at LBA = 0x0001e2c8 = 123592Commands 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 a0 90 f8 01 40 00 7d+00:14:44.584 READ FPDMA QUEUED
60 40 98 50 f3 01 40 00 7d+00:14:42.334 READ FPDMA QUEUED
60 40 90 10 ee 01 40 00 7d+00:14:42.331 READ FPDMA QUEUED
60 40 88 d0 e8 01 40 00 7d+00:14:42.326 READ FPDMA QUEUED
60 40 80 90 e3 01 40 00 7d+00:14:42.323 READ FPDMA QUEUEDSMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended captive Interrupted (host reset) 90% 5267 -
# 2 Extended offline Interrupted (host reset) 90% 5267 -
# 3 Extended offline Aborted by host 90% 5232 -
# 4 Short offline Completed without error 00% 5228 -
# 5 Short offline Completed without error 00% 5191 -
# 6 Extended offline Aborted by host 90% 5180 -
# 7 Short offline Completed without error 00% 5179 -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.Was haltet ihr davon, sollte ich Toshiba mal anschreiben?
Gruß Frank
-
Guten Abend zusammen und danke für eure Hilfe. 👍
Als Nächstes werde ich Folgendes versuchen;
- Powertop in der /boot/config/go auskommentieren
- reboot
- Write corrections to parity deaktivieren
- Parity-Check läuft bereits (der letzte Check wurde vor 30 Min. beendet und ergab keine Fehler etc.)
Gruß Frank
Nachtrag;
die Fehler auf der Startseite sind jetzt auch wieder weg, siehe Bild...
-
Hallo,
1 hour ago, hawihoney said:Wie passt das zeitlich? Von wann sind die Errors und von wann smartctl.
Eigentlich in der Zeitfolge, wie ich geschrieben bzw. geantwortet habe.
- Current pending sector = 418
- Array Error´s (1024)
- Current pending sector = 0
Die beiden Ergebnisse von smartctl habe ich direkt vor dem Schreiben im Forum ausgelesen.
ca. 11 Uhr
Spoilersmartctl;
root@unraid:~# smartctl -a /dev/sdd
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG08ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG08ACA16TE
Serial Number: X1N0A0KSFVGG
LU WWN Device Id: 5 000039 b38da0a4f
Firmware Version: 0102
User Capacity: 16,000,900,661,248 bytes [16.0 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-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Sep 15 10:42:06 2022 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: PASSEDGeneral SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: ( 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: (1428) 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: 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 0x000b 100 095 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8109
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1567
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 5191
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 91
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 28
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1855
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 41 (Min/Max 20/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 418
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 270139429
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1299
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 534
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0SMART Error Log Version: 1
No Errors LoggedSMART 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% 5191 -
# 2 Extended offline Aborted by host 90% 5180 -
# 3 Short offline Completed without error 00% 5179 -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.17:21 Uhr
Spoilerroot@unraid:~# smartctl -a /dev/sdd
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG08ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG08ACA16TE
Serial Number: X1N0A0KSFVGG
LU WWN Device Id: 5 000039 b38da0a4f
Firmware Version: 0102
User Capacity: 16,000,900,661,248 bytes [16.0 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-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Sep 15 17:22:04 2022 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: PASSEDGeneral SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: ( 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: (1428) 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: 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 0x000b 100 095 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8109
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1567
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 5198
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 91
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 28
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1855
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 40 (Min/Max 20/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 270139429
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1306
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 534
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 5193 hours (216 days + 9 hours)
When the command that caused the error occurred, the device was in standby mode.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 43 18 c8 e2 01 40 Error: UNC at LBA = 0x0001e2c8 = 123592Commands 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 a0 90 f8 01 40 00 7d+00:14:44.584 READ FPDMA QUEUED
60 40 98 50 f3 01 40 00 7d+00:14:42.334 READ FPDMA QUEUED
60 40 90 10 ee 01 40 00 7d+00:14:42.331 READ FPDMA QUEUED
60 40 88 d0 e8 01 40 00 7d+00:14:42.326 READ FPDMA QUEUED
60 40 80 90 e3 01 40 00 7d+00:14:42.323 READ FPDMA QUEUEDSMART 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% 5191 -
# 2 Extended offline Aborted by host 90% 5180 -
# 3 Short offline Completed without error 00% 5179 -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.Das interessante ist der SMART Error Log
ca. 11 Uhr
SMART Error Log Version: 1 No Errors Loggedund 17:21
SMART Error Log Version: 1 ATA Error Count: 1
-noVNCMozillaFirefox.png.353e31f293e09f296512af419236b829.png)
vdisk Read-only file system vdisk
in Deutsch
Posted · Edited by frank80
Das versuche ich morgen einmal.
Es hat keinen Unterschied gemacht.
Es ist als wäre die „defekte“ HDD im Array. Wie du weiter oben im Post auch schreibst, habe ich wieder ein defektes Dateisystem.