If the response is helpful, please click " Accept Answer "and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. Thank you for your answer.
I hoped for better solution. I asked Dell forum, bud they haven't helped me yet. I will upload solution after I will get it. Thank your for your reply and hope things are going well. The solution may help others with the similar needs. Thanks for your time! Skip to main content. Find threads, tags, and users I will deal with manufacturers of other brands later :- 1, What do I need to upload to Dell openmanage on the device? The issue you are seeing is due to the fact the that the Raid controller, when presented with a larger or faster drive, will slow or show the drive at the lower speed or size.
Now that doesn't make the space above the 67GB unacceptable, but you would have to access the controller or OpenManage perform a rescan, then you configure that additional space into a new virtual disk.
Which in turn would then show in the OS as a new drive. There is not a "Task" column where I believe this would be done. The PERC 6 does not support "rescan". You cannot "expand" the existing array by replacing the disks with larger ones.
Browse Community. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Last reply by theflash Unsolved. Hello, I have a pesky PE which I just upgraded all its firmware to their latest versions that refuses to allow the OS riding on top Windows R2 to see the new GB drive expansion size. All forum topics Previous Topic Next Topic.
Replies 3. SuperCell29, The issue you are seeing is due to the fact the that the Raid controller, when presented with a larger or faster drive, will slow or show the drive at the lower speed or size.
Machine I'm testing from is on a Mb wired connection. The server has 3x 1Gb links. I've established where the issue comes from and its to do with the network configuration on the host. The Ubuntu host has 2x 1G interfaces bonded into bond0. This LACP interface is then bridged with a 3rd 1G interface to form the bridged interface br0 The issue arises when the VMs run a bridged interface virtio off br0.
0コメント