Setting Up Network RAID1 With DRBD On Debian Squeeze:
'via Blog this'
Sunday, 24 July 2016
Monday, 4 July 2016
Creating a tiered virtual disk in Windows Server 2016 VM using VirtualBox as hypervisor
I've been playing with Windows Server 2016 as a VM inside VirtualBox, but despite VirtualBox being able to mark virtual disks as an SSD disk, I was unable to create any tiered Storage Spaces inside the guest VM.
The VM disks (hosted as virtual disks on an actual SSD) were marked as SSD correctly:
Turns out that the SSD disks weren't the problem, it was the HDD which were coming up as UnSpecified:
Get-PhysicalDisk | select FriendlyName, UniqueId, MediaType, Size
FriendlyName UniqueId MediaType Size
------------ -------- --------- ----
VBOX HARDDISK {01c1a62b-e1d6-1910-b251-09f3ae1b2047} UnSpecified 214748364800
VBOX HARDDISK {12fcf70b-b805-183a-f1a8-103d6b91ba70} UnSpecified 34359738368
VBOX HARDDISK {31b25faa-db05-490a-7acd-a8927a2b569f} UnSpecified 214748364800
VBOX HARDDISK {45fc2705-9a13-1afc-a554-0ded23d9e78b} UnSpecified 214748364800
VBOX HARDDISK {50642166-ca99-47ce-2f87-b5b4f2c19254} SSD 21474836480
VBOX HARDDISK {57b897e4-f98a-3330-dbc2-6a5ab6749742} SSD 21474836480
VBOX HARDDISK {769a2aa9-a289-7627-24ef-6b3a2fcff2bb} SSD 21474836480
VBOX HARDDISK {a1a9e55d-68b9-7eb3-11dd-6348bb837642} UnSpecified 214748364800
VBOX HARDDISK {d98baa0d-b0df-74ea-ac87-d107998e79ed} SSD 21474836480
The commands below won't work if the disks are still in the primordial pool, so you need to use either the GUI or PowerShell to create the pool first. Once that is done you can edit change the FriendlyName and the MediaType using Powershell.
I was able to rename and reclassify the HDD's like so:
Set-PhysicalDisk -UniqueId '{01c1a62b-e1d6-1910-b251-09f3ae1b2047}' -NewFriendlyName HDD1 -MediaType HDD
Set-PhysicalDisk -UniqueId '{31b25faa-db05-490a-7acd-a8927a2b569f}' -NewFriendlyName HDD2 -MediaType HDD
Set-PhysicalDisk -UniqueId '{45fc2705-9a13-1afc-a554-0ded23d9e78b}' -NewFriendlyName HDD3 -MediaType HDD
Set-PhysicalDisk -UniqueId '{a1a9e55d-68b9-7eb3-11dd-6348bb837642}' -NewFriendlyName HDD4 -MediaType HDD
I was also able to rename the SSD devices to make them more obvious:
Set-PhysicalDisk -UniqueId '{50642166-ca99-47ce-2f87-b5b4f2c19254}' -NewFriendlyName SDD1
Set-PhysicalDisk -UniqueId '{57b897e4-f98a-3330-dbc2-6a5ab6749742}' -NewFriendlyName SDD2
Set-PhysicalDisk -UniqueId '{769a2aa9-a289-7627-24ef-6b3a2fcff2bb}' -NewFriendlyName SDD3
Set-PhysicalDisk -UniqueId '{d98baa0d-b0df-74ea-ac87-d107998e79ed}' -NewFriendlyName SDD4
The disks were now identified correctly and I could create my tiered virtual disks:
FriendlyName UniqueId MediaType Size
------------ -------- --------- ----
HDD1 {01c1a62b-e1d6-1910-b251-09f3ae1b2047} HDD 214748364800
VBOX HARDDISK {12fcf70b-b805-183a-f1a8-103d6b91ba70} UnSpecified 34359738368
HDD2 {31b25faa-db05-490a-7acd-a8927a2b569f} HDD 214748364800
HDD3 {45fc2705-9a13-1afc-a554-0ded23d9e78b} HDD 214748364800
SDD1 {50642166-ca99-47ce-2f87-b5b4f2c19254} SSD 21474836480
SDD2 {57b897e4-f98a-3330-dbc2-6a5ab6749742} SSD 21474836480
SDD3 {769a2aa9-a289-7627-24ef-6b3a2fcff2bb} SSD 21474836480
HDD4 {a1a9e55d-68b9-7eb3-11dd-6348bb837642} HDD 214748364800
SDD4 {d98baa0d-b0df-74ea-ac87-d107998e79ed} SSD 21474836480
Everything looked good in the GUI too:
The VM disks (hosted as virtual disks on an actual SSD) were marked as SSD correctly:
Turns out that the SSD disks weren't the problem, it was the HDD which were coming up as UnSpecified:
Get-PhysicalDisk | select FriendlyName, UniqueId, MediaType, Size
FriendlyName UniqueId MediaType Size
------------ -------- --------- ----
VBOX HARDDISK {01c1a62b-e1d6-1910-b251-09f3ae1b2047} UnSpecified 214748364800
VBOX HARDDISK {12fcf70b-b805-183a-f1a8-103d6b91ba70} UnSpecified 34359738368
VBOX HARDDISK {31b25faa-db05-490a-7acd-a8927a2b569f} UnSpecified 214748364800
VBOX HARDDISK {45fc2705-9a13-1afc-a554-0ded23d9e78b} UnSpecified 214748364800
VBOX HARDDISK {50642166-ca99-47ce-2f87-b5b4f2c19254} SSD 21474836480
VBOX HARDDISK {57b897e4-f98a-3330-dbc2-6a5ab6749742} SSD 21474836480
VBOX HARDDISK {769a2aa9-a289-7627-24ef-6b3a2fcff2bb} SSD 21474836480
VBOX HARDDISK {a1a9e55d-68b9-7eb3-11dd-6348bb837642} UnSpecified 214748364800
VBOX HARDDISK {d98baa0d-b0df-74ea-ac87-d107998e79ed} SSD 21474836480
The commands below won't work if the disks are still in the primordial pool, so you need to use either the GUI or PowerShell to create the pool first. Once that is done you can edit change the FriendlyName and the MediaType using Powershell.
I was able to rename and reclassify the HDD's like so:
Set-PhysicalDisk -UniqueId '{01c1a62b-e1d6-1910-b251-09f3ae1b2047}' -NewFriendlyName HDD1 -MediaType HDD
Set-PhysicalDisk -UniqueId '{31b25faa-db05-490a-7acd-a8927a2b569f}' -NewFriendlyName HDD2 -MediaType HDD
Set-PhysicalDisk -UniqueId '{45fc2705-9a13-1afc-a554-0ded23d9e78b}' -NewFriendlyName HDD3 -MediaType HDD
Set-PhysicalDisk -UniqueId '{a1a9e55d-68b9-7eb3-11dd-6348bb837642}' -NewFriendlyName HDD4 -MediaType HDD
I was also able to rename the SSD devices to make them more obvious:
Set-PhysicalDisk -UniqueId '{50642166-ca99-47ce-2f87-b5b4f2c19254}' -NewFriendlyName SDD1
Set-PhysicalDisk -UniqueId '{57b897e4-f98a-3330-dbc2-6a5ab6749742}' -NewFriendlyName SDD2
Set-PhysicalDisk -UniqueId '{769a2aa9-a289-7627-24ef-6b3a2fcff2bb}' -NewFriendlyName SDD3
Set-PhysicalDisk -UniqueId '{d98baa0d-b0df-74ea-ac87-d107998e79ed}' -NewFriendlyName SDD4
The disks were now identified correctly and I could create my tiered virtual disks:
FriendlyName UniqueId MediaType Size
------------ -------- --------- ----
HDD1 {01c1a62b-e1d6-1910-b251-09f3ae1b2047} HDD 214748364800
VBOX HARDDISK {12fcf70b-b805-183a-f1a8-103d6b91ba70} UnSpecified 34359738368
HDD2 {31b25faa-db05-490a-7acd-a8927a2b569f} HDD 214748364800
HDD3 {45fc2705-9a13-1afc-a554-0ded23d9e78b} HDD 214748364800
SDD1 {50642166-ca99-47ce-2f87-b5b4f2c19254} SSD 21474836480
SDD2 {57b897e4-f98a-3330-dbc2-6a5ab6749742} SSD 21474836480
SDD3 {769a2aa9-a289-7627-24ef-6b3a2fcff2bb} SSD 21474836480
HDD4 {a1a9e55d-68b9-7eb3-11dd-6348bb837642} HDD 214748364800
SDD4 {d98baa0d-b0df-74ea-ac87-d107998e79ed} SSD 21474836480
Everything looked good in the GUI too:
Friday, 24 June 2016
Google Chrome on Ubuntu 16.04
On reinstalling this today onto a stock install of Ubuntu 16.04, I had a couple of unmet dependencies. I sorted it out with:
sudo apt install libappindicator1 libindicator7
sudo apt install libappindicator1 libindicator7
Wednesday, 8 June 2016
renew Openvas 8 Certificates
This happens on a yearly basis and always left my scratching my head:
openvas-mkcert -q -f 'Refreshes the server certificate for a year
openvas-mkcert-client -n -i 'Refresahes the client certificate for a year
reboot
openvas-mkcert -q -f 'Refreshes the server certificate for a year
openvas-mkcert-client -n -i 'Refresahes the client certificate for a year
reboot
Wednesday, 1 June 2016
A Networker's Log File: Single Sign On for RD Web Access (WS2012)
A Networker's Log File: Single Sign On for RD Web Access (WS2012):
This worked for me on 2008R2 as well.
Set the "Allow Delegating Default Credentials" etc on Local computer using gpedit.msc and Local Computer policy.
'via Blog this'
This worked for me on 2008R2 as well.
Set the "Allow Delegating Default Credentials" etc on Local computer using gpedit.msc and Local Computer policy.
'via Blog this'
Friday, 27 May 2016
Drivers & Software - HP Support Center.
Drivers & Software - HP Support Center.:
Update to v6.0.1.7657 Rev C of Hp Realtek Audio Driver
'via Blog this'
Update to v6.0.1.7657 Rev C of Hp Realtek Audio Driver
'via Blog this'
Microphone too quiet on HP ZBook 15u G2 - HP Support Forum - 5637322
Microphone too quiet on HP ZBook 15u G2 - HP Support Forum - 5637322:
I'm getting quite frustrated not being able to online conference with my audio mic.
'via Blog this'
I'm getting quite frustrated not being able to online conference with my audio mic.
'via Blog this'
Monday, 23 May 2016
Saturday, 21 May 2016
Booting Tails 2.3 on HP Zbook 15 G2
I've had issues with the last few versions of Tails on my HP ZBook G2 and with the new version 2.3 released in April thought I'd have another look.
There are quite a few workrounds on the Tails page for laptops with dual graphic adaptors, but none of them worked for me.
The ZBook seems to boot in Intel HD graphics and then switch to Radeon graphics on login.
The display is then only active for a few seconds before crashing to the boot text. All you can do then is press the power button to shut down.
Failsafe mode wasn't really acceptable as it seems to be software driven and was very slow, so, after a bit of experimentation I found hitting TAB on the Grub boot screen and appending 'radeon.modeset=0' (without the quotes) allowed Tails to boot into a stable, fast desktop. I know it's only using the Intel graphics now, but I don't think Tails needs the high power Radeon adaptor anyway.
I then tried to find a way to make this permanent.
After more experimentation I found that you could remount the boot media with a read-write flag and then change the appropriate .cfg files with:
To use use sudo, you need to set a password on boot with the 'More Options' dialog, and you have to append the 'radeon.modeset=0" manually the first time you boot to be able to do the above.
There are quite a few workrounds on the Tails page for laptops with dual graphic adaptors, but none of them worked for me.
The ZBook seems to boot in Intel HD graphics and then switch to Radeon graphics on login.
The display is then only active for a few seconds before crashing to the boot text. All you can do then is press the power button to shut down.
Failsafe mode wasn't really acceptable as it seems to be software driven and was very slow, so, after a bit of experimentation I found hitting TAB on the Grub boot screen and appending 'radeon.modeset=0' (without the quotes) allowed Tails to boot into a stable, fast desktop. I know it's only using the Intel graphics now, but I don't think Tails needs the high power Radeon adaptor anyway.
I then tried to find a way to make this permanent.
After more experimentation I found that you could remount the boot media with a read-write flag and then change the appropriate .cfg files with:
- sudo mount -o remount,rw /lib/live/mount/medium
- sudo vi /lib/live/mount/medium/syslinux/liveamd64.cfg
- sudo vi /lib/live/mount/medium/EFI/BOOT/liveamd64.cfg
- sudo mount -o remount,ro /lib/live/mount/medium
To use use sudo, you need to set a password on boot with the 'More Options' dialog, and you have to append the 'radeon.modeset=0" manually the first time you boot to be able to do the above.
Tuesday, 17 May 2016
Subscribe to:
Posts (Atom)