iripmotoles

Excellent. Thank you so much for your help!

On the emulated drive now I don't have the Lost+Found folder. I will check again after rebuild.

Ok, thank you. I cancelled, then checked and repaired the drive with the following output: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_ifree 350, counted 348 sb_fdblocks 1172213351, counted 1189241404 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 inode 4455004287 - bad extent starting block number 4503567550636411, offset 0 correcting nextents for inode 4455004287 bad data fork in inode 4455004287 cleared inode 4455004287 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 2 - agno = 3 - agno = 4 - agno = 1 - agno = 6 - agno = 8 - agno = 9 - agno = 7 entry "DeloreanASAnnotationToolbarView.nib" at block 0 offset 560 in directory inode 4455004273 references free inode 4455004287 clearing inode number in entry at offset 560... Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 4455004273 (no data entry): rebuilding rebuilding directory inode 4455004273 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (14:2462824) is ahead of log (1:2). Format log to cycle 17. done Then I stopped the array and started it normally, now it has started a new Data-Rebuild. My shares are back but of course have an exclamation mark for being unprotected. I will report back the results. If everything is back to normal after the rebuild, I will install the newly ordered drive as dual parity.

Thank you for your reply. Does it make sense to cancel the Data-Rebuild in order to attempt check/repair or is it better to let the rebuild run through?

Hi All, the other day I upgraded my seemingly fully functioning server from 6.12.6 to 6.12.8. After the upgrade certain dockers wouldn't start anymore and the attempt gave me an "execution error". I didn't realize or suspect a potential issue with my array. I urgently needed to access my paperless docker and in a knee-jerk reaction I downgraded to 6.12.6 and then upgraded to 6.12.8 again. Edit: I forgot and now remembered: After the first upgrade, the Server became unreachable and I forced a reboot. Later I had the time to investigate a bit further and finally found my main Disk 1 being unmountable. I stopped the array and today started looking into the issue. First I downloaded diagnostics, see attached (edit: attachment removed after problem was solved). Then I followed this advice, stopped the array, unassigned the drive and started again. I didn't notice an emulated drive, most of my shares were gone and the docker issue persisted. I then stopped the array, assigned the drive again and started the array. A data-rebuild started that I paused and that's where I'm standing now. I have ordered a new drive that will arrive tomorrow. Any help would be highly appreciated.

Wieso?

Ok, thank you! Once the initial backup is completed I will compare the directories with krusader synchronize and see what happened. Edit: You were right, the destination size is almost half of the original directory. Maybe you could put a short warning in your opening post. Sooner or later there will be somebody out there that set this up the way I intended and thinks that it works. Looking further opened a whole new can of worms. I suspect using another backup solution such as CCC instead of time machine would end with the same issue. I will keep looking for another solution for simple synchronizing, maybe something like unison.

I want to use the script to rsync time machine backups which in itself have hard links. Therefore I believe I need the -H flag to preserve the hard links in order to not break the time machine functionality. @mgutt Can I just change your script to -avH without messing with its functionality?

Kommt aufs Case an. Die von dir ausgesuchte ist Full Profile. Je nach Case kann es sein, dass du Low Profile brauchst. Da ist dann einfach das Slot-Blech kürzer.

Laut unraid wiki geht das:

Nee, Unraid läuft vom USB-Stick. Wenn du deine SATA SSDs als Cache nimmst, brauchst du keine NVME.

Wieso Selbstbau? Die Kiste muss man doch nur auspacken, Platten reinstecken und installieren. socke braucht anscheinend kein Array in so astronomischen Größen, wie man es hier im Forum oft liest. Für den normalen Hausgebrauch reicht doch bei den heutigen Festplattengrößen eine Platte plus Parität ewig. Falls die wider Erwarten irgendwann doch mal voll wird, kann er eine weitere Platte hinzufügen die dann wieder ewig reicht. Klar ist es irgendwie cool, einen Speicher mit dreistelligen TB zu haben. Braucht aber eben nicht jeder.

Wenn du Abstriche in der Ausstattung machen willst: Fujitsu D3644-B, nur ein M.2 slot und ein NIC onboard, zwei SATA ports weniger. Wenn du Abstriche beim Stromverbrauch und beim Kaufpreis machen willst: Supermicro, zB. X11SCH-LN4F. Tolle Ausstattung aber kostet derzeit so ab 300€. Ich habe letzten Monat ein C246M-WU4 bei mindfactory gekauft aber leider hat der Chipsatz gesponnen. Wollte dann nicht ewig auf Ersatz oder Reparatur warten und habe mir den Preis erstatten lassen. Hab dann eins bei Amazon erwischt. Kein Warehouse Deal, direkt von Amazon. Die haben mir aber ein Board mit verbogenen Pins am Sockel geschickt, großzügig mit Leitpaste vollgeschmiert. Also Vorsicht mit Amazon. Haben sie mir aber ersetzt durch eins, was gut aussieht und bisher gut funktioniert.

Erstens hat er nach einem gen 10 plus gefragt und zweitens braucht er keinen zusätzlichen SATA Controller. Falls eine iGPU gewünscht ist, würde ich den T40 nochmal ins Spiel bringen. Da die drei 3,5" Bays hier ausreichend sind, ist der doch für den Preis ein tolles Gesamtpaket. Cache je nach Anspruch per SATA oder PCIe-NVME Adapter. Laut elefacts braucht der 15,1 W + Festplatten im Leerlauf mit Unraid.

Here you go.