jmztaylor

I have already moved too much stuff around and off of disk7. I will just finish moving everything and add it back and format it. Is this a possible drive issue or just something got messed up?

root@Tower:~# xfs_repair -v /dev/mapper/md7p1 Phase 1 - find and verify superblock... - block cache size set to 1503144 entries Phase 2 - using internal log - zero log... zero_log: head block 2063886 tail block 2063868 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 the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. 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.

Its not emulated. /mnt/disk7 does not exist. Even though the webui says emulated. I can verify the files on disk7 do not exist in the shares they were assigned.

I did but its still not wanting to mount it without formatting it. Just for ease, I am able to mount it with unassigned plugin and moving everything off of it right now. I will just add it to the array again and format it when done

It wasn't replaced as after repair it was functioning again. Currently if I try to assign the disk to the array it wants to format it and doesn't even emulate the contents.

attached tower-diagnostics-20260708-1017 2.zip

I got it back up for a few days but the same exact thing happened today.

Noticed a disk was offline. Shut it down, verified all connections and started it back up. Met with Unmountable: wrong or no file system. Nearly every reboot has caused a parity re read lately so that is not good timing. Also unable to start in maintenance mode. Check the box, hit start and it just reloads the page. Got it into maintenance mode after a couple reboots. Disk 7 xfs check says Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. Clicking fix results in Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... 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 the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. 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. tower-diagnostics-20260702-1337 2.zip

Fairly new install. No WebUI or SSH. But I can access everything from the server. I can ping gateway and google. I can ssh from this unraid install to anywhere. EDIT: Not sure what was going on. After changing IP to see if there was a conflict, I rebooted and got a kernel panic. Hard rebooted it and it seems to be working again. diagnostics.zip

Well I made sure to choose the right option and it seemed to have worked. Somehow there was a cache pool created and it wouldn't let me remove it. So I deleted the pool.cfg and rebooted. Was able to get back up after a weird license issue also.

Yeah thats the thing. I know without a doubt I chose that boot+data option. I will wipe and try it again.

Attached. According to fdisk it has 4 partitions on it. tower-diagnostics-20260613-1421.zip

have it ingest the rss feed I think its unique to your user. Its the RSS link at the bottom left of the page here.

On the same topic. Another unraid server I have I needed to reconfigure and reinstall. I have to booting from the ssd without usb just fine. But I can't assign shares to the device. Shares tab says no array or pool devices. The docs say It lets you choose a dedicated boot pool for boot-only devices, or a boot + data pool when you want to reserve part of a larger device for boot and use the remaining capacity as a normal pool. https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/internal-boot-faq/#internal-boot-benefits

LSI MegaRAID SAS 2008

Went through onboarding wizard. Chose 2 drives, rebooted, failed to boot. So I disabled secure boot and it booted past grub. Now its in a boot loop with the last log message, waiting for boot drive to come online.

I am able to get my docker image pulled by simply using docker login, but the problem I run into is the built in update checker doesn't use this and just says not available. Is there any workaround for this or am I just doing docker pull, delete and recreate manually?

Someone else is more than welcome. I needed more stability than Booklore and now a new one. I ended up writing my own opds server and mobile app as my needs are a lot less than booklore features.

Try using the lan IP instead of the docker IP

I updated the template to include these.

For anyone that uses it for only OPDS like me, https://github.com/Node-Dog-Consulting/python-opds/pkgs/container/opds This is a very simple and dumbed down version of the OPDS standard. All I needed was the book listing, downloading, and the cover image. There is no web ui for this. Just map the container path of /books to wherever your books are. Not sure if I will put more effort into this to name it and publish it to Community Apps. I built my own ereader so most of booklore was useless to me.

Yeah it seems I am going to move away from Booklore. I already have my own reader I wrote so I will just wrap my own opds service. Too many hard breaking changes from Booklore and not going to keep chasing rabbit holes.

How did you force an update EDIT: I opened an issue as I confirmed this locally as well. https://github.com/booklore-app/booklore/issues/2867

Is localhost in your db URL? If so, it should be your server IP

My previous thread had the same symptoms. But mine was usually within a few hours. The only thing that worked for me was to rebuild the flash drive and only copying the bare minimum files over needed to preserve disk assignments and docker containers. I don't have VMs so not sure what is required to keep those.