pwm

Multiple arrays are great. More than two parity drives is great. But remember that parity is intended for improved availability - it is not a replacement for backup. So you should really, really look into cheap USB disks and copy out your "must not lose" data on them and then store them at parents/children/friends. A single "big oops" with the PSU may kill all drives in the machine. And a fire may kill all data on every piece of hardware in the house. So only use single storage for data you can afford to lose, whatever number of parity drives you may be allowed use of.

Gamers really are worried about input lag for mouse/keyboard. And it can be shown that every x mouse clicks will be delayed another display redraw even for a single 1ms delay of the click. But since this requires statistical methods, it shouldn't matter much for most users who aren't using real-time-streaming devices. Besides using statistical methods, the lag can't be seen. Standard keyboards/mice have 125 Hz poll rate just because we aren't fast enough to notice the delay even when the key presses are only polled every 8 ms. But with 100 fps, a 128 Hz poll rate means half the key presses will be delayed one additional display refresh and in some games that will be measurable in damage-per-second or similar.

Yes you can forward USB devices to a VM. Some people forward a complete USB host controller for maximum functionality, but in most situatuations it will work well to just forward individual devices.

Yes, the update speed have been way higher the last year. And lots of the changes have been very useful for a larger group of users.

You should normally not be able to notice with keyboard/mouse. A traditional keyboard/mouse has a quite slow report rate - maybe 125 Hz report rate. It's only gaming keyboards/mouses that make use of 1kHz report rate. And we humans aren't fast enough to measure such short delays. But when the game responds to key presses or mouse clicks synchronized with the display frame rate, then one in x mouse clicks may result in the game responding one display redraw earlier which for 100 frames/second could scale a 1ms mouse lag into a 10ms slower game response. Where it normally matters for non-gamers is when using USB sound cards, JTAG-interfaces, logic analyzers etc that streams synchronous data that may require hard real time (a bit depending on buffer capacity on each side). But for this type of devices, I have - in some situations - clearly seen a difference between having the VM own the USB host or just bridging the USB device. But it matters what other hardware shares the interrupts on the host machine and what load the host machine has (and quality of drivers), so it can work very well even with streaming devices. But a single slow critical section in the kernel can starve the USB processing enough to affect the transfer.

Did you need the extra transfer speed? RAID-0 means you lose all data if one drive fails.

Backblaze also see failed Seagate drives. But they note that they buy the Seagate drives cheaper than WD Red drives. And since their infrastructure can handle broken disks, it's more profitable with the Seagate disks. If 5 disks in 100 fails, that still only represents 5% of the purchase cost - and if they buy the drives 15% cheaper than WD Red and the WD drives maybe have 3 disks in 100 fail then it's clearly an advantage to select Seagate drives. For normal home users, it doesn't work well to consider amortized costs like that - we don't have the same routines to maintain redundancy even with multiple broken disks. And we don't have the same routines to restore data to new disks. And we have so few disks, that a single broken disk will represent a significant percentage of the total purchase price of the storage server disks.

But the poster of the bitmap can at least spot if the bitmap doesn't look the same as the text output. When I look at the bitmap from my monitor, it looks the same as the text above/below. But I intentionally cropped down the width to reduce the probability of the forum scaling it in the inline view.

Filled speech bubbles means you have been busy filling it. Empty speech bubbles means the thread is waiting for you to fill it with good content. Grayed speech bubbles means no new content.

Viewing at 1:1 is obviously important. But the DPI decides how many 1:1 pixels that are used to render a 12point font, since the point system relates to an inch - there are 72 pica points in an inch and when rendering to printer or display, the computer needs to figure out how many pixels the output medium fits in an inch. Viewing that bitmap at 1:1 on a different monitor with a different DPI will show the characters larger or smaller than on the original system, since the pixel sizes will differ. Apple have been using the term Retina for a rather large span of DPI - from about 220 DPI to 460 DPI. Lots of Windows installations are also using quite arbitrary DPI settings, i.e. Windows isn't configured to match the true DPI of the monitor - that's a common trick to force rendered information to be larger or smaller.

Note that the look of the screenshots doesn't just depend on system and web browser, but also on what DPI the display is configured for. So a screen shot from a QHD or 4k monitor isn't likely to look similar to a screen shot from a monitor with lower DPI. And lots of mobile phones are configured to run with quite low DPI (to preserve the battery) even if the native display is high-resolution.

