itimpi

Tools->Diagnostics to get the diagnostics zip file.

Can you provide the system diagnostics zip file (obtained via Tools->Diagnostics) covering an attempt to add this disk to see if we can work out what might be happening?

I am surprised you think you need a new motherboard to go LSI? This is the first time I can recollect where that has been mentioned as an issue. What makes you think this? What motherboard do you currently have? You are correct in that the SASLP controllers seemed fine on v5. The suspicion is that the Linux 64-bit drivers that v6 uses are not as reliable as the 32-bit ones that v5 used. They seem to work fine most of the time with v6, but some users find that they are prone to 'dropping' disks without any obvious reason. You are also on quite an old Unraid release (the current stable being 6.6.7 with 6.7.0 getting close to going Stable). It might be possible to go back to v5 (although that means hardly anyone here could then help with issues), but if you do not have a copy in your archives then you may need to contact Limetech to see if they can provide a link to the last v5 release (5.06 I think). Also remember that v5 only supported disks in ReiserFS format so if you have any drives that are in XFS or BTRFS format going back to v5 is unlikely to be practical.

Another way to approach this might be to download one of the later 6.x vmdk's where the partition size seems to be 1GB, and then copy the contents of whatever Unraid release you want to use on top of the existing contents.

Coming out of Maintenance mode would not trigger a parity check (the whole idea if Maintenance mode is to maintain parity while doing something like a file system repair). Do you know why the system wants to run a parity check (e.g. did you have an unclean shutdown).

The way this works under the covers is at the time the disk is selected the selection code does NOT know the file size. That is why having a sensible value for the Minimum Free Space is important.

The cut-overs are based on the largest disk. Since that is 4TB the first cut-over is 2TB. However since no drive is larger than 2TB and the 4TB drive still has 2TB free no cut-over occurs. As was said the next cutover-point will be 1TB. You willthen get 1TB written to each of the 2TB drives.

I have changed the vdisk size on VMs without the effect on the network that you describe. I expect that there is something else going on in your case. i would not expect the ‘df’ command to show anything different until you have run an appropriate partition management tool (e.g. gparted) inside the VM under Linux. Unraid may increase the physical size of the emulated disk but it will not touch the partitions/file systems on the vdisk - that is up to the VM to do so.

I have used both NoMachine and RDP with Linux VMs so I would say those suggestions are both relevant.

Since each drive from an Unraid system contains a complete file system it can be mounted outside of the array. You could mount an old drive using the Unassigned Devices plugin (I.e. do not add it to the array). The data can then be copied onto the new drive(s). Repeat for as many of the old drives as needed.

Setting the appdata to Use Cache = No does not achieve what you want? You actually need Use Cache=Yes to achieve what you want. If you turn on the Help in the GUI this might make it clearer as it describes how the various Use Cache options interact with mover. Regarding the format options if you have more than one cache drive you are only going to be offered BTRFS options. You get offered other options if you have a single cache drive. You can safely change the format to BTRFS encrypted and format the drive. After that stop the array and change it back to BTRFS (assuming that is what you want) restart the array and run the format again.

You can get a sound card emulated by editing the VM settings in XML mode and adding <sound model='ac97'> </sound> As to what the quality of sound you will get and what the best client to use is I am not sure.

That is a subset of the information returned by the CLI level 'uptime' command. Perhaps you had not realised that 'uptime' is a standard command?

Fair enough. However in this case I want an existing built-in page (not customised) to also use the revised version of the script so my way may still be appropriate? I did check that the existing script is only called from one place in the current GUI, and since the script simply populates a pop-up it will not affect normal operation.

The easiest way is to: The normal process is to have the vdisk in a user Share that has "Use Cache = Prefer". Stop the VM Service. Run mover and it will transfer the vdisk to the array (or you can do it manually instead). It is only User Shares that have Use Cache = Yes that results in files being moved from cache to array. Now restart the VM service and you should be good to go. If in your VM you have explicitly named a particular disk rather than a user share then the procedure s slightly different as you have to edit the references in your VM configuration to match the new location.