mikela
-
Posts
104 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by mikela
-
-
4 minutes ago, dlandon said:
If you're going to put it into the array, don't clear the disk. Unraid will format it. Preclearing creates a partition, but does not create a file system. That's why it is not mountable.
So just stop the array and put it in position 10 and unraid will recognize the preclear signature and format it ?
-
15 minutes ago, dlandon said:
Click on the red X next to the disk serial to clear the disk and then format the disk.
I started to do that but read the following warning:
"If this disk was pre-cleared, you will remove the pre-clear signature. If you add the disk to the array and the pre-clear signature is removed, Unraid will go through the lengthy process of clearing the disk again."
-
I did a preclear over the course of several days shutting down at night. It successfully completed. However, the "Mount" button was greyed out so I deleted the preclear log per the instructions and still am not able to mount.
Do I need to stop the array and press the red x to clear the disk?
-
On 6/2/2022 at 11:20 AM, JorgeB said:
It shouldn't make any difference, you'll see the BIOS screen when a boot device is not found, try a different USB port/hub and make sure it's USB 2.0.
Switching to a USB 2.0 port on the back of my rack mounted server seems to have worked.
I swapped out my old Cruzer USB 2.0 drive with a Samsung BAR Plus USB 3.0 drive based on this review by gridrunner (aka SpaceInvader One). Before trying the 2.0 port, I had been using this USB board adapter since my original build. I have been using the Samsung 3.0 drive since April without any problems. Only recently did I start having problems. I reseated the adapter and continued to use the 3.0 drive. That worked for awhile before reverting to previous behavior (failing to load the OS). Taking the advice of @JorgeB and moving the Samsung drive to a 2.0 port seems to have cured the issue at least so far.
-
1
-
-
56 minutes ago, itimpi said:
Looking at the diagnostics I think you started the array with the new disk9, and later stopped the array and unassigned it and restarted the array? This would cause Unraid to start ‘emulating’ disk9, so that when you later added it back in it wanted to rebuild it because it was now assuming that you were in a failed disk scenario. It then looked as though you formatted the emulated disk, and Unraid is now attempting to rebuild an empty file system on the physical disk9.
I believe you are right. Definitely operator error on my part.
Is there any way to recover?
Should I just let it rebuild?
-
I was able to get my new 8TB drive precleared over the course of several days while stopping in the evenings and then resuming. However, the "Mount" button was greyed out so I stopped the array and assigned the drive to the array. I selected for the drive to be formatted but it seems that unraid wants to rebuild so I stopped everything for the moment and ran a diagnostic. Thoughts?
tower-diagnostics-20220606-1054.zip
-
I am still getting an intermittent issue where sometimes my server will boot up without any issues or will attempt to boot up and I wind up with this screen:
I have a dual mount USB adapter on the mother board. If I unseat the adapter and reseat it, it seems to boot successfully and I temporarily get the following screen:
The blue section in the bios screen is hard to read but says "My Favorite" and it looks like it is giving me the option to delete it. Is that something I should do? Even though I reseat the USB adapter, it does not always boot properly...color me perplexed.
-
I prefer to not operate my server over night. I started a manual parity check off of the Main tab and got to about 8.5%. Then I shutdown. Later I restarted and started parity check which proceeded to start from 0. Is this expected behavior or am I doing something wrong? I was assuming that I would be able to resume. I am on the latest version of Unraid and am using the default settings with the exception of "Use increments for manual parity check:" which is set to Y. I have "Scheduled parity check:" set to disabled.
-
I'm guessing the diagnostics did not reveal any anomalous information. Everything started normally today. Fingers crossed.
-
I have 8TB drives which take quite awhile to preclear. I need to be able to shutdown my server nightly. Is my understanding correct that I can shut down the server while Preclear is running and that upon start up it will resume?
-
1 hour ago, jmztaylor said:
Yes that would be the best option. If you can access it from SSH then you can just run the diagnostics command and the file will be on your flash drive in the logs folder.
OK that worked. I was able to log in that way. My laptop was able to get the GUI. So it seemed like everything was working again. So I shutdown and tried with the just the laptop and no go. I then tried the direct connection route again and now it was dumping me into the bios menu where it was indicating 404 Error. I tried reseating the thumb drive and now it works again. There is something intermittent going on apparently. In any case, it's running right now so I ran a diagnostic.
-
24 minutes ago, jmztaylor said:
Whats the hardware? Are you able to access via SSH? Please post diagnostics.
Here is my hardware. I can't seem to reach my unraid login screen via my laptop at all and therefore can't post diagnostics. I'm wondering if hooking up my screen and keyboard directly to the server should be my next move?
-
Unlike many folks, I turn off my server every day. I only use it for my home theater and don't want it running 24/7. Recently I tried to reach the Login screen from my PC like I always do and received the message "This site can't be reached". I also do not have access to any files. Not sure where to go from here. Any assistance would be greatly appreciated.
-
I always dismiss the nag screen. It always updates the next time I start my server. Unlike many, I shut down my server daily.
-
Discover works for me.
-
I tried my first "restore" from a saved backup. It worked. I also tried to "restore" from a previous backup that was made prior to separating apps and app data as described earlier in this thread. I could not get that one to work. Looks like all back ups going forward should work. Really excited to use Roon as originally intended.
Thanks to all who assisted in getting this docker workable!!!
-
3 hours ago, xrqp said:
MULTIPLE FILE LOCATIONS FOR MUSIC
With this container, can you add multiple file locations for music?
Do you have to add them in both 1) the container mappings and 2) in the app mappings?
In this paragraph, I am showing the mappings as they appear in Windows file viewer, where Z: is my Unraid Tower.
I am currently mapping both app and container using a relatively direct share "Z:\music\".
I want to add another location, less direct, in a different share called "data" like this "Z:\data\media\music".
Can I do that, and if I can, do I need to add it to both the app and the container mappings?
Thanks.
For mapping to multiple music locations start reading at this post.
-
6 hours ago, Kendel said:
Looks like you are sending both the roonserver app and data to the same location.
-
That worked!
Thanks!
-
4 minutes ago, dkerlee said:
Mapping two locations to /music is probably the issues. Just map to another folder. For instance:
1. music 2/ > /music
2. music (Blu-ray)/ > /music2
Then, in Roon, simply point it at BOTH /music and /music2
Ahhh...that makes total sense. I'll give it a shot and report back.
-
1
-
-
Here are my settings without adding the additional path:
I tried to add another path: /mnt/user/music (Blu-ray)/ to the Container Path: /music
I just noticed that my share is actually "Music (Blu-ray) and now I can't remember if I used the lower case in my attempt.
-
On 12/19/2020 at 11:31 PM, DaveW42 said:
1) MULTIPLE MUSIC DIRECTORIES: I have my music files in separate directories. The template by default provides a single entry for your music directory. I went ahead and entered one of my music directories, and then later I tried to add another directory using the main Roon interface (i.e., in the settings, storage area of Roon Remote). Needless to say, it didn't work after numerous attempts. After searching a bit I learned that docker containers can't really see your host file system, unless you map (mount?) particular directories. This is done through the aforementioned template, by selecting "Add another Path, Port, Variable, Label or Device," and then you just follow the formatting example established for the first music directory you set up.
Hey folks, I just tried to add a second music folder following this approach and got an error message indicating a duplicate mount directory. Am I missing something?
-
First time it's ever worked for me 👍
-
1
-
-
Unassigned Devices Preclear - a utility to preclear disks before adding them to the array
in Plugin Support
Posted
Success!
Thank you for this wonderful plugin. Really great for those of us that need to shutdown our servers at night. 👍