thx4nothing

2.5 Weeks ago one of my drives failed, ordered a new one after christmas and plugged it in today. Both are/were 8TB, same manufacturer (WD MyBooks, 1 shucked, 1 not). Trying to replace the failed drive gives the error message mentioned in the title. HPA: max sectors = 15628053168/1(15628053168?), HPA setting seems invalid (buggy kernel device driver?) Syslog size: Jan 7 15:25:38 X kernel: md: import disk5: (sdc) WDC_WD80EZAZ-X size: 7814026532 Jan 7 15:25:38 X kernel: md: import disk6: (sdj) WD_My_Book_25ED_X-0:0 size: 7814026188 Here you can see that the size differs by 344. But the SMART logs of both the old and new drive report the same size: User Capacity: 8,001,563,222,016 bytes [8.00 TB] I usually shuck my drives (e.g. sdc), but this time, because I can not access my server right now, I didn't. I am currently staying in a different country (won't be home for another 8 months) and my parents helped me get the new drive connected via USB as I thought shucking and plugging the drive in via SATA would be too much of a hassle for them. I read about HPA, but this only seems to be about Gigabyte motherboards? I have an ASRock. Could the USB Controller somehow be a possible source for the missing 344kb? I know that sizes can differ per drive, but I read that it should be the same for the same manufacturer (all my disks are MyBooks).... Any advice on how to "reclaim" the lost 344kb or what my next best move could be? If possible, I would like to avoid having my parents do the shucking of the drive and putting it in the (rather messy) server. I don't have another drive I could use to copy the missing data and do a new config. I attached the SMART log of the old failed drive and the diagnostics of the server. TL;DR: 1. New drive size reported as too small. Syslog size difference 344; SMART Log same capacity. 2. Old and new drive same product (WD MyBooks); old was shucked (SATA), new one wasn't (USB) 3. HPA invalid? (Doesn't seem to be a factor here though?) 4. Can't physically access server myself right now -> Can't shuck the drive and plug it in via SATA to test if USB Controller is at fault. 5. Don't have another data drive to temporary copy missing data (would probably be 6TB) and do a new config. WDC_WD80EDBZ-11B0ZA0_VRJMSSUK-20221222-2317.txt kuri-diagnostics-20230108-0020.zip

I fixed it. The path is the same as yours and I have enough space, but I just didn't notice that the /usr/share/elasticsearch/data path is inside the cointainer... haha (in my defense, I never saw a variable for a path inside the container before). Anyways, it couldn't create the files and folders because it lacked permissions. I used the same command "chown..." as earlier and now it successfully created all the things and it works now! Thanks!

It looks a bit different, but the important bits are the same: Just to confirm, I only need the TubeArchivist, TubeArchivist-RedisJSON and TubeArchivist-ES containers, right? Do I need to install something else?

I can't get ES to start. It can't find (access?) the path.repo. I didn't change it from the default as it said in the installation guide. It says to check the log at /usr/share/elasticsearch/logs/docker-cluster.log, but the file (and folders) are not there. I tried creating the elasticsearch folder and setting the permissions (chown 1000:0 -R) manually, but still the same error. I'm on unRAID Version: 6.10.3 and installed TubeArchivist for the first time. Docker log: @timestamp=2022-12-03T07:10:09.032Zecs.version=1.2.0elasticsearch.cluster.name=docker-clusterelasticsearch.node.name=3092b8c09c8aerror.message=Unable to access 'path.repo' (/usr/share/elasticsearch/data/snapshot)error.stack_trace=java.lang.IllegalStateException: Unable to access 'path.repo' (/usr/share/elasticsearch/data/snapshot) at [email protected]/org.elasticsearch.bootstrap.FilePermissionUtils.addDirectoryPath(FilePermissionUtils.java:66) at [email protected]/org.elasticsearch.bootstrap.Security.addFilePermissions(Security.java:252) at [email protected]/org.elasticsearch.bootstrap.Security.createPermissions(Security.java:178) at [email protected]/org.elasticsearch.bootstrap.Security.configure(Security.java:125) at [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:186) at [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:66) Caused by: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data/snapshot at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:90) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:397) at java.base/java.nio.file.Files.createDirectory(Files.java:700) at java.base/java.nio.file.Files.createAndCheckIsDirectory(Files.java:807) at java.base/java.nio.file.Files.createDirectories(Files.java:793) at [email protected]/org.elasticsearch.bootstrap.Security.ensureDirectoryExists(Security.java:330) at [email protected]/org.elasticsearch.bootstrap.FilePermissionUtils.addDirectoryPath(FilePermissionUtils.java:64) ... 5 more error.type=java.lang.IllegalStateExceptionevent.dataset=elasticsearch.serverlog.level=ERRORlog.logger=org.elasticsearch.bootstrap.Elasticsearchmessage=fatal exception while booting Elasticsearchprocess.thread.name=mainservice.name=ES_ECS 03/12/2022 16:10:09 ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/docker-cluster.log 03/12/2022 16:10:09 ERROR: Elasticsearch exited unexpectedly