Adubs

Yes, the folder stays behind in appdata. There is an 'Appdata Cleanup' plugin which can show you what folders are not currently assigned to a container and remove them. Tread carefully. The intent with these directories is the software is not persistent, but the data the software relies on is... so deleting one version of a container to use another version can be as simple as mapping the same paths.

I just tested this both ways and it does work, so I'm leaning towards whatever db name, user, or pass you initially put in is not what you have in there now and its not going to update that for you. You probably still want to use the IP of the server rather than docker in case that happens to change down the road. The server should be static. Your config is otherwise correct.

your database URL should be the IP of the unraid server if you're using bridged, it should be possible to use the docker network too but im not certain. you will need to include the port number for either. I would blow away the folder for the database in your appdata folder and start over there. The fields on the DB container for DB name, user, and password are only executed on first run so if you changed those fields after, you're going to get errors. alternatively you could add the database to your existing mariadb instance with some relatively simple commands.

you configure the password on the database name, user, and password on the mariadb container, then enter it into the booklore template. Post your logs.

So what you have to do now is add 2 variables to specify UID/GID for the container and chown the directory in appdata make a new variable: Name: User ID Key: USER_ID Value: 99 Default: 99 Description: Unraid User ID Then repeat for group ID make a new variable: Name: Group ID Key: GROUP_ID Value: 100 Default: 100 Description: Unraid Group ID Finally start a console and enter: chown -R 99:100 /mnt/user/appdata/booklore/ You should now be able to do everything as expected. I'm not certain what it was before, I assume 1000/1000 as that would be root which is fine™ for unraid but less than ideal for everything else. They're probably trying to bring this in line with best practices on other distros which is understandable. These changes should be fairly straight forward to implement on the template but anyone running without these variables initially is going to struggle.

I had to go through the terminal to see the full log history but long story short, it seems like they expect a path variable for bookdrop now. add a new path Name: Bookdrop Container path: /bookdrop Host Path: /mnt/user/appdata/booklore/bookdrop_temp Default Value: /mnt/user/appdata/booklore/bookdrop_temp Description: Path for bookdrop uploads. I'm having issues now with being able to save book covers to the images directory but it doesnt appear to be a permissions issue as I can enter the container and write to that path. Still working through that one.

You are connecting the disk to your unraid server? If so do you have the unassigned devices plus plugin? You would need to mount it to use it within unraid.

Nevermind... I had somehow configured the smart controller type to ATA, but it should be use default. After correcting it is working as expected.

