JonathanM
-
Posts
16,594 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JonathanM
-
-
If you have docker containers, the customized templates are stored on the flash drive, so those will need to be redone. Many times they will run with their last config, but they won't update or edit properly.
-
It's the command that tells the drive's firmware to pretty much start over with data allocation, it can help if there are cells that couldn't be optimized for some reason or another.
-
1
-
-
7 minutes ago, stephenmoore33 said:
Can you please elaborate a little more?
Different motherboards have different settings exposed, I don't know what options you have available. Exhaustively go through each CMOS item and subitem, sometimes advanced settings are hidden under sub menus.
-
14 minutes ago, toughiv said:
Surely this is an UnRaid issue?
If it is, then it's specific to your setup, so very difficult for Unraid to fix.
So it restarts with no containers or VM's while in safe mode?
-
40 minutes ago, uglytuna said:
Would have never guessed that one of the SSDs was bad.
Possibly not bad, it may be ok after a full blkdiscard.
-
I suspected that was the case, but since you didn't volunteer your local IP addresses, all I could do is point you there.
41 minutes ago, Nothingbutkale said:(Dont know the technical terms for it but in layman's terms the PC is higher on the river than the WIFI)
20 hours ago, JonathanM said:Same subnet?
That's the question I asked, and you just confirmed they weren't on the same network segment.
-
And you've tried all the different USB port modes in BIOS?
-
Try disabling fast boot.
-
Maybe it would help to chart out your IP schema, and which can and can't ping each other.
Router IP (most likely the gateway address)
Surface IP
Workstation IP
Unraid IP
At the command prompt of the Surface, workstation and Unraid, check which ones can and can't be reached. You should end up with a list of which devices can successfully reach each IP.
e.g.
from the command prompt of the Surface - pings router, workstation and Unraid OK
from the command prompt of the Workstation - pings router, Surface, but not Unraid
from the command prompt of Unraid - pings router, Surface, but not Workstation
or something like that.
-
If the main PC is using windows of some flavor, is the network connection set as private or public?
-
Same subnet? Can you ping the router IP from the PC and Unraid's console?
-
Can you ping the IP from the PC?
-
What do you get when you browse to the address that works on your Surface using your main PC?
-
6 minutes ago, Bcj said:
When plugging directing into the server, all I get is a black screen.
See if you can get in to the BIOS and check the boot order.
7 minutes ago, Bcj said:Recently I added a new fan to the case
Soiunds like you disturbed something when you were in the case.
-
Rebalance from RAID1 to Single.
Keep in mind if either drive has an error, you will lose the content of the entire pool.
It defaults to RAID1 for data redundancy.
-
22 minutes ago, Phantom-Verde said:
Am I doing this wrong?
Yes. Set the secondary storage to array, and the mover direction from array to cache.
-
Honestly, at this point it would be good for you to just have a play. If you start the array with the failed disk unavailable, then the next disk that is assigned to that slot will be used for the rebuild. The emulated failed drive data should be available any time the array is started.
A larger drive will automatically expand during the rebuild, and for reasons that are obvious when you know how parity works, it's impossible to use a smaller drive to rebuild. The replacement drive can be any size from equal to the failed drive, up to and including the size of the smallest parity drive.
-
3 minutes ago, live4soccer7 said:
@JonathanM I'm not sure I understand. Is that a question?
Nope, I was answering your question.
/mnt/user = array + pools
/mnt/user0 = array only
-
1 hour ago, live4soccer7 said:
or whatever reason under /mnt I have /user and /user0. Any ideas on why/how this would be?
array + pools or array only
-
1 hour ago, BOBOkingbbe9 said:
started searching the forums for some horror storys, came up lacking so far.
The biggest issue tends to be when it comes time to migrate to different hardware, Unraid identifies the drives with hardware identification, which RAID controllers don't pass intact. One of the biggest benefits of Unraid is the ability to move the drives to almost any plain vanilla platform, as long as the disk controller is a plain HBA the drives will be detected and used without any changes needed at all.
Sometimes RAID controllers alter the drive's geometry, which can put the partition at a location that isn't compatible when the drive is moved to different hardware, causing unmountable drives.
USB instead of SATA or SAS is very hit or miss, typically miss. The USB bus resets can and do cause writes to fail, and Unraid will drop the drive when a write fails.
Another issue for many people (not for you, you seem to have this taken care of) is that Unraid's ability to monitor and report on disk health is disabled by many RAID controllers. If a drive is failing, you want to investigate, and possibly replace the drive sooner rather than later. Unraid (like most RAID) requires the entire capacity of all the data drives and the parity drive to rebuild a failed drive. The reason it's super important with Unraid compared to other RAID setups, is that in the Unraid parity array disks are allowed to spin down when not accessed, which means a drive can possibly go months without being touched, but when another drive fails the spun down drives are all required to be read perfectly.
As long as you keep good backups you will be fine. The issue is simply that you are bypassing or hamstringing many of the features and safeguards built into Unraid to help protect your data. People tend to get upset when they lose data, so we try to mitigate as many causes as possible.
-
Just now, Xyler94 said:
It's the file size that Windows File Explorer shows when I look for the vdisk from the share itself.
That will only show the reserved space, not what's actually occupied.
-
3 minutes ago, Xyler94 said:
I check my Windows Server VM, and the vdisk size is 200GB, which is exactly what I set the limit as. This would indicate a thick provision from my understanding, no?
Depends on how you check the size. At the command line use "ls -l -s" That's LS -L -S lowercase. That will show you both actual space used and the allocation limit.
-
Probably won't change anything, but in general the min-max memory doesn't work like you think it should, and probably should be set to the same amount.
-
Another thing to investigate would be a client machine that has access to the files could be infected with ransomware. I've seen behaviour where the original file was renamed, and an encrypted copy written with the original name. The end result would be the deletion of the randomly named files, but maybe not all the actions are able to happen over a remote share.
-
1
-
Have Firefox Remember Important Settings
in Feature Requests
Posted
The built in browser is only updated when a new upgrade of Unraid is released, so the chances are good that a vulnerability may be exposed with no way to immediately mitigate it. Given that it's running on the base OS, if it's exploited your entire Unraid install is vulnerable.
The only reason the GUI browser was included at all was to give the local console the ability to manage Unraid. For general use, it's highly recommended to only use the built in browser to launch a VM or container that can be used as a daily driver. If the local GUI becomes unusable for any reason it would be very bad.
Consider what could happen if you accidentally open a page with an exploit that allows remote access, or starts ransomware. It would have access to your whole server.
Much safer to sandbox your activities with a container or VM.