Jump to content

alexandru360

Members
 View Profile  See their activity

  • Posts

    24

  • Joined

  • Last visited

 Content Type 

Posts posted by alexandru360

    [Solved] Help HDD with error

    in General Support

    Posted

    5 minutes ago, itimpi said:

    The -L option virtually never causes corruption, and even if it does it will only be to the last file(s) written to the disk.    That warning message reads a lot more ominously than turns out to be the case in practice.

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

    [Solved] Help HDD with error

    in General Support

    Posted

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

     

    Quote

    Ordinarily, SSDs are not recommended in the array. But in your case only parity disks are SSDs. I'm not sure how that plays out in the discussions we have had about SSDs in the array.

     

     

     

    now-vs-original.png

    [Solved] Help HDD with error

    in General Support

    Posted · Edited by alexandru360

    Quote

    (new array - software) --------> Tools -> New Config

     

    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.

     

    [Solved] Help HDD with error

    in General Support

    Posted

    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.

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    5 minutes ago, alexandru360 said:

     

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

     

    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 ?

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by alexandru360

    22 minutes ago, alexandru360 said:

     

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

     

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

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    2 hours ago, Ryguy said:

    with the latest update, unfortunately all of my reverse proxies are no longer working.

     

    I have it configured to use my own domain, and there is a cname associated to each subdomain. My dynamic dns is resolved with DuckDNS, and I have all of the relevant containers set on proxynet along with the SWAG container.

     

    My logs show that the Server is ready, however it is flagging that the Prox-conf files are out of date. Could this be causing the issue? did the templates change materially?

     

    The containers in use are Bitwardenrs, Nextcloud, and OMbi

     

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

    • Like 1

    [Support] Linuxserver.io - Nextcloud

    in Docker Containers

    Posted · Edited by alexandru360

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

    [Support] Linuxserver.io - Nextcloud

    in Docker Containers

    Posted

    7 minutes ago, andreidelait said:

    I have some log entries in nginx error log that look like this

      

    
2020/12/29 20:38:38 [error] 375#375: *405 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /wp-login.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "MYDOMAIN", referrer: "http://mta-sts.MYDOMAIN/wp-login.php"

    is this normal?

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

    Greetings

    in Lounge

    Posted · Edited by alexandru360

    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.

    • Like 3
×
×
  • Create New...