I have a SATA SSD that refuses to properly display the smart data in the unraid UI. Its a 4TB 860 EVO. I purchased it used so I had considered it might be a fake, but Samsung Magician has no issues identifying it and crystaldiskinfo shows all relevant data. When at Unraids terminal I can see the smart data. root@Hyperion:~# smartctl -x /dev/sdc smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.24-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 860 EVO 4TB Serial Number: S596NE0N100749D LU WWN Device Id: 5 002538 e101299f8 Firmware Version: RVT04B6Q User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available, deterministic, zeroed Device is: In smartctl database 7.3/5706 ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed Oct 22 17:06:52 2025 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 320) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 9 Power_On_Hours -O--CK 099 099 000 - 3243 12 Power_Cycle_Count -O--CK 095 095 000 - 4080 177 Wear_Leveling_Count PO--C- 099 099 000 - 5 179 Used_Rsvd_Blk_Cnt_Tot PO--C- 100 100 010 - 0 181 Program_Fail_Cnt_Total -O--CK 100 100 010 - 0 182 Erase_Fail_Count_Total -O--CK 100 100 010 - 0 183 Runtime_Bad_Block PO--C- 100 100 010 - 0 187 Uncorrectable_Error_Cnt -O--CK 100 100 000 - 0 190 Airflow_Temperature_Cel -O--CK 072 059 000 - 28 195 ECC_Error_Rate -O-RC- 200 200 000 - 0 199 CRC_Error_Count -OSRCK 092 092 000 - 7157 235 POR_Recovery_Count -O--C- 099 099 000 - 66 241 Total_LBAs_Written -O--CK 099 099 000 - 25176669341 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 SL VS 16 Device vendor specific log 0xa5 SL VS 16 Device vendor specific log 0xce SL VS 16 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2085 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing 256 0 65535 Read_scanning was never started Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) Device State: Active (0) Current Temperature: 28 Celsius Power Cycle Min/Max Temperature: 23/28 Celsius Lifetime Min/Max Temperature: 21/41 Celsius Specified Max Operating Temperature: 70 Celsius Under/Over Temperature Limit Count: 0/0 SMART Status: 0xc24f (PASSED) SCT Temperature History Version: 2 Temperature Sampling Period: 10 minutes Temperature Logging Interval: 10 minutes Min/Max recommended Temperature: 0/70 Celsius Min/Max Temperature Limit: 0/70 Celsius Temperature History Size (Index): 128 (63) Index Estimated Time Temperature Celsius 64 2025-10-21 19:50 ? - ... ..( 3 skipped). .. - 68 2025-10-21 20:30 ? - 69 2025-10-21 20:40 29 ********** 70 2025-10-21 20:50 ? - ... ..( 2 skipped). .. - 73 2025-10-21 21:20 ? - 74 2025-10-21 21:30 27 ******** 75 2025-10-21 21:40 ? - ... ..( 9 skipped). .. - 85 2025-10-21 23:20 ? - 86 2025-10-21 23:30 29 ********** 87 2025-10-21 23:40 25 ****** 88 2025-10-21 23:50 24 ***** ... ..( 3 skipped). .. ***** 92 2025-10-22 00:30 24 ***** 93 2025-10-22 00:40 ? - 94 2025-10-22 00:50 29 ********** 95 2025-10-22 01:00 29 ********** 96 2025-10-22 01:10 30 *********** 97 2025-10-22 01:20 29 ********** 98 2025-10-22 01:30 30 *********** 99 2025-10-22 01:40 30 *********** 100 2025-10-22 01:50 30 *********** 101 2025-10-22 02:00 31 ************ 102 2025-10-22 02:10 30 *********** 103 2025-10-22 02:20 30 *********** 104 2025-10-22 02:30 29 ********** 105 2025-10-22 02:40 29 ********** 106 2025-10-22 02:50 29 ********** 107 2025-10-22 03:00 30 *********** 108 2025-10-22 03:10 31 ************ 109 2025-10-22 03:20 30 *********** 110 2025-10-22 03:30 30 *********** 111 2025-10-22 03:40 31 ************ 112 2025-10-22 03:50 30 *********** 113 2025-10-22 04:00 30 *********** 114 2025-10-22 04:10 31 ************ 115 2025-10-22 04:20 30 *********** 116 2025-10-22 04:30 29 ********** 117 2025-10-22 04:40 29 ********** 118 2025-10-22 04:50 30 *********** 119 2025-10-22 05:00 30 *********** 120 2025-10-22 05:10 29 ********** ... ..( 3 skipped). .. ********** 124 2025-10-22 05:50 29 ********** 125 2025-10-22 06:00 ? - 126 2025-10-22 06:10 25 ****** 127 2025-10-22 06:20 26 ******* 0 2025-10-22 06:30 26 ******* 1 2025-10-22 06:40 26 ******* 2 2025-10-22 06:50 23 **** 3 2025-10-22 07:00 20 * ... ..( 9 skipped). .. * 13 2025-10-22 08:40 20 * 14 2025-10-22 08:50 21 ** ... ..( 13 skipped). .. ** 28 2025-10-22 11:10 21 ** 29 2025-10-22 11:20 22 *** ... ..( 8 skipped). .. *** 38 2025-10-22 12:50 22 *** 39 2025-10-22 13:00 23 **** ... ..( 7 skipped). .. **** 47 2025-10-22 14:20 23 **** 48 2025-10-22 14:30 24 ***** ... ..( 3 skipped). .. ***** 52 2025-10-22 15:10 24 ***** 53 2025-10-22 15:20 23 **** ... ..( 5 skipped). .. **** 59 2025-10-22 16:20 23 **** 60 2025-10-22 16:30 ? - 61 2025-10-22 16:40 28 ********* 62 2025-10-22 16:50 24 ***** 63 2025-10-22 17:00 23 **** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 4080 --- Lifetime Power-On Resets 0x01 0x010 4 3243 --- Power-on Hours 0x01 0x018 6 25176669341 --- Logical Sectors Written 0x01 0x020 6 266257243 --- Number of Write Commands 0x01 0x028 6 54624281204 --- Logical Sectors Read 0x01 0x030 6 819765091 --- Number of Read Commands 0x01 0x038 6 622000 --- Date and Time TimeStamp 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 1596 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 28 --- Current Temperature 0x05 0x020 1 41 --- Highest Temperature 0x05 0x028 1 21 --- Lowest Temperature 0x05 0x058 1 70 --- Specified Maximum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 13009 --- Number of Hardware Resets 0x06 0x010 4 0 --- Number of ASR Events 0x06 0x018 4 7157 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 0 N-- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 2 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC I dont see anything wrong with the drive. Yes it has quite a few CRC errors but those have not changed in any meaningful way since I have begun to use it. I have rebooted, and tried different spots in the hot swap bays. Has anyone seen anything like this before? hyperion-diagnostics-20251022-1718.zip

You made the same mistake I did of thinking the server port and webUI port needed to be changed. Server port is the internal port, so you can leave it as 8080. The WebUI port can be 8079 or whatever you'd like.

I was able to connect to the console using your provided command but inputs dont seem to be doing anything. I am unable to OP myself. I am doing this from the web terminal in unraid. I cant help but feel like I'm missing something obvious here.