Description of problem: I have a Dell Proliant 2650 with 32bit processor 4gig Ram, Perr 3/di with Raid 5. When trying to format the partitions I get an error while formating the largest partition in ext4. Same happens with a newer server, a Dell Proliant 2900 14gigs of Ram and only one 400gb hard drive on a SAS 5 raid controller. Same problem while trying to format the harddrive. Is there a trick while installing on this servers? It is weird since I tried Ubuntu 16 on the 32bit server and it installed fine except that once installed it write protects itself and cannot update... I have not tried Ubuntu on the 64bit server. To be honest I would prefeer Mageia on this than Ubuntu.. Please help. Regards
Thank you for the report, and sorry for the problems. The Dell Proliant 2650 is 32bit; What is the Dell Proliant 2900? Have you ever been able to install Mageia on either box? Can you say what partitions you are trying to create on the two drives - size & type; the same in both cases? Are you starting from zero, or working with some existing partitions? What error gets reported, and at what stage? Do the partitions get created as defined? Does the error happen when formatting the first partition (to format), or a subsequent one?
Status: NEW => NEEDINFOCC: (none) => lewyssmith
Hello, >The Dell Proliant 2650 is 32bit; What is the Dell Proliant 2900? Proliant 2900 is 64bit.. Proliant 2650 is 32bit. On the Proliant 2650 It has a Perc 3 /Di array with Raid 5 setup.. 273.4GB Total with 5 Fujitsu MAP3735NC 68.3gb HDs. Mageia 8 32bit classic install fail while formating. I used Simple partition setup Auto Allocate. It does format first 50gb partition but fails on the second.. Sometimes it fails on both. On the Prolian 2900 it has a SAS 5 Controller with only one 400gb Hard Drive (Seagate ST3400755SS) Mageia 8 64bit classic install fails while formating, same problem with Mageia 8 Live 64bit. I also trie the server partition Auto Allocation but the / is setup as 7gb and it gives me an error saying it should be at least 10gb. I will do it manually and see what happens. And yes I did started from cero. Regards
Confused about whether the "Prolian 2900 it has a SAS 5 Controller with only one 400gb Hard Drive" & "only one 400gb hard drive on a SAS 5 raid controller" is a Raid5 device (on one disc?), or a straight uncomplicated 400Gb disc. It is easy to suspect Raid as the root of the problem. Can you also please say whether the servers are using BIOS/MBR or EFI/GPT? (being unsure whether that is relevant with Raid). I need to do a bit of research before replying further.
CC: (none) => fri, ouaurelien
Hello Lewis, It is Bios/MBR on both. They don´t seem to support EFI at least it doesn´t say on the BIOS or anywhere else. Proliant 2650 It has a Perc 3 /Di array with Raid 5 setup.. 273.4GB Total with 5 Fujitsu MAP3735NC 68.3gb HDs. And yes, On the Prolian 2900 it has a SAS 5 Controller to be able to create a Raid 5, but for now in only one one 400gb Hard Drive (Seagate ST3400755SS); I think this is called Raid 0. I was able to install Mageia on the Prolian 2900, I also think I found a bug on the automatic partition Auto Allocation as Server. It assigns only 7gb on / and later complains of being 10gb as minimal.. This is what I did. I downloaded Dell Server Assist CD. This CD has a way to setup everything and install RedHat Linux until RHL4 and Suse XX.. it does not work with Mageia.. I only used this to erase the whole raid partition and install the Dell Utility Partition with server diagnostics and stuff. I was only able to install with the Automatic Allocation as Server but modified the / spaces as 30gb instead of 7gb. It ended up as this: sda1 (Dell Utility Partition) vfat 31mb sda5 / ext4 30bg sda6 SWAP 3.8gb sda7 /usr ext4 19gb sda8 /var ext4 157gb sda9 /home ext4 157gb sda10 /tmp ext4 I rebooteed many times and upgraded packages without getting any errors or the HDs becoming read only.. I will try on the Proliant 2650 32bit later today. Probably this Dell Server Assistan erases something on the HDs that Mageia DrakHardrive does not. To test this posibility I would like to reformat the 2900 but as normal partition instead of as server. / 50 gb swap 3.8. /home 39X gb This is where it failed before while formatting the large partition.
Hello Again, I rebooted and reformated the Prolian 2900 and repartitioned using Normal Mode / 50gb EXT4 swap 3.8gb /home 318gb ext 4 I did not had any problems anymore. It seems that the Dell Server Assistant does something when Erasing everything on the hard drive. Right now I will make some test on the 32bit Proliant 2560. But once the Dell Server Assistant erases the hard drives it also erases the Raid 5 Container so I had to create a new one and I need to wait until it ends ¨Scrubbing¨ the harddrives to be able to be redundant. I will report this once I have the results. Regards
Thank you for your willingness to persist, and your success on the single-disc Prolian 2900; and the useful detailed partition information you gave - which shows that at least the sda1 (Dell Utility Partition) vfat 31mb partition needs to be preserved, so the whole disc is not an issue. I was going to suggest that you pre-partition the discs from one of our Live ISOs (you do not say which ISO you are using) in a Live session using Gparted; then do the installation 'using existing partitions' which you assign as required. > I think I found a bug on the automatic partition Auto Allocation as Server > I was only able to install with the Automatic Allocation as Server I do not think that the installer disc partitioning has any knowledge of 'server'. If you really do have a bug, it is at least this... > I also trie the server partition Auto Allocation but the / is setup as 7gb > and it gives me an error saying it should be at least 10gb. plus the formatting failures.
Auto Allocation should not allocate below the recommended disk size. Per comment 2: > I also trie the server partition Auto Allocation but the / is setup as 7gb and > it gives me an error saying it should be at least 10gb. I will do it manually > and see what happens. Assigning to Mageia Tools Maintainers.
Target Milestone: --- => Mageia 9Source RPM: (none) => drakx-installer-stage2-18.46-1.mga9.src.rpmComponent: RPM Packages => InstallerAssignee: bugsquad => mageiatoolsVersion: 8 => CauldronWhiteboard: (none) => MGA8TOOStatus: NEEDINFO => NEW
Summary: Cannot install mageia to Dell servers. => DrakX should not create root partition below the recommended size with "Auto Allocate" and complains about it
Hello I have new information on this. Today I started working on two Dell PowerEdge 2650. When installing Mageia 8, sometimes format fails and when it passes formating the HDDs get write protected. I also tested this with MGA 7.1 with same results. But guess what?... Mageia 6 works great!!!! The only problem is that there are no MGA6 repositories left for me to upgrade and upgrading to MGA 7 does not work, probably since I need to upgrade to more recent MGA6 packages, so the next step is to upgrade using the DVD. This worked with both of my Dell PowerEdge 2650.. I also found the same problem with a Dell PowerEdge 750. I will let you know how things came out. BTW, if this is a bug, I guess this happens with all other distros too, I tested openSUSE Tumbleweed NET i586, this one does install but later HDDs got write protected, Debian i386 Net Install fails while installing at around 60% The only one that worked is Ubuntu 18 tls i386. This means older versions of Linux do work. Regards
(In reply to Ezequiel Partida from comment #8) > The only problem is that there are no MGA6 repositories left for me to > upgrade and upgrading to MGA 7 does not work, probably since I need to > upgrade to more recent MGA6 packages, so the next step is to upgrade using > the DVD. urpmi.addmedia --distrib http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia-archive/distrib/6/x86_64/
CC: (none) => davidwhodgins
(In reply to Ezequiel Partida from comment #8) > this one does install but later HDDs > got write protected Are you sure that they are „write protected“? Because if you format a drive (which requires root rights) it is owned by root and can only be written by root unless you: - set user flag on this partition/drive - change ownership of this drive/partition with chown - use polkit rules that allow users to mount drives/partitions: https://wiki.mageia.org/en/Useful_polkit_policies#Mount_devices_by_users_without_password
(In reply to sturmvogel from comment #10) > (In reply to Ezequiel Partida from comment #8) > > this one does install but later HDDs > > got write protected > > Are you sure that they are „write protected“? Because if you format a drive > (which requires root rights) it is owned by root and can only be written by > root unless you: > - set user flag on this partition/drive > - change ownership of this drive/partition with chown > - use polkit rules that allow users to mount drives/partitions: > https://wiki.mageia.org/en/ > Useful_polkit_policies#Mount_devices_by_users_without_password You are my hero sturmvogel... I have upgraded to lates packages ;-) But guess what?.. I think there is something wrong with the kernel and the server failed again, but if I go back to the original kernel it works. With kernel 4.9.35-server-1.mga6 all works fine. But with kernel 4.18.20-server-1.mga6 I start getting problems after hardware detect. After hardware detect I got: [360.098903] aacraid: host adapter abort request. [360.098903] aacraid: Outstanding commands on (2,0,0,0); [350.440260]: Host adapter reset request, SCI hang? Please see shared pictures below. I will upgrade to MGa7 in a moment to test with MGA7 kernels. https://www.dropbox.com/s/lk358plqgm88n8f/screen1.jpeg?dl=0 https://www.dropbox.com/s/stq8l7c9b85jtar/Screen2.jpeg?dl=0 https://www.dropbox.com/s/71w0r7qmg22ot8w/screen3.jpg?dl=0 Regards
(In reply to sturmvogel from comment #10) > Are you sure that they are „write protected“? Because if you format a drive > (which requires root rights) it is owned by root and can only be written by > root unless you: > - set user flag on this partition/drive > - change ownership of this drive/partition with chown > - use polkit rules that allow users to mount drives/partitions: > https://wiki.mageia.org/en/ > Useful_polkit_policies#Mount_devices_by_users_without_password I remeber seeing a message saying that filesystem is readonly. If use mga8 (and I thing MGA7 too) I got an error while formatting and never got thru that... When I rebooted I got a message eighter that no HDD´s where available or that the Filesystem was readonly. Then I tried MGA6 and I was able to install. I already download an ISO boot CD from Dell with latest Bios and hardware firmware and got a newer version of the bios of what the support.dell.com has, also another firmware was upgraded.
I upgraded all the way to MGA8 i586 and none of the kernels work. They hang when aacraid is executed, only kernel 4.9.35-server-1.mga6 works. I booted with MGA8 netinstaller as well as DVD and it does detect the raid controller but not the drives, MGA6 DVD does. I guess this is a problem on the kernel since OpenSuse and Debia x86 have the same problem. I am trying to check hardware firmware with gnome-firmware I got from and opensuse rpm but it requires glibc_34 and the 32bit version is not available on flatpak. I will test MGA9 but draktools are not working well on real x86 hardware (CoreDump Segment Fault), they work fine on virtualbox btw.