Stubbs

Members
  • Posts

    207
  • Joined

  • Last visited

Everything posted by Stubbs

  1. What's this? (from the log, straight after installation) WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender (file:/usr/local/tomcat/lucee/lucee.jar) to method java.net.URLClassLoader.addURL(java.net.URL) WARNING: Please consider reporting this to the maintainers of org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release
  2. Well, the first disk I was planning on installing was the 10TB parity drive. Once parity is established on that, restoring it to each new 10TB disks should be simple. The point of my question in this thread was asking if I could mount the old array disks as unassigned devices. This way I could keep my data available while building the data on the new drives. This way, while I'm building each 10TB disk, I can still keep my Nextcloud & Media data up.
  3. I know this sounds a bit complicated, but: I want my new 4x10TB Hard Drives to replace my current array Hard Drives (1x3TB parity, 2x3TB & 2x2TB). I don't have any SATA ports left, and cannot fit an HBA Card in right now. So I was thinking of taking the current array drives out, putting them in an HDD USB3 Docking Station, connecting it to the Unraid Server and mounting them as read-only Unassigned Devices. This way, my current array's data will still be available when I build the array on the new drives. Then I could put my new 10TB hard drives in the SATA bays of the server, maybe preclear them (I don't know if this is still important in 6.9+), then build parity, then either rebuild the data from parity or transfer it over from the old array disks mounted as unassigned devices, or just restore my data backups. I suspect doing the latter could lead to parity problems so I might have to rebuild it.
  4. See what JonathanM linked above. I'm exploring solutions that will let me transfer data on my current array to a new set of HDDs, while minimizing the downtime of my current array's data. I figured maybe temporarily mounting a current array drive as a read-only unassigned device while building the data on the new drives might be an ok option.
  5. If I run a preclear over a USB3 connection to a hard drive, then re-connect the hard drive with a SATA cable, it will retain the Unraid signature, right? And can be added straight to the array?
  6. Wouldn't this be very taxing on the parity drive compared to just moving the data directly from each old drive? Or using external storage? Is rebuilding from parity more reliable in some way compared to manually allocating data from an external source? I also kind of want to re-arrange where my data is stored across the array for better efficiency. With the old array I just used high water allocation for everything. Also slightly unrelated question, but if I preclear a drive over a USB-C connection, then swap it to a SATA connection, can it still be loaded straight into an array without waiting?
  7. Can array drives be mounted as unassigned devices? Like, if I wanted to temporarily remove a drive from my array, plug it into a docking station and connect it to the server via USB, could it safely be used as an unassigned device with all its data intact?
  8. I am currently running a 10TB array: x1 3TB parity, x2 3TB storage and x2 2TB storage - 10TB storage total. I decided I wanted to upgrade and my new x4 10TB Seagate Ironwolfs arrived in the mail today. How should I get the data off my current array and onto the new drives? I cannot add the 10TB drives to the array because I have 0 SATA slots left on the motherboard. I cannot use my HBA Card because the only PCIe x16 slot on the motherboard is being used by my NIC which I pass through to my pfSense VM. Disconnecting it for a long period of time is not an option cause its literally my router and I refuse to use anything else. I'll hopefully be getting a new motherboard with one or two more PCIe x16 slots soon. In the meantime, is there anything I can do to transfer the data safely?
  9. I have a slightly unorthodox setup. I believe disks 2 & 3 are installed within my servers case, whereas the parity disk + disks 1 and 4 are inside the hotswap bay connected to the front of the case. This bay (and its fan) is powered by two SATA power connectors. I've had to interchange them over the years because of past problems. One time I had a defective cable, another time one of the hotswap bays had the wrong mounting screws, causing a faulty connection. Never really kept track of where each specific disk is because Unraid remembers their IDs anyway. The thing is, I can't (or rather, couldn't) even complete the short test. It got stuck at 90% before showing the message "Interrupted (host reset)". In an attempt to fix this, I restarted the server, and the read errors have gone away. I assume they're still actually there though, and I'll try to run an extended test. First I'm backing everything important up.
  10. And just one extra question which I'm not 100% sure is related: does a parity sync achieve the same things as a parity check? I performed a parity sync about a fortnight ago. Would there be any point in starting a parity check less than a month later?
  11. I noticed these errors started appearing in my log. The reads and writes on my array tab are all incrementing, except for Disk 3 which is remaining completely static at 1,375,745 reads and 581 writes. At first only disk0(parity drive) had errors, but now multiple disks do. Sep 6 23:24:45 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x3fc00 SErr 0x0 action 0x0 Sep 6 23:24:45 Tower kernel: ata6.00: irq_stat 0x40000008 Sep 6 23:24:45 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Sep 6 23:24:45 Tower kernel: ata6.00: cmd 60/08:50:f8:8c:37/04:00:26:00:00/40 tag 10 ncq dma 528384 in Sep 6 23:24:45 Tower kernel: res 41/40:00:f8:8c:37/00:00:26:00:00/40 Emask 0x409 (media error) <F> Sep 6 23:24:45 Tower kernel: ata6.00: status: { DRDY ERR } Sep 6 23:24:45 Tower kernel: ata6.00: error: { UNC } Sep 6 23:24:45 Tower kernel: ata6.00: ATA Identify Device Log not supported Sep 6 23:24:45 Tower kernel: ata6.00: ATA Identify Device Log not supported Sep 6 23:24:45 Tower kernel: ata6.00: configured for UDMA/133 Sep 6 23:24:45 Tower kernel: sd 6:0:0:0: [sde] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=7s Sep 6 23:24:45 Tower kernel: sd 6:0:0:0: [sde] tag#10 Sense Key : 0x3 [current] Sep 6 23:24:45 Tower kernel: sd 6:0:0:0: [sde] tag#10 ASC=0x11 ASCQ=0x4 Sep 6 23:24:45 Tower kernel: sd 6:0:0:0: [sde] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 26 37 8c f8 00 00 04 08 00 00 Sep 6 23:24:45 Tower kernel: blk_update_request: I/O error, dev sde, sector 641174776 op 0x0:(READ) flags 0x0 phys_seg 129 prio class 0 Sep 6 23:24:45 Tower kernel: md: disk0 read error, sector=641174712 Sep 6 23:24:45 Tower kernel: md: disk0 read error, sector=641174720 Sep 6 23:24:45 Tower kernel: md: disk0 read error, sector=641174728 Sep 6 23:24:45 Tower kernel: md: disk0 read error, sector=641174736 Sep 6 23:24:45 Tower kernel: md: disk0 read error, sector=641174744 Sep 6 23:24:45 Tower kernel: md: disk0 read error, sector=641174752 And they're continuing in intervals. Sep 6 23:41:25 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x3fe8 SErr 0x0 action 0x0 Sep 6 23:41:25 Tower kernel: ata6.00: irq_stat 0x40000008 Sep 6 23:41:25 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Sep 6 23:41:25 Tower kernel: ata6.00: cmd 60/40:18:b8:54:b2/05:00:93:00:00/40 tag 3 ncq dma 688128 in Sep 6 23:41:25 Tower kernel: res 41/40:00:b8:54:b2/00:00:93:00:00/40 Emask 0x409 (media error) <F> Sep 6 23:41:25 Tower kernel: ata6.00: status: { DRDY ERR } Sep 6 23:41:25 Tower kernel: ata6.00: error: { UNC } Sep 6 23:41:25 Tower kernel: ata6.00: ATA Identify Device Log not supported Sep 6 23:41:25 Tower kernel: ata6.00: ATA Identify Device Log not supported Sep 6 23:41:25 Tower kernel: ata6.00: configured for UDMA/133 Sep 6 23:41:25 Tower kernel: sd 6:0:0:0: [sde] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=7s Sep 6 23:41:25 Tower kernel: sd 6:0:0:0: [sde] tag#3 Sense Key : 0x3 [current] Sep 6 23:41:25 Tower kernel: sd 6:0:0:0: [sde] tag#3 ASC=0x11 ASCQ=0x4 Sep 6 23:41:25 Tower kernel: sd 6:0:0:0: [sde] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 93 b2 54 b8 00 00 05 40 00 00 Sep 6 23:41:25 Tower kernel: blk_update_request: I/O error, dev sde, sector 2477937848 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 0 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937784 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937792 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937800 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937808 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937816 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937824 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937832 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937840 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937848 Sep 6 23:41:25 Tower kernel: md: disk0 read error, sector=2477937856 Sep 7 00:00:48 Tower kernel: ata9.00: cmd 60/08:18:68:71:11/05:00:9e:00:00/40 tag 3 ncq dma 659456 in Sep 7 00:00:48 Tower kernel: res 41/40:00:68:71:11/00:00:9e:00:00/40 Emask 0x409 (media error) <F> Sep 7 00:00:48 Tower kernel: ata9.00: status: { DRDY ERR } Sep 7 00:00:48 Tower kernel: ata9.00: error: { UNC } Sep 7 00:00:48 Tower kernel: ata9.00: ATA Identify Device Log not supported Sep 7 00:00:48 Tower kernel: ata9.00: ATA Identify Device Log not supported Sep 7 00:00:48 Tower kernel: ata9.00: configured for UDMA/133 Sep 7 00:00:48 Tower kernel: sd 9:0:0:0: [sdf] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=7s Sep 7 00:00:48 Tower kernel: sd 9:0:0:0: [sdf] tag#3 Sense Key : 0x3 [current] Sep 7 00:00:48 Tower kernel: sd 9:0:0:0: [sdf] tag#3 ASC=0x11 ASCQ=0x4 Sep 7 00:00:48 Tower kernel: sd 9:0:0:0: [sdf] tag#3 CDB: opcode=0x28 28 00 9e 11 71 68 00 05 08 00 Sep 7 00:00:48 Tower kernel: blk_update_request: I/O error, dev sdf, sector 2651943272 op 0x0:(READ) flags 0x0 phys_seg 161 prio class 0 Sep 7 00:00:48 Tower kernel: md: disk2 read error, sector=2651943208 Sep 7 00:00:48 Tower kernel: md: disk2 read error, sector=2651943216 Sep 7 00:00:48 Tower kernel: md: disk2 read error, sector=2651943224 Sep 7 00:00:48 Tower kernel: md: disk2 read error, sector=2651943232 Sep 7 00:00:48 Tower kernel: md: disk2 read error, sector=2651943240 Sep 7 00:00:48 Tower kernel: md: disk2 read error, sector=2651943248 Diagnostics attached. Also attached a SMART test for the parity drive, although it got stuck on 90% and won't complete. Says "Interrupted (host reset)". For what it's worth, a couple of weeks ago I had some big problems with power failures and didn't have a UPS working at the time. tower-diagnostics-20220906-1405.zip (disk0) tower-smart-20220906-2339.zip
  12. Where can new icons be submitted? Here? The github page? I want to submit one for YunoHost.
  13. About 3 years ago when I built my server, I chose an Asus B450M-A + Ryzen2400G because I figured that's all I needed at the time. I've since decided I want to both expand my storage array with an HBA Card and pass through a NIC so I can virtualize my router. Maybe even throw in a GPU too. The problem is the B450M only has one PCIe slot so I'm going to have to upgrade at some point. Some questions I have: Does ECC work with consumer-grade Ryzen CPUs? I've heard conflicting information on this. I just bought x2 16TB drives and I'm looking to set up a new array for important data, so ECC is something I'm looking into, but I'd rather not invest in an expensive server-grade motherboard + CPU (all server motherboards seem to be expensive where I live). Is DDR5 worth it for Unraid? What are some good value for money motherboards that offer good power efficiency and lots of room for PCIe expansion?
  14. I just updated this container, and it broke it. My log keeps showing the message s6-supervise pihole-dot-doh (child): fatal: unable to exec run: Permission denied
  15. It had been a while since I last made a VM in Unraid, and when assigning a vdisk size, I forgot you're supposed to postfix it with the letter "G" to assign it in gigabytes.
  16. Problem solved. Yet another case of dumb user error. Close this awful thread.
  17. root@Tower:~# ls -lah /mnt/cache/system/docker total 25G drwxrwxrwx 1 nobody users 20 Aug 21 23:53 ./ drwxrwxrwx 1 nobody users 26 Dec 21 2019 ../ -rw-rw-rw- 1 nobody users 25G Sep 1 22:40 docker.img root@Tower:~# ls -lah /mnt/disk2/system/docker total 25G drwxrwxrwx 2 nobody users 24 Nov 23 2019 ./ drwxrwxrwx 3 nobody users 20 Nov 23 2019 ../ -rw-rw-rw- 1 nobody users 25G Aug 21 23:53 docker.img root@Tower:~# I guess I had a docker image on disk 2 after all. Not that it's of big consequence, after all the persistent data is fine.
  18. Thanks! Sorry for bothering you with this dumb user error.
  19. The log shows this being repeated: time="2022-09-01T16:02:17+10:00" level=fatal msg="default addr for network '192.168.1.5:3306/photoprism' unknown" started 220730-bookworm as root (amd64-prod) init: updating filesystem permissions PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them: https://docs.photoprism.app/getting-started/troubleshooting/ file umask....: "0002" (u=rwx,g=rwx,o=rx) home directory: /photoprism assets path...: /opt/photoprism/assets storage path..: /photoprism/storage config path...: default cache path....: default backup path...: /photoprism/storage/backups import path...: /photoprism/import originals path: /photoprism/originals switching to uid 99:100 /opt/photoprism/bin/photoprism start Both are on Bridge.
  20. Yeah, I created a database called photoprism, a user called photoprism, and granted all privileges to the user. Did the exact same thing for my Nextcloud database. How do you ping from Photoprism? Also as a side note, when I open both the console and the log window for Photoprism, the window always crashes after about 5-10 seconds.
  21. The PhotoPrism container isn't working for me. I configured a database for it in mariadb and the MySQL Database Connection field looks like this: photoprism:[email protected]:3306/photoprism/photoprism?parseTime=true But the WebUI won't load. Also it doesn't seem to have created anything in the database folder in my mariadb appdata directory.
  22. Yeah sorry about that. Parity did sync and I sort of forgot about this thread. I came back and replied because I was also asking about a VM-related issue on the VM forum. I did have a "disk2 has read errors error" yesterday, although I haven't noticed anything wrong besides that. They all look fine on the array menu. tower-diagnostics-20220831-2114.zip
  23. root@UnraidServer:~# ls -lah /mnt/cache/system total 16K drwxrwxrwx 1 nobody users 26 Dec 21 2019 ./ drwxrwxrwx 1 nobody users 102 Aug 31 14:40 ../ drwxrwxrwx 1 nobody users 20 Aug 21 23:53 docker/ drwxrwxrwx 1 nobody users 22 Dec 21 2019 libvirt/ root@UnraidServer:~# ls -lah /mnt/disk2/system total 0 drwxrwxrwx 3 nobody users 20 Nov 23 2019 ./ drwxrwxrwx 10 nobody users 137 Aug 31 14:40 ../ drwxrwxrwx 2 nobody users 24 Nov 23 2019 docker/ root@UnraidServer:~#
  24. This tutorial no longer works. The PfSense VM simply cannot load the installation screen while Primary vDisk Bus is set to SATA.