alexandru360

Well ... it worked I got my HDD back ... Thank you all for the assistance

Ok ... here goes ... fingers crossed ...

xfs_repair -v /dev/md3 Phase 1 - find and verify superblock... - block cache size set to 1508680 entries Phase 2 - using internal log - zero log... zero_log: head block 77215 tail block 77209 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the file

alexhometower-diagnostics-20210404-1000.zip xfs_repair -n /dev/md3 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 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... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - p

Hy guys unfortunately I rearranged my hdds in the server (new array - software) and for one hard-disk I get this: Apr 4 02:34:17 AlexHomeTower kernel: ata8: SATA max UDMA/133 abar m8192@0xfbe80000 port 0xfbe80180 irq 71 Apr 4 02:34:17 AlexHomeTower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 4 02:34:17 AlexHomeTower kernel: ata8.00: ATA-10: ST2000NM0008-2F3100, ZDS12462, SN02, max UDMA/133 Apr 4 02:34:17 AlexHomeTower kernel: ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA Apr 4 02:34:17 AlexHomeTower kernel: ata8.00: configured for UDMA/133 Apr

Hello guys Currently I have on my server a MSI X2999 PRO it is not a bad mainboard card but there is no way to do KVM Passthrough for video cards has anyone tried: X299 Taichi X299 Taichi CLX Thank you.

Hello guys I am using this thread to post a question; currently I have on my server a MSI X2999 PRO it is not a bad mainboard card but there is no way to do KVM Passthrough for video cards has anyone tried the X299 Taichi or the X299 Taichi CLX Thank you.

I am looking at the same thing and found here on the forum this thread: solved-how-to-create-a-virtual-nic-for-internalisolated-use-only

yep ... that was the problem forgot to switch to the custom docker network

I uninstalled Nerd Tools ... deleted completely SWAG and reinstalled made all the configurations again and still Bad Gateway ... but the main domain works ... I am confused ... I think I have to investigate what Bad Gateway means for Nginx

Nope ... I backed up all my configs, reset everything to default, cloned only deluge[...].conf and restarted swag and for subdomains I get Bad Gateway ... If someone has an idea I'll be all eyes ... Just a thought: I saw on another thread here a response from 2019 that Nerd Pack might interfere with swag "mojo" ... is this still the case ?

After some further investigation I had this lines in my swag log: **** The following reverse proxy confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare them to the samples in the same folder to make sure you have the latest updates. **** /config/nginx/proxy-confs/sonarr.subdomain.conf /config/nginx/proxy-confs/plex.subdomain.conf /config/nginx/proxy-confs/openvpn-as.subdomain.conf /config/nginx/proxy-confs/nextcloud.subdomain.conf /config/nginx/proxy-con

Same with me ... I had my server down like for 3 weeks(I had my mainboard in the warenty) and everything worked plex, gitea, sonarr, deluge, nextcloud ... finally I had all of them working and now all are down again Funny thing now as an exception for other not working dates(misconfiguration of swag/pipeline until swag) is that swag is validating the certificate for everything domain and the above mentioned subdomains but am still getting Bad Gateway ...

Well ... I do not know what to say about that.

Fortunately for me I was stupid enough to leave my mysql-nextcloud docker offline and that was causing my server error but ... in the logs there was no hint whatsoever that this was the case ... now I have a different problem regarding swag and dynamic dns updating for namecheap (works for 15-30 minutes then my ip changes and it doesn't work from web but from inside my lan works well ) I'll bang my head against the scripts some more ...