Slamer

Issue has gone after updating to version 6.11.3! Thanks for the help.

Hi ChatNoir, Indeed I'm using version 6.11.2. Please find here my diags file. Thanks tower-diagnostics-20221116-1237.zip

Hi all, I have already precleared two times and is still displaying UNMOUNTABLE: UNSUPPORTED PARTITION LAYOUT! Please find here the report:preclear.txt Here the screen capture: Any idea on what's happening? This is a new WD disk I have just installed a 2 new HD Seagate (Disk9 and Disk10) without need to preclear and was recognized. Thanks for your help.

Now I'm able to use the eSata interface but I'm facing I/O Log error. Please find the attached diagnostic file. Sorry for the delay and thanks for your help. S. tower-diagnostics-20181027-1531.zip

Hi, I bought the Startech PCIe eSata Multiplier https://www.amazon.co.uk/d/Graphics-Cards/StarTech-Port-SATA-Gbps-Express-eSATA-Controller/B003GSGMPU and to expand my HDD array I have also added this box : https://www.amazon.fr/QB-35US3-6G-Boîtier-disques-externes-ventilateur/dp/B00ORENYJE/ref=sr_1_1_sspa?ie=UTF8&qid=1538598733&sr=8-1-spons&keywords=fantec&psc=1 I'm facing an issue that the eSata seems to be not recognized by the HDD box and the led is activated for the USB3.0. Is there any manipulation to do on the bios to get the eSata enabled on the server? For information, I have updated the bios firmware on the latest one from HPE. I saw that with N40L and N54L there are a MOD bios to activate hot swap for eSata ports : https://homeservershow.com/forums/topic/4727-successfully-enabled-port-multiplier-on-esata/ Could you help please? S

Thanks a lot! I've fixed my issues by following your comments : I/O Error and Docker issues. Last question, do you recommend to use eSata instead of USB3.0?

I did a check on Disk5 such as suggested in the link by running the check with repair (option -nd). Below the xfs_repair_status : Phase 1 - find and verify superblock... - block cache size set to 738272 entries Phase 2 - using internal log - zero log... zero_log: head block 16739 tail block 16733 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... Metadata CRC error detected at xfs_allocbt block 0x3a382260/0x1000 btree block 1/8 is suspect, error -74 bad magic # 0xaab40a7f in btbno block 1/8 Metadata CRC error detected at xfs_allocbt block 0x74704448/0x1000 btree block 2/1 is suspect, error -74 bad magic # 0xb763e301 in btbno block 2/1 Metadata CRC error detected at xfs_allocbt block 0x3a382250/0x1000 Metadata CRC error detected at xfs_allocbt block 0x74704450/0x1000 btree block 2/2 is suspect, error -74 btree block 1/6 is suspect, error -74 bad magic # 0xb5dea178 in btcnt block 2/2 bad magic # 0x4d06950 in btcnt block 1/6 agf_freeblks 121803650, counted 0 in ag 2 agf_freeblks 121971479, counted 0 in ag 1 agf_longest 113467576, counted 0 in ag 2 agf_longest 105317432, counted 0 in ag 1 Metadata CRC error detected at xfs_inobt block 0xaea86678/0x1000 agf_btreeblks 4, counted 0 in ag 1 btree block 3/3 is suspect, error -74 bad magic # 0x81c1838 in inobt block 3/3 Metadata CRC error detected at xfs_inobt block 0x74704458/0x1000 btree block 2/3 is suspect, error -74 bad magic # 0x55978c97 in inobt block 2/3 Metadata CRC error detected at xfs_inobt block 0x3a382238/0x1000 btree block 1/3 is suspect, error -74 bad magic # 0x4ce3550 in inobt block 1/3 inode chunk claims untracked block, finobt block - agno 2, bno 249252, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249253, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249254, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249255, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249256, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249257, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249258, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 3996, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 249259, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 3997, inopb 8 undiscovered finobt record, ino 2149477664 (2/1994016) inode chunk claims untracked block, finobt block - agno 1, bno 3998, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 3999, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 4000, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 4001, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 4002, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 4003, inopb 8 agi_count 256, counted 0 in ag 2 agi_freecount 25, counted 0 in ag 2 undiscovered finobt record, ino 1073773792 (1/31968) agi_count 576, counted 0 in ag 1 agi_freecount 44, counted 0 in ag 1 sb_icount 896, counted 64 sb_ifree 127, counted 58 sb_fdblocks 975359350, counted 732565281 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... found inodes not in the inode allocation tree found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 4 entry "Audio 2018-08-23" in shortform directory 99 references non-existent inode 1073741920 - agno = 3 would have junked entry "Audio 2018-08-23" in directory inode 99 - agno = 5 - agno = 7 - agno = 6 entry "Audio 2018-09-02" in shortform directory 99 references non-existent inode 2149391456 would have junked entry "Audio 2018-09-02" in directory inode 99 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 Maximum metadata LSN (2130140933:-29345724) is ahead of log (1:16739). Would format log to cycle 2130140936. No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Fri Sep 28 23:24:03 2018 Phase Start End Duration Phase 1: 09/28 23:24:03 09/28 23:24:03 Phase 2: 09/28 23:24:03 09/28 23:24:03 Phase 3: 09/28 23:24:03 09/28 23:24:03 Phase 4: 09/28 23:24:03 09/28 23:24:03 Phase 5: Skipped Phase 6: Skipped Phase 7: Skipped Total run time: I'm not sure that the problem was fixed.

