Sparkyy

Not sure where I went wrong this time around as I have another RAID1 under the Unassigned Devices plugin. I put in 2 NVMe drives on my motherboard, started following the steps from this link here: However, when doing this portion of the instructions: btrfs dev add -f /dev/nvme0n1p1 /mnt/disks/MyPath. I get the error of, ERROR: /dev/nvme0n1p1 is mounted. Isn't that what I want or need? I tried to unmount the share but then the share isn't found. I stopped the array and tried mount and unmount with the same but exact same error messages.

Just wanting to find out if it was possible to rearrange the numbers listed? It seems as though Supermicro likes to count from bottom to top and left to right. So my case actually goes like this: 5...11...17...23 4...10...16...22 3...9...15...21 2...8...14...20 1...7...13...19 0...6...12...18 This more of a cosmetic thing but just thought I would reach out.

Where do you see the format error? I can't reproduce it. You can't change the device_serial number. To change the name, click on the serial number, then on the mount point and change the name, then press 'Enter'. I knew it was something simple and easy! Thank you again for that. I have attached two screenshots of me formatting the drive. First shows the format failed and then the second is of the drive mounted. As I said, looks like everything works, I can create a docker.img on the drive, make folders, even set up a docker template and had it running. So just an oddity. Can you post the UD log so I can see the format log entries? The log under UD, just right of the share On/Off option is blank. So is the partition one as well. Click on the 'Help' button and you'll see a 'Download Log' button at the bottom. Click on that buttom to download the UD log. Thanks for that and sent.

Where do you see the format error? I can't reproduce it. You can't change the device_serial number. To change the name, click on the serial number, then on the mount point and change the name, then press 'Enter'. I knew it was something simple and easy! Thank you again for that. I have attached two screenshots of me formatting the drive. First shows the format failed and then the second is of the drive mounted. As I said, looks like everything works, I can create a docker.img on the drive, make folders, even set up a docker template and had it running. So just an oddity. Can you post the UD log so I can see the format log entries? The log under UD, just right of the share On/Off option is blank. So is the partition one as well.

Where do you see the format error? I can't reproduce it. You can't change the device_serial number. To change the name, click on the serial number, then on the mount point and change the name, then press 'Enter'. I knew it was something simple and easy! Thank you again for that. I have attached two screenshots of me formatting the drive. First shows the format failed and then the second is of the drive mounted. As I said, looks like everything works, I can create a docker.img on the drive, make folders, even set up a docker template and had it running. So just an oddity.

Thank you again for your hard work.

Hopefully someone can help me out with this task. Got the Unassigned devices plug in set up and working and enabled destructive mode to format the device. My problem is, I don't want the name it provides. I saw I just need to mount the drive and it auto stuffs it into the disks area but I don't know Linux. How can I set the device name to 'Docker' since that is going to be it's role and make it easier and cleaner if I need to share it out. As opposed to see the 'drivename_serial' that is there now. Thank you! Also, when I format the drive as xfs, it says 'Format failed' but the drive still mounts and was even able to set up docker.img on it.

Thank you again for your hard work on this plugin.

Thank you moose. I was going to post up something similar as well about it wanting, at least it looks like, an older version of the program. I cannot thank you enough for this plugin, I always wait until this is updated as well. It's a life saver for those of us running ESXi!

Not sure if this was mentioned in the last 18 pages but is there any update on using the IBM M1015 in regards to drive spin down support and drive temp readings? I ask because on page one they are both still listed as Cannot determined unless driver is added and tested. I saw where it say the M1015 would become the LSI SAS9211 which has support for both drive spin down and drive temp readings but rather be safe and find out then get the hardware and it doesn't work.