Everything posted by Blade
-
Supermicro X9DRH set RPM for certain fans
yes they do I am thinking of just removing the pwm line
-
Supermicro X9DRH set RPM for certain fans
Yes they are all noctua NF-A14 PWM
-
Supermicro X9DRH set RPM for certain fans
Hi I would like to set the RPM higher for FAN3 and FAN4 on my Supermicro X9DRH motherboard I am using the IPMI plugin and it works good but the RPM for FAN3 and 4 are quite low FAN1 and 2 for the CPUs are fine but 3 and 4 need to be higher Is there a way to do this? Thanks
-
Moving data drives from one tower to another
Thank you
-
Moving data drives from one tower to another
OK so I would powerdown the tower and add the drives from the other tower, then power it up but do not start the array Then go to new config.. I assume I preserve current assignments. Then I would assign the drives in new slots and then start the array and parity will get rebuilt Am I correct?
-
Moving data drives from one tower to another
I am trying to eliminate an unraid system. Is it possible to add the 4 data drives from it into my other bigger tower and assign them and setup shares for them They are all xfs drives What is the proper way to do this or can it be done? Thanks
-
Rackmount device to expand HDD storage
Right now my tower is full with 2 parity drives and 13 data drives Is there a separate rackmount device I could use to extend the HDD storage and possibly run more drives off a SAS card in my unraid tower Has anyone done something like this? Thanks
-
Unraid api crashed while updating dockers
Can anyone provide any insight into this Attach is log tower2-diagnostics-20240121-1224.zip
-
[Plugin] CA Appdata Backup / Restore v2.5
This will work - Thanks
-
[Plugin] CA Appdata Backup / Restore v2.5
OK would be awesome because I think something happend yesterday with the backup and my parity check running and caused unraid to just go off into its own world and not respond to anything
-
[Plugin] CA Appdata Backup / Restore v2.5
Is there a way to bypass the backup if a monthly parity check is in progress?
-
Tower was not responsive
I could not get to the web UI or ping the tower Can anyone see issues in the attached syslog tower2-syslog-20230501-0950.zip
-
Dockers acting weird after some time
This has becoming a growing issue where after some time the dockers seem to have issue and stop \ A reboot seems to fix the issue but it is occurring more and more now I have attached my logs tower2-diagnostics-20230416-1712.zip
-
/mnt/user looks odd now
Tower has been running fine I noticed some dockers would not start - saying Execution error I looked at my shares and I noticed that /mnt/user looks odd drwxrwxrwt 2 nobody users 40 Mar 9 12:59 rootshare/ d????????? ? ? ? ? ? user/ drwxrwxrwx 1 nobody users 62 Mar 12 16:26 user0/ Anyone have any ideas?
-
Added new data drive but I am not seeing it
I used a different power cable and it seems ok now I guess that power cable is bad
-
Added new data drive but I am not seeing it
I just added a new 4tb data drive but I am not seeing it in the unassigned devices Attached is my syslog tower3-syslog-20230309-1135.zip
-
[Support] binhex - NZBHydra2
How can I revert back to previous image because it worked fine?
-
[Support] binhex - NZBHydra2
I updated to latest and now docker does not start 2023-01-23 06:52:31,240 DEBG 'start-script' stdout output: 2023-01-23 06:52:31.234 ERROR --- [ main] org.nzbhydra.NzbHydra : FATAL: An unexpected error occurred during startup: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Found non-empty schema(s) "PUBLIC" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Found non-empty schema(s) "PUBLIC" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table. at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1751) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:599) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:521) at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:326) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:324) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:313) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200) at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1130) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:905) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:584) at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:730) at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:432) Caused by: org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "PUBLIC" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table. at org.flywaydb.core.Flyway.lambda$migrate$0(Flyway.java:166) at org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:204) at org.flywaydb.core.Flyway.migrate(Flyway.java:128) at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:66) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1797) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1747) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:599) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:521) at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:326) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:324) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:313) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200) at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1130) 2023-01-23 06:52:37,764 DEBG 'start-script' stdout output: 2023-01-23 06:52:37,764 ERROR - Main process shut down unexpectedly. If the wrapper was started in daemon mode you might not see the error output. Start Hydra manually with the same parameters in the same environment to see it 2023-01-23 06:52:37,777 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23241208409072 for <Subprocess at 23241208404080 with name start-script in state RUNNING> (stdout)> 2023-01-23 06:52:37,777 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23241208409024 for <Subprocess at 23241208404080 with name start-script in state RUNNING> (stderr)> 2023-01-23 06:52:37,778 WARN exited: start-script (exit status 255; not expected) 2023-01-23 06:52:37,778 DEBG received SIGCHLD indicating a child quit
-
Anyone got Idrive working on Unraid ?
OK I got the dashboard service running I do not see the linux computer in the list of computers on the iDrive web interface though It mentions that it should show there and you can configure backups using the web interface
-
Anyone got Idrive working on Unraid ?
@stalkerama This is what I get and I do not see my linux machine in the list of computers root@Tower:/mnt/cache/appdata/iDrive# ./Status_Retrieval_Script.pl ========================================================================================== Version: 2.29 Developed By: IDrive Inc. ------------- --------------------------------------------- Status: Logged In IDrive Username: xxxxxxxxxxxxxxxxx ----------------- --------------------------------------------- Storage Used: 55.98 MB of 10000.00 GB Linux Username: root ========================================================================================== Warning(s): * Dashboard service has stopped. ------------------------------------------------------------------------------------------ No Backup/Express Backup/Restore Job is running.
-
Anyone got Idrive working on Unraid ?
I am trying to set this up for iDrive but I am getting this when running the account_setting.pl script I downloaded 2.29 version of scripts Verifying your account information... Starting Dashboard service... Failed to start Dashboard service.
-
Says my flash drive is corrupt
Yep had to build a new flash drive and get my license transferred over
-
Says my flash drive is corrupt
I have attached my syslog tower-syslog-20220830-1013.zip
-
I ran 2 preclears on 2 new disks
I added 2 new 4tb disks to my array and ran 2 preclears on them One is still running fine but the other one appears to no longer be running and I no longer see that disk as unassigned I have attached the sylog Is it a bad disk or can I not run 2 preclears at the same time? Thanks tower2-syslog-20210905-0146.zip
-
[Support] Linuxserver.io - Nextcloud
Worked perfectly - thank you so much