Hi, I'm getting since a couple of days an error when try to write on my Samba shares. The shares have a write access for the selected user. I've observed also that Docker service can't started due to the error: Sep 27 20:57:34 Tower root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error. I've tried to recreate the ssd cache and re-format it. So I've tried to backup my appdata, isos ans system dirs using tar -czvf command but I have obtained an I/O error. tar -czvf Archives/cache.tar.gz appdata isos system tar (child): Archives/cache.tar.gz: Cannot open: Input/output error tar (child): Error is not recoverable: exiting now appdata/ appdata/kde/ appdata/kde/cache-14f538808b47 appdata/kde/tmp-14f538808b47 appdata/kde/socket-14f538808b47 appdata/kde/share/ appdata/kde/share/config/ appdata/kde/share/config/phonondevicesrc appdata/kde/share/config/drkonqirc appdata/kde/share/config/katerc appdata/kde/share/config/kcookiejarrc appdata/kde/share/config/kdedrc appdata/kde/share/config/kget_multisegkiofactory.rc appdata/kde/share/config/kgetrc tar: Archives/cache.tar.gz: Cannot write: Broken pipe tar: Child returned status 2 tar: Error is not recoverable: exiting now Please find as attachement the diagnostics file. Could you please give me any help? Regards, S. tower-diagnostics-20180927-2210.zip

The issue is related to chrome navigator. I've checked on Safari and shares are displayed correctly

Hi there, After I installed the unBalance plugin, I have observed that my Shares has disappeared from the tab Shares! Could you please help me to see what is wrong? Thanks. Sl

Hi, I finally succeeded to restart the server. After that I've started a parity check and obtained until now 535048090 Corrected Sync Errors after 18 hours. The estimated end time is in 23 hours! Is that a normal behaviour to get a lot by checking the parity check? Is the issue is coming from the HDDs? What's your recommandation to investigate. For information, I'm using : 2 SSD : 250GB (eSATA)+500GB(UDB3.0) for Caching 2 HD : 2*3TB(eSATA) for Parity 6 HD : 2*3TB(eSATA)+4*2TB(USB3.0) for Data Thanks a lot.

Hi there, I'm experiencing the same issue. The docker image Nzbget is freezing and can't stop it or remove it. This was happened after adding a volume mapping -v /mnt/usr/Exchange/intermediate:/intermediate as suggested by the install documentation from linuxserver/nzbget (https://hub.docker.com/r/linuxserver/nzbget/) I've tried using command line but no success: docker stop <container id> Diagnostics are attached : tower-diagnostics-20180426-1936.zip Thanks for your help.