MrChip

Members
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

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

MrChip's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I'm also getting the Invalid Certificate error from FCP. I don't use self-signed certs but use use Lets Encrypt certs. My home network is all based on a local domain name local.mydomain.tld, and my certs are for myserver.local.mydomain.tld. In settings I had Local TLD set to local, which doesn't match the certificate, but everything was working fine, so I missed this. I changed Local TLD to local.mydomain.tld . I feel that change should work, but I'd like to confirm that there won't be an issue going to 6.10. Perhaps @ljm42 can comment on this? After changing the Local TLD, I now get the same FCP error, but this time it's due to a case mismatch - the certificate uses all lower case domain name, but my Server Name setting uses an upper case letter. I'll change the server name setting, but as host and domain names are case insensitive, I suggest that FCP do a case insensitive match.
  2. AMQP looks like overkill for my needs, but the MQTT plugin would be fine. It's not a big deal for me using the current version I guess. My only problem has been that date format, and I can work around that. So, do what suits you. 😎
  3. Will there be any updates to the MQTT version? I'm getting an error trying to configure the log timestamp format: Error: Unknown configuration variable "log_timestamp_format". It appears this variable applies to newer versions of the Mosquitto MQTT broker. Current version is now 2.0 on mosquitto.org. Bob
  4. Sigh ... Live and learn from silly mistakes. My main board has SATA hot swap settings for each SATA port. I forgot about that. When I set up my server I ignored the SATA port settings for ports I wasn't going to use, so they were at default of no hot swap. When I added the eSATA dock I used one of those ports. I remembered changing the hot swap setting, but forgot that it was per-port and I hadn't done it for all the ports. I fixed that now, and the dock is working as expected when the system is booted with the dock off and no drive in it.
  5. I generally do the same - turn the unit off before removing or inserting disks. I did that with the USB dock and I do that with the new one. With this problem I'm experiencing, I've tried the different options - replacing a disk with the unit on, and replacing with the unit off. In either case if there's no disk in it (with the unit powered on) when Unraid boots then any amount of disk swapping doesn't work - the disk doesn't appear in UD. I can change disks with the unit on, or turn it off and swap disks and turn it back on, and in both cases the disk does not appear in UD. But when I boot Unraid with a disk in the unit and the unit powered up then UD shows the disk and it shows each disk change, regardless of whether the unit was on or off during the change. (By that I mean disk changed with the unit on, versus turn off the unit, change the disk, turn on the unit.) If this was another USB dock device, I'd send it back because I'm sure disk changes should be detected regardless of whether there was a disk in it at boot time. But this is an eSATA dock, and I'm not sure how Unraid/SATA should behave when a device appears on a SATA port after power-up. I did some testing and looked at lsscsi output and tried echo "- - -" > /sys/class/scsi_host/host4/scan to see if that helped. It didn't, but here's the details for those interested: Boot with device on and disk inserted The UD device lists shows the disk as unassigned device Dev2 (I have a permanently installed unassigned disk at Dev1) root@Tower:~# lsscsi [0:0:0:0] disk Ut163 USB2FlashStorage 0.00 /dev/sda [1:0:0:0] disk ATA WDC WDS100T2B0A 00WD /dev/sdb [2:0:0:0] disk ATA CT1000MX500SSD1 033 /dev/sdc [4:0:0:0] disk ATA WDC WD10EZRX-00A 1A01 /dev/sdd [7:0:0:0] disk ATA ST2000DM008-2FR1 0001 /dev/sde [7:0:1:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdf [7:0:2:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdg [7:0:3:0] disk ATA ST8000NE001-2M71 EN01 /dev/sdh [N:0:1:1] disk WDC WDS100T2B0C-00PXH0__1 /dev/nvme0n1 -- the disk is: [4:0:0:0] disk ATA WDC WD10EZRX-00A 1A01 /dev/sdd Turn off the dock device and remove the disk -- the disk disappears from the UD list, and the the lsscsi output root@Tower:~# lsscsi [0:0:0:0] disk Ut163 USB2FlashStorage 0.00 /dev/sda [1:0:0:0] disk ATA WDC WDS100T2B0A 00WD /dev/sdb [2:0:0:0] disk ATA CT1000MX500SSD1 033 /dev/sdc [7:0:0:0] disk ATA ST2000DM008-2FR1 0001 /dev/sde [7:0:1:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdf [7:0:2:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdg [7:0:3:0] disk ATA ST8000NE001-2M71 EN01 /dev/sdh [N:0:1:1] disk WDC WDS100T2B0C-00PXH0__1 /dev/nvme0n1 Turn on device, without disk inserted -- no change to lsscsi output, no change to UD device listing Turn off device, insert disk, turn on device -- disk appears in UD and lsscsi becomes root@Tower:~# lsscsi [0:0:0:0] disk Ut163 USB2FlashStorage 0.00 /dev/sda [1:0:0:0] disk ATA WDC WDS100T2B0A 00WD /dev/sdb [2:0:0:0] disk ATA CT1000MX500SSD1 033 /dev/sdc [4:0:0:0] disk ATA WDC WD10EZRX-00A 1A01 /dev/sdd [7:0:0:0] disk ATA ST2000DM008-2FR1 0001 /dev/sde [7:0:1:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdf [7:0:2:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdg [7:0:3:0] disk ATA ST8000NE001-2M71 EN01 /dev/sdh [N:0:1:1] disk WDC WDS100T2B0C-00PXH0__1 /dev/nvme0n1 Then I tried booting without a disk inserted in the dock and the dock powered off. No disk is listed in UD (except the permanent one at Dev1) root@Tower:~# lsscsi [0:0:0:0] disk Ut163 USB2FlashStorage 0.00 /dev/sda [1:0:0:0] disk ATA WDC WDS100T2B0A 00WD /dev/sdb [2:0:0:0] disk ATA CT1000MX500SSD1 033 /dev/sdc [7:0:0:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdd [7:0:1:0] disk ATA ST2000DM008-2FR1 0001 /dev/sde [7:0:2:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdf [7:0:3:0] disk ATA ST8000NE001-2M71 EN01 /dev/sdg [N:0:1:1] disk WDC WDS100T2B0C-00PXH0__1 /dev/nvme0n1 Insert a disk into the dock and power it on. -- No change in UD disk list, nor the lsscsi output root@Tower:~# lsscsi [0:0:0:0] disk Ut163 USB2FlashStorage 0.00 /dev/sda [1:0:0:0] disk ATA WDC WDS100T2B0A 00WD /dev/sdb [2:0:0:0] disk ATA CT1000MX500SSD1 033 /dev/sdc [7:0:0:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdd [7:0:1:0] disk ATA ST2000DM008-2FR1 0001 /dev/sde [7:0:2:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdf [7:0:3:0] disk ATA ST8000NE001-2M71 EN01 /dev/sdg [N:0:1:1] disk WDC WDS100T2B0C-00PXH0__1 /dev/nvme0n1 Force a rescan: root@Tower:~# echo "- - -" > /sys/class/scsi_host/host4/scan No change in UD or lsscsi. root@Tower:~# lsscsi [0:0:0:0] disk Ut163 USB2FlashStorage 0.00 /dev/sda [1:0:0:0] disk ATA WDC WDS100T2B0A 00WD /dev/sdb [2:0:0:0] disk ATA CT1000MX500SSD1 033 /dev/sdc [7:0:0:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdd [7:0:1:0] disk ATA ST2000DM008-2FR1 0001 /dev/sde [7:0:2:0] disk ATA ST2000DM008-2FR1 0001 /dev/sdf [7:0:3:0] disk ATA ST8000NE001-2M71 EN01 /dev/sdg [N:0:1:1] disk WDC WDS100T2B0C-00PXH0__1 /dev/nvme0n1 This was surprising and disappointing - I was hoping that the rescan echo command would be what I needed. But no. I then tried booting with the dock powered on but no disk inserted. No improvement. Same UD and same lsscsi output. I tried the echo "- - -" again, and still no improvement.
  6. Hi. I just received a new eSATA docking bay for HDDs. I'm replacing a USB3 dock that works fine with older disks but new disks I just bought aren't recognized by Unraid in that dock. Now, the new dock isn't recognized unless there is a disk in the dock at boot time. Without a disk in it on boot, any disk I put in the dock later just doesn't appear in Unassigned Devices. Nor are there any logs that show a disk being added. With a disk in the unit on boot, that disk is recognized in UD. I can remove it and add another disk and it gets recognized and correctly listed in UD, and there are related log entries. Is this behavior to be expected? Or should it act like the previous USB3 dock and show disks added and removed regardless of whether there was a disk in it at boot time? Is there a way I can trigger the OS to pick up the dock and disk once booted (when I forget to put a disk in the dock on boot, which I'm sure I will, 🙄 )? These are what I bought and added to my server: https://www.amazon.ca/ORICO-External-Docking-SSD(4TB-support/dp/B00A5323NO/ref=sr_1_5?dchild=1&keywords=orico+esata&qid=1628120388&sr=8-5 https://www.amazon.ca/StarTech-com-ESATAPLATE1-1-Port-eSATA-Bracket/dp/B000GX4C7I/ref=sr_1_17?dchild=1&keywords=esata+cable&qid=1628120450&sr=8-17 Thanks for any feedback. Bob
  7. And I don't have that record, so I'm out of luck I think to diagnose further at this point. I've configured the syslog server feature to help retain logs going forward. I've put the disk on the shelf, marked as questionable. Thank you for your help and insights.
  8. Those messages don't look familiar. What I saw was more like: <date> <time> <hostname> <???> Read error <disk> block=123456789 where I don't recall what was at <???> , and <disk> was either Disk2 or sdc - it unambiguously identified the disk listed on the Main tab. There were thousands of these error logs, all together as a block in the log file with only a handful of other log messages interspersed though the block. The block numbers weren't consecutive, but they appeared to be inside a range. There was a parity check running at the time, so I at first thought that there was a bad spot on the disk that the parity check was reading through at the time. But if that were so, I would anticipate errors to appear on the pre-read portion of the follow-up preclear, but there were no errors reported during any of the preclear. The disks in this server are on the main board SATA ports.
  9. Thanks for the info. I don't have syslogs for the read errors. I didn't save a copy prior to shutting down to swap disks - I forgot logs aren't persistent across reboots. What are the specific log messages that distinguish disk issue from connection issues? Maybe I can recognize from memory. The messages I saw were showing a read error followed by a block number, if that helps.
  10. Earlier this year I converted an older Ubuntu file server into an Unraid server. It's been fine until I started getting notices about 1 disk. First these: Event: Unraid Disk 2 SMART health [197] Subject: Warning [FLINT-UN] - current pending sector is 2 Description: WDC_WD10EZRX-00L4HB0_WD-WMC4J0164198 (sdc) Importance: warning Event: Unraid Disk 2 SMART health [198] Subject: Warning [FLINT-UN] - offline uncorrectable is 2 Description: WDC_WD10EZRX-00L4HB0_WD-WMC4J0164198 (sdc) Importance: warning I followed another thread here and ran an extended SMART self-test, which finished without showing anything out of the ordinary other than the 197 and 198 attributes at 2. I ran a parity check without corrections and it passed fine. The logs showed no errors on the drive. So I monitored it. Shortly the 198 returned to 0: Event: Unraid Disk 2 SMART message [198] Subject: Notice [FLINT-UN] - offline uncorrectable returned to normal value Description: WDC_WD10EZRX-00L4HB0_WD-WMC4J0164198 (sdc) Importance: normal I continued using the disk, and then this past weekend it started reporting errors: Event: Unraid array errors Subject: Warning [FLINT-UN] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 2 - WDC_WD10EZRX-00L4HB0_WD-WMC4J0164198 (sdc) (errors 856) The error count went up to about 2700 and then stayed there. This all happened during a scheduled parity check. There haven't been any further errors logged since that parity check. After seeing those read errors, I got myself a new drive and installed it and precleared it. Once precleared I put the new drive in for the old drive. This went smoothly and the rebuild onto the new drive completed without error. The old drive is now in as an unassigned device. I wanted to see what I could learn about it's condition and now it's looking like there's nothing amiss with it (but I don't fully understand all the SMART stats, so I may be missing something). I ran an extended self-test which came back with the current pending sector at 2 as before. So I ran a pre-clear and was anticipating that there would be read errors, but there were none. The preclear completed without error, and the current pending sector has now gone back to 0: Event: Unraid device dev1 SMART message [197] Subject: Notice [FLINT-UN] - current pending sector returned to normal value Description: WDC_WD10EZRX-00L4HB0_WD-WMC4J0164198 (dev1) Importance: normal So now I don't know how to treat the disk. The read errors on the weekend suggested it was bad, but nothing since seems to support that. I'm attaching the latest SMART self tests - the extended one before the pre-clear and a regular one after, and the pre-clear logs and summary. I'm also including an extended self test form Jul 14 when the current pending sector first appeared. What do you think? How would you treat this disk now? Thanks for any feedback. Bob disk-info.zip
  11. I'm running internetsystemsconsortium/bind9, and in its dockerfile (here) it has CMD ["/usr/sbin/named", "-g", "-c", "/etc/bind/named.conf", "-u", "bind"] The -g option tells named to run in foreground and to dump all logging to STDERR. This works but analysing logs is a pain - the GUI logs window for the docker updates while open, and when it does to scrolls back to the bottom, so you lose your place where you were looking. So I'd like to change the -g option to -f and use the named logging features to write logs to /var/log, which is an exposed VOLUME in the dockerfile. The docker run command can do this, if I've read the documentation correctly. Can this be done through the docker GUI configuration? Extra Parameters? Post Arguments? These two look like they might be the way to go, but my experience with dockers is limited for now, so I'm not sure about it. I'd appreciate some tips, please. Cheers, Bob
  12. When the disk filled up the rsync was copying my photo library - everything in there is nowhere near 1 GB in size. I suppose the floor could be too low, but I don't see it. I followed trurl's suggestion and turned off the cache and then finished the rsync. That completed without interruption. Thank you for your inputs. Bob
  13. Okay, so it's about rsync, in this case. That eases my mind - I was looking for the setting I got wrong.... So if a folder is created on the cache before the minimum free space is passed, Unraid will later write a file into that folder on the cache, even if the minimum has been passed in the interim? (edited to correct a typo)
  14. I'm setting up a new Unraid server and using rsync to bring files to it from another server. Rsync operates as I expected at the start - it writes all the new files to the cache, up to the time it reaches the minimum free space setting. At that point I'm expecting it to continue by writing to the array, but it doesn't. It continues writing to the cache until the cache fills. Then rsync reports a disk full error and dies. I have both the share minimum free space and the cache minimum free space set to 1GB. The last time this happened rsync was copying a collection of 6 megapixel photos, jpg format, so the files were well below the set minimum. The rsync command I run is: rsync -av user@host:/mnt/user/NAS/ /mnt/user/NAS > /tmp/bb From the .cfg for the share: shareFloor="1000000" From the .cfg for the cache: diskShareFloor="1GB" The cache is a pool of 2 SSDs, RAID1 with btrfs. I'm attaching a diagnostic file. What am I missing here, please? Thanks for any guidance. Bob bailey-diagnostics-20210626-1920.zip