TQ

Members
  • Posts

    98
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TQ's Achievements

Apprentice

Apprentice (3/14)

6

Reputation

  1. You've been rate limited. Are you behind a large NAT? That error indicates rate limited. If you continue to have issues, rebuild the container and try again. If that doesn't work, try manually installing the main db files into a bind mounted dir and see if that works.
  2. Hi Binhex. Recently, the sabnzbd container started griping about unrar version 0.00. I noticed that the options to unpack + delete no longer work and downloads are not be extracted. I've validated that the container has `par2cmdline` as well as `unrar`. Do you know what this issue is? I can run unrar from inside the container no issue, but sab seems to think I have version 0.00 and it wont extract.
  3. Thanks @vroommm
  4. I erred on the side of "DONT REBOOT" and didn't even try that. thanks Squid.
  5. I'm not sure what happened. My user share files still exist in /boot/config/shares/ But when trying to even change to the user folder /mnt/user: Transport endpoint is not connected quizzleunraid-diagnostics-20210509-0746.zip
  6. This looks like lack of free space on the Flash disk.
  7. Update. I have updated to 0.103.2-r0 and merged a couple of PRs. For my scan today, the `LibClamAV` issue seems resolved.
  8. I promise I can read. ...and I guess the answer is right there in front of me.
  9. Alright. Assuming I have backups of the data and can accept the loss of data from this disk, how do I get disk8 back to a working filesystem and available to take data again?
  10. Unfortunately, all syslogs prior to the second posting of this thread are blank.
  11. Thanks @JorgeB. Disk7 back in action. What should I do about disk8. I attempted to remove it from the array, and rebuild it's contents again, and that "succeeded" but the disk is still unmountable. Since I have dual parity and one of those is also disabled, should I attempt the rebuild of that one first and then again for disk8? I'm just at a loss (and I feel possibly data loss) as to what my next steps should be.
  12. Disk 7: Disk 8: How should I address each?
  13. Rebooted after figuring out why syslog was blank. I see errors now below: # grep -C 3 -i error /var/log/syslog -- Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11375): mount -t xfs -o noatime /dev/md7 /mnt/disk7 Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Mounting V5 Filesystem Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Starting recovery (logdev: internal) Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Metadata CRC error detected at xfs_inobt_read_verify+0xd/0x3a [xfs], xfs_inobt block 0xaea86678 Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Unmount and run xfs_repair Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): First 128 bytes of corrupted metadata buffer: Apr 11 12:09:05 QuizzleUNRAID kernel: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ -- Apr 11 12:09:05 QuizzleUNRAID kernel: 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Apr 11 12:09:05 QuizzleUNRAID kernel: 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Apr 11 12:09:05 QuizzleUNRAID kernel: 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): metadata I/O error in "xfs_btree_read_buf_block.constprop.0+0x75/0xc1 [xfs]" at daddr 0xaea86678 len 8 error 74 Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): xfs_do_force_shutdown(0x1) called from line 296 of file fs/xfs/xfs_trans_buf.c. Return address = 00000000d5f03c72 Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): I/O Error Detected. Shutting down filesystem Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Please unmount the filesystem and rectify the problem(s) Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): xfs_difree_inobt: xfs_inobt_lookup() returned error -117. Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Ending recovery (logdev: internal) Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md7): Error -5 reserving per-AG metadata reserve pool. Apr 11 12:09:05 QuizzleUNRAID root: mount: /mnt/disk7: can't read superblock on /dev/md7. Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11375): exit status: 32 Apr 11 12:09:05 QuizzleUNRAID emhttpd: /mnt/disk7 mount error: not mounted Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11376): umount /mnt/disk7 Apr 11 12:09:05 QuizzleUNRAID root: umount: /mnt/disk7: not mounted. Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11376): exit status: 32 -- Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md8): Mounting V5 Filesystem Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md8): Log inconsistent (didn't find previous header) Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md8): failed to find log head Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md8): log mount/recovery failed: error -117 Apr 11 12:09:05 QuizzleUNRAID kernel: XFS (md8): log mount failed Apr 11 12:09:05 QuizzleUNRAID root: mount: /mnt/disk8: mount(2) system call failed: Structure needs cleaning. Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11379): exit status: 32 Apr 11 12:09:05 QuizzleUNRAID emhttpd: /mnt/disk8 mount error: not mounted Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11380): umount /mnt/disk8 Apr 11 12:09:05 QuizzleUNRAID root: umount: /mnt/disk8: not mounted. Apr 11 12:09:05 QuizzleUNRAID emhttpd: shcmd (11380): exit status: 32 Should I start back in maintenance mode and run file checks on both disks? syslog.txt