hm, okay - bin extra lange aufgeblieben: das Ding ist jetzt durch. Schaut auch einigermaßen Vielversprechend aus. Lange Zeit hat sich so gut wie nix getan (bis ca 65%), dann ging es auf einmal ab in der Konsole.
Ich poste nur ungern die kompletten Inhalt der Ausgabe, da dort auch einige persönliche Dateien (YEAH!) aufgelistet waren. Außerdem ist es elendig lang - knapp 16.000 Zeilen!
Ich versuche mal, das Wesentliche zu posten:
[~] # e2fsck -C 0 -p /dev/md0/dev/md0 contains a file system with errors, check forced./dev/md0: Entry 'tab-strip-bg.png' in /.qpkg/photostation2/lib/ext/resources/images/gray/tabs (55009293) has deleted/unused inode 139796592. answer=1CLEARED./dev/md0: Entry 'tab-btm-inactive-left-bg.gif' in /.qpkg/photostation2/lib/ext/resources/images/gray/tabs (55009293) has deleted/unused inode 139796584. answer=1CLEARED..../dev/md0: Entry 'ezcode.js' in /.qpkg/photostation2/m/javascripts/auth (55009392) has deleted/unused inode 140623946. answer=1CLEARED.Entry 'Klettern' in /Public/tunix (138657832) has deleted/unused inode 139862040. answer=1CLEARED./dev/md0: Entry 'MAIL-Archiv' in /Public/tunix (138657832) has deleted/unused inode 140541981. answer=1CLEARED.
hier kommt ne Reihe bekannter Ordner Immer das slebe Muster. Manchmal ist auch folgendes dabei
Entry '..' in ??? (140771332) has deleted/unused inode 140632065. answer=1 CLEARED./dev/md0: Entry '..' in ??? (141090817) has deleted/unused inode 140951555. answer=1CLEARED..../dev/md0: Entry '..' in ??? (152248322) has deleted/unused inode 140541983. answer=1CLEARED.Problem in HTREE directory inode 1286145: node (1) has bad max hash /dev/md0: Problem in HTREE directory inode 1286145: node (2) has bad min hash/dev/md0: Problem in HTREE directory inode 1286145: node (2) has bad max hash/dev/md0: Problem in HTREE directory inode 1286145: node (3) has bad min hash/dev/md0: Problem in HTREE directory inode 1286145: node (3) has bad max hash/dev/md0: Problem in HTREE directory inode 1286145: node (4) has bad min hash/dev/md0: Problem in HTREE directory inode 1286145: node (5) has bad min hash/dev/md0: Problem in HTREE directory inode 1286145: node (5) has bad max hash/dev/md0: Problem in HTREE directory inode 1286145: node (6) has bad min hash/dev/md0: Problem in HTREE directory inode 1286145: node (6) has bad max hash/dev/md0: Invalid HTREE directory inode 1286145 (/.@mysql). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 16637964: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 16637964: node (2) has bad min hash/dev/md0: Problem in HTREE directory inode 16637964: node (2) has bad max hash...//// so geht es dann mehrer hundert Zeilen weiter bis: .../dev/md0: Problem in HTREE directory inode 16637964: node (376) has bad min hash/dev/md0: Problem in HTREE directory inode 16637964: node (376) has bad max hash/dev/md0: Problem in HTREE directory inode 16637964: node (377) has bad min hash/dev/md0: Problem in HTREE directory inode 16637964: node (377) has bad max hash
Dannkommt wieder ein längerer Abschnitt, der so aussieht
/dev/md0: Invalid HTREE directory inode 16637964 (/.timemachine/tunixs iMac.sparsebundle/bands). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 38813719: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 38813719: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 38813719 (/Qweb/_phpMyAdmin). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 38813916: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 38813916: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 38813916 (/Qweb/__alt/_ermisch/images/fotographie). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 38815219: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 38815219: node (2) has bad min hash/dev/md0: Problem in HTREE directory inode 38815219: node (3) has bad min hash/dev/md0: Problem in HTREE directory inode 38815219: node (3) has bad max hash/dev/md0: Invalid HTREE directory inode 38815219 (/Qweb/_phpMyAdmin/libraries). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 38823819: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 38823819: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 38823819 (/Qweb/_phpMyAdmin/themes/original/img). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 38839492: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 38839492: node (2) has bad min hash/dev/md0: Problem in HTREE directory inode 38839492: node (3) has bad min hash/dev/md0: Problem in HTREE directory inode 38839492: node (3) has bad max hash/dev/md0: Invalid HTREE directory inode 38839492 (/Qweb/_phpMyAdmin/themes/pmahomme/img). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 55017770: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 55017770: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 55017770 (/.qpkg/LogitechMediaServer/lib). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 55232080: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 55232080: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 55232080 (/.qpkg/LogitechMediaServer/lib/perl5/5.10.0/unicore/lib/gc_sc). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 75202561: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 75202561: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 75202561 (/Qmultimedia/Musik/Unbekannter Interpret/Unbekanntes Album). answer=1HTREE INDEX CLEARED./dev/md0: Problem in HTREE directory inode 75587696: node (1) has bad max hash.../dev/md0: Problem in HTREE directory inode 142516225: node (1) has bad max hash/dev/md0: Problem in HTREE directory inode 142516225: node (2) has bad min hash/dev/md0: Invalid HTREE directory inode 142516225 (...). answer=1HTREE INDEX CLEARED.
Auch hier tauchen ein paar persönliche Daten auf (z.B. _ermisch).
Der folgende Abschnitt geht ca. 200 Zeilen lang und sieht so aus
Unconnected directory inode 139591681 (...) answer=1RECONNECTED./dev/md0: Unconnected directory inode 140247041 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140640257 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140640269 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140640305 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140640307 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140640315 (...)answer=1RECONNECTED.Unconnected directory inode 140641179 (...) answer=1RECONNECTED./dev/md0: Unconnected directory inode 140746773 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140771332 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 140771389 (...)answer=1RECONNECTED.Unconnected directory inode 141090817 (...) answer=1RECONNECTED..../dev/md0: Unconnected directory inode 152248321 (...)answer=1RECONNECTED./dev/md0: Unconnected directory inode 152248322 (...)answer=1RECONNECTED.
Jetzt kommt was (für mich) Schönes Ich sehe viele FIXED
Unattached inode 95412225 answer=1RECONNECTED./dev/md0: Inode 95412225 ref count is 2, should be 1. answer=1FIXED./dev/md0: Unattached inode 95412226answer=1RECONNECTED./dev/md0: Inode 95412226 ref count is 2, should be 1. answer=1FIXED./dev/md0: Unattached inode 95412227answer=1RECONNECTED./dev/md0: Inode 95412227 ref count is 2, should be 1. answer=1FIXED..../dev/md0: Unattached inode 102301705answer=1RECONNECTED./dev/md0: Inode 102301705 ref count is 2, should be 1. answer=1FIXED.Inode 138657832 ref count is 10, should be 5. answer=1 FIXED./dev/md0: Inode 138657833 ref count is 3, should be 2. answer=1FIXED./dev/md0: Inode 138657835 ref count is 7, should be 6. answer=1FIXED./dev/md0: Inode 138657839 ref count is 23, should be 9. answer=1FIXED./dev/md0: Inode 139452417 ref count is 5, should be 4. answer=1FIXED./dev/md0: Unattached inode 139460641answer=1RECONNECTED./dev/md0: Inode 139460641 ref count is 2, should be 1. answer=1FIXED..../dev/md0: Unattached inode 139460700answer=1RECONNECTED./dev/md0: Inode 139460700 ref count is 2, should be 1. answer=1FIXED./dev/md0: Inode 139591681 ref count is 12, should be 9. answer=1FIXED./dev/md0: Inode 140099587 ref count is 8, should be 7. answer=1FIXED./dev/md0: Inode 140247041 ref count is 3, should be 2. answer=1FIXED..../dev/md0: Inode 142434305 ref count is 3, should be 2. answer=1FIXED./dev/md0: Inode 142475265 ref count is 3, should be 2. answer=1FIXED./dev/md0: Inode 142516225 ref count is 3, should be 2. answer=1FIXED.Unattached inode 149282817 answer=1RECONNECTED./dev/md0: Inode 149282817 ref count is 2, should be 1. answer=1FIXED./dev/md0: Unattached inode 149282818answer=1RECONNECTED./dev/md0: Inode 149282818 ref count is 2, should be 1. answer=1FIXED./dev/md0: Unattached inode 149282819answer=1RECONNECTED./dev/md0: Inode 149282819 ref count is 2, should be 1. answer=1FIXED..../dev/md0: Unattached inode 168313835answer=1RECONNECTED./dev/md0: Inode 168313835 ref count is 2, should be 1. answer=1FIXED./dev/md0: Unattached inode 168313836answer=1RECONNECTED./dev/md0: Inode 168313836 ref count is 2, should be 1. answer=1FIXED.
Ich zähle 1165x FIXED
An dieser Stelle kam dann mal wieder kurz der Statusbalken, gefolgt von unzähligen "answer=1" (ca 8700x)
answer=1: |====================================================== | 96.0% answer=1: |======================================================= - 97.5% answer=1answer=1answer=1...
Am Ende steht dann
answer=1answer=1/dev/md0: 128852/182853632 files (28.3% non-contiguous), 244707557/731395200 blocks[~] #
So... ich bin wieder etwas optimistischer. Wie geht es weiter?? Wie geht's jetzt weiter...???
PS
Ich hab die komplette Ausgabe als Text-DAtei gespeichert, könnte also bei Bedarf nochmal etwas nachschauen. Aber ich dachte, so ist es übersichtlicher.
-- EDIT --
Hab das NAS mal neu gestartet, in der Hoffnung das einfach wieder alles passt. Leider ist das RAID nach wie vor nicht gemounted, aber immerhin das LOG schaut wieder gut aus:
2014-03-26 01:52:31 System 127.0.0.1 localhost [Media Library] Media Library Server started.
2014-03-26 01:51:12 System 127.0.0.1 localhost System started.
2014-03-26 01:48:40 System 127.0.0.1 localhost System was shut down on Wed Mar 26 01:48:40 CET 2014.
2014-03-26 01:47:41 admin 192.168.178.186 --- [Power Management] System will be restart now.
Die alte Fehlermeldung "The file system is not clean. It is suggested that you run "check disk"." erscheint um ersten mal seit langem nicht mehr :thumb:
In der Datenträger- bzw. RAID-Verwaltung wird das RAID nach wie vor als "entladen" dargestellt.