alexandru360

+1

https://github.com/alexandru360/unVerdaccio

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 filesystem before doing this. It is that corruption I fear but I guess it is much better than not being able to mount the HDD. I will wait a little for your friend's input and then do the -L thing ...

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... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1:79588) is ahead of log (1:77215). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting.

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 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Write Protect is off Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 4 02:34:17 AlexHomeTower kernel: sdb: sdb1 Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Attached SCSI disk Apr 4 02:36:33 AlexHomeTower emhttpd: ST2000NM0008-2F3100_ZDS12462 (sdb) 512 3907029168 Apr 4 02:36:33 AlexHomeTower emhttpd: read SMART /dev/sdb Apr 4 02:39:52 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:39:52 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:39:52 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:39:53 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:39:53 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:39:53 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:39:54 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:39:54 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:39:54 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:39:54 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:39:55 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:39:55 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:39:55 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:04 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:04 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:04 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:05 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:05 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:05 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:06 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:06 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:06 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:07 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:07 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:07 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.

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-confs/gitea.subdomain.conf I will investigate and comeback with results ...

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 ...

That also looks like my log unfortunately ... guess in the future I will not rush into an update

/mnt/user/appdata/nextcloud/log This is the path to the log but for me it was not much help ... And yes it happened to me as well after the docker update

I'm using your script, thanks it really helps me

try this:

Hello, I would like to thank the unraid team that created the product For me it is simply awesome I'm a one year Unraid user and I want to share, a little, my thoughts about the server. I had some prior experience with linux(debian/ubuntu based mostly) but I always wanted something like Unraid that has both the liberty for creating scripts/custom stuff from linux console and to have predefined stuff in an interface to get repetitive things done fast (here I'm thinking dockers and community applications). Intentionally I left out the virtualisation because for me this was a selling point I was in a period where I tried to do that on my own with Fedora and stuff and it was a big hassle ... when I tried unraid and it did that out of the box ... I never looked back Bottom line now I have dockers and vm-s for everything I wanted and now with the added pools my life is even better. PS. Many many thanks to the Unraid team.