Ubuntu Server 18.04 does not show Intel SW RAID(RAID 0 or RAID 1) device in Partition Manger
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
My Intel system is configured with RAID 0(2 disks) or RAID 1(2 disks) in BIOS.
And I use the image from http://cdimage.ubuntu.com/ubuntu/releases/bionic/release/
to perform installation.
During "Detect disks" stage, it asked if I want to "Active MDADM constainers (Intel/DDF RAID), I answered "yes". Then it asked my if I want to "Activate Serial ATA RAID device", I answered "yes" also.
However, in "Partition disks" stage, it does not show me any disk information.
With Ubuntu Server 16.04, the installation works without issue on this system.
18.04 raid
asked May 11 at 9:09
hongpj
62
add a comment |Â
up vote
1
down vote
favorite
My Intel system is configured with RAID 0(2 disks) or RAID 1(2 disks) in BIOS.
And I use the image from http://cdimage.ubuntu.com/ubuntu/releases/bionic/release/
to perform installation.
During "Detect disks" stage, it asked if I want to "Active MDADM constainers (Intel/DDF RAID), I answered "yes". Then it asked my if I want to "Activate Serial ATA RAID device", I answered "yes" also.
However, in "Partition disks" stage, it does not show me any disk information.
With Ubuntu Server 16.04, the installation works without issue on this system.
18.04 raid
asked May 11 at 9:09
hongpj
62
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My Intel system is configured with RAID 0(2 disks) or RAID 1(2 disks) in BIOS.
And I use the image from http://cdimage.ubuntu.com/ubuntu/releases/bionic/release/
to perform installation.
During "Detect disks" stage, it asked if I want to "Active MDADM constainers (Intel/DDF RAID), I answered "yes". Then it asked my if I want to "Activate Serial ATA RAID device", I answered "yes" also.
However, in "Partition disks" stage, it does not show me any disk information.
With Ubuntu Server 16.04, the installation works without issue on this system.
18.04 raid
asked May 11 at 9:09
hongpj
62
My Intel system is configured with RAID 0(2 disks) or RAID 1(2 disks) in BIOS.
And I use the image from http://cdimage.ubuntu.com/ubuntu/releases/bionic/release/
to perform installation.
During "Detect disks" stage, it asked if I want to "Active MDADM constainers (Intel/DDF RAID), I answered "yes". Then it asked my if I want to "Activate Serial ATA RAID device", I answered "yes" also.
However, in "Partition disks" stage, it does not show me any disk information.
With Ubuntu Server 16.04, the installation works without issue on this system.
18.04 raid
asked May 11 at 9:09
hongpj
62
asked May 11 at 9:09
hongpj
62
asked May 11 at 9:09
hongpj
62
asked May 11 at 9:09
hongpj
62
62
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
When asked:
Active MDADM containers (Intel/DDF RAID), choose "yes"
It will then ask:
Activate Serial ATA RAID device, at this point wait and switch to a shell by pressing "alt+f2"
Press Enter to activate the console
Then run the command "mdadm --stop /dev/md127"
Next activate the intel dmraid by running the command "dmraid -ay"
Press "alt+f1" to go back to the installer.
Now you can answer the
Activate Serial ATA RAID device with "No".
It should now pick up your Intel RAID.
answered May 29 at 18:22
Fats
111
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
add a comment |Â
up vote
0
down vote
You should not use dmraid for Intel Raid arrays, as it has moved to mdadm for a long time now. dmraid is limited in many ways for Intel Raid arrays. For example - limited disk size / raid array size.
Are you booting in UEFI? If not, you probably should. We regularly test Intel Raid array installation with d-i based server installer and mdadm and it does work with 18.04.1 LTS (which ships updated mdadm with many Intel Raid array fixes).
Did you setup Volume0 or similar in the pre-os/uefi screens? And if after that raid arrays were not detected, please extract /var/log/syslog from the installation environment and open a bug report on launchpad against mdadm or debian-installer package.
answered Aug 1 at 11:27
Dima
5,25482545
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
When asked:
Active MDADM containers (Intel/DDF RAID), choose "yes"
It will then ask:
Activate Serial ATA RAID device, at this point wait and switch to a shell by pressing "alt+f2"
Press Enter to activate the console
Then run the command "mdadm --stop /dev/md127"
Next activate the intel dmraid by running the command "dmraid -ay"
Press "alt+f1" to go back to the installer.
Now you can answer the
Activate Serial ATA RAID device with "No".
It should now pick up your Intel RAID.
answered May 29 at 18:22
Fats
111
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
add a comment |Â
up vote
1
down vote
When asked:
Active MDADM containers (Intel/DDF RAID), choose "yes"
It will then ask:
Activate Serial ATA RAID device, at this point wait and switch to a shell by pressing "alt+f2"
Press Enter to activate the console
Then run the command "mdadm --stop /dev/md127"
Next activate the intel dmraid by running the command "dmraid -ay"
Press "alt+f1" to go back to the installer.
Now you can answer the
Activate Serial ATA RAID device with "No".
It should now pick up your Intel RAID.
answered May 29 at 18:22
Fats
111
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
add a comment |Â
up vote
1
down vote
up vote
1
down vote
When asked:
Active MDADM containers (Intel/DDF RAID), choose "yes"
It will then ask:
Activate Serial ATA RAID device, at this point wait and switch to a shell by pressing "alt+f2"
Press Enter to activate the console
Then run the command "mdadm --stop /dev/md127"
Next activate the intel dmraid by running the command "dmraid -ay"
Press "alt+f1" to go back to the installer.
Now you can answer the
Activate Serial ATA RAID device with "No".
It should now pick up your Intel RAID.
answered May 29 at 18:22
Fats
111
When asked:
Active MDADM containers (Intel/DDF RAID), choose "yes"
It will then ask:
Activate Serial ATA RAID device, at this point wait and switch to a shell by pressing "alt+f2"
Press Enter to activate the console
Then run the command "mdadm --stop /dev/md127"
Next activate the intel dmraid by running the command "dmraid -ay"
Press "alt+f1" to go back to the installer.
Now you can answer the
Activate Serial ATA RAID device with "No".
It should now pick up your Intel RAID.
answered May 29 at 18:22
Fats
111
answered May 29 at 18:22
Fats
111
answered May 29 at 18:22
Fats
111
answered May 29 at 18:22
Fats
111
111
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
add a comment |Â
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
I literally ran into this issue installing 18.04 LTS to a dual node supermicro server. This was like the 2nd answer on Google. Thank you!
– Evan R.
Jun 23 at 2:03
add a comment |Â
up vote
0
down vote
You should not use dmraid for Intel Raid arrays, as it has moved to mdadm for a long time now. dmraid is limited in many ways for Intel Raid arrays. For example - limited disk size / raid array size.
Are you booting in UEFI? If not, you probably should. We regularly test Intel Raid array installation with d-i based server installer and mdadm and it does work with 18.04.1 LTS (which ships updated mdadm with many Intel Raid array fixes).
Did you setup Volume0 or similar in the pre-os/uefi screens? And if after that raid arrays were not detected, please extract /var/log/syslog from the installation environment and open a bug report on launchpad against mdadm or debian-installer package.
answered Aug 1 at 11:27
Dima
5,25482545
add a comment |Â
up vote
0
down vote
You should not use dmraid for Intel Raid arrays, as it has moved to mdadm for a long time now. dmraid is limited in many ways for Intel Raid arrays. For example - limited disk size / raid array size.
Are you booting in UEFI? If not, you probably should. We regularly test Intel Raid array installation with d-i based server installer and mdadm and it does work with 18.04.1 LTS (which ships updated mdadm with many Intel Raid array fixes).
Did you setup Volume0 or similar in the pre-os/uefi screens? And if after that raid arrays were not detected, please extract /var/log/syslog from the installation environment and open a bug report on launchpad against mdadm or debian-installer package.
answered Aug 1 at 11:27
Dima
5,25482545
add a comment |Â
up vote
0
down vote
up vote
0
down vote
You should not use dmraid for Intel Raid arrays, as it has moved to mdadm for a long time now. dmraid is limited in many ways for Intel Raid arrays. For example - limited disk size / raid array size.
Are you booting in UEFI? If not, you probably should. We regularly test Intel Raid array installation with d-i based server installer and mdadm and it does work with 18.04.1 LTS (which ships updated mdadm with many Intel Raid array fixes).
Did you setup Volume0 or similar in the pre-os/uefi screens? And if after that raid arrays were not detected, please extract /var/log/syslog from the installation environment and open a bug report on launchpad against mdadm or debian-installer package.
answered Aug 1 at 11:27
Dima
5,25482545
You should not use dmraid for Intel Raid arrays, as it has moved to mdadm for a long time now. dmraid is limited in many ways for Intel Raid arrays. For example - limited disk size / raid array size.
Are you booting in UEFI? If not, you probably should. We regularly test Intel Raid array installation with d-i based server installer and mdadm and it does work with 18.04.1 LTS (which ships updated mdadm with many Intel Raid array fixes).
Did you setup Volume0 or similar in the pre-os/uefi screens? And if after that raid arrays were not detected, please extract /var/log/syslog from the installation environment and open a bug report on launchpad against mdadm or debian-installer package.
answered Aug 1 at 11:27
Dima
5,25482545
answered Aug 1 at 11:27
Dima
5,25482545
answered Aug 1 at 11:27
Dima
5,25482545
answered Aug 1 at 11:27
Dima
5,25482545
5,25482545
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034836%2fubuntu-server-18-04-does-not-show-intel-sw-raidraid-0-or-raid-1-device-in-part%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password