With the forum having moved to unraid.net, it's definitely best to stay away from own DNS entries of type x.unraid.net, since you can't know what subdomains Limes may introduce. so x.unraid.local would definitely be a better choice, given that .local is a reserved name for broadcast-local network trees.

Extended SMART tests aren't really good friends with disk rebuilds. Both the rebuild and the extended SMART test requires access to all of the disk surface.

A newer layout may have introduced some changes in the block structure or tag labels that trigs the ad blocker. Ad blockers hae manual white- and blacklist options just because they can never be 100% correct - they will sometimes misunderstand content.

I would also be quite worried that the old flash drive might have been added to the blacklist, blocking any future updates. And it's quite important that Limes checks the error codes to get the key management server aligned with any other changes introduced during the domain name move.

I'm quite good with HTML but leaves the true CSS magic to professionals. I know what the CSS constructs does, but doesn't have the professional knowledge about what goofs different web browsers suffers from and what workarounds that are needed. My speciality is in systems-level coding, electronics and interfacing directly with the hardware. So quite far from web front-end work.

There are quite a lot of 404 links right now, especially if searching on Google. But the bug reports subforum link should probably get some priority. https://forums.unraid.net/forum/66-bug-reports/

When the web designers knows what they are doing, then you shouldn't see much difference between browsers unless the user have decided to explicitly tweak their browser. I'm still curious why the typekit download doesn't work for some users.

It's just that lots of stores are starting to focus on selling USB 3.0 devices since the cost difference is low. But besides giving more boot problems depending on motherboard etc, USB 3.0 devices tends to be very hot so they cook the flash memory. Every 10°C warmer flash memory means the retention time for the data is halved. So a 20°C warmer flash memory has only one fourth the retention time. And unRAID doesn't constantly write to the flash so the content isn't regularly getting refreshed.

Most people don't need to worry about more than a normal burglar - or about being able to send in a drive for warranty replacement even when the drive interface is dead so the content can't be overwritten. But it's always good to notify people about potential limitations. Lots of uses have heard about AES-256 and thinks AES-128 is too unsafe to use - and then use a 20-30 bit password to unlock their 256-bit encryption key (assuming that each character of English text is worth about 3-4 bits of security). And lots of users wants "extra high" security so they use key files representing maybe a million bits of security (regarding the randomnes of the file contents) to unlock a 128-bit AES even when nothing they do can make the system safer than the 128-bit AES key. And then they follow up by forgetting that their server only has 100k files and an attacker can ignore the amount of noise in the "key" photo and just try the 100k files one-by-one. Or read the configuration file that names the key file and the host that stores the key file. Hopefully the new web site can result in people stepping in and reworking the FAQ texts.

Most USB 2 drives from Kingston and Sandisk should work well. Just with a slight warning for drives with tiny form factor. And a big warning for USB 3 devices. I have one system with a datatraveler - I think it's a SE9. It has worked well for maybe 5 years. (But I have seen people have issues with SE9 G2 that is USB 3) I also have a system with a Sandisk Cruzer Blade - also maybe 5 years of perfect function.

At least some Cruzer Fit drives runs quite hot because of the small size. But the USB 2 variantes are at least cooler than the USB 3 variants. Unless you are worried that someone will bump into the drive, it might be better to go for a full-size thumb drive.

Just note that Microsoft has a number of patents you can license for free. So even when patents are involved, you don't always need to pay anything. And this is possible for both commercial and open-source products. But Microsoft has managed to make the situation so complicated that they have to recommend users to contact them for formal answers: https://msdn.microsoft.com/en-us/openspecifications/dn750984 "please contact the IP Licensing Team" The problem comes from RDP involving multiple patents where an RDP client doesn't need coverage of all - and it isn't obvious which patents are needed. You have one patent for handling of user state of remote desktops in a cloud. And another patent for secure sessions. A third for handling transparency in a remote desktop. A fourth for double-buffering when doing remote desktop sharing. ... Different RDP clients may have different patent needs, and Microsoft needs to help out with which patents are relating to the Patent Promises program and which patents are not. And that is probably also why the wikipedia page can't know the actual state for different clients.

Alas quite a lot of 404 links right now to unraid.net. Just hours since this forum moved from a limes technology domain name to unraid.net. So I bet the admins has lots of work to do to catch 404 requests and apply redirects.