Bug 28188 - RAID 1 Fails To Auto-mount Upon Start-up
Summary: RAID 1 Fails To Auto-mount Upon Start-up
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard: MGA8TOO ?
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2021-01-21 19:31 CET by John
Modified: 2021-09-07 14:09 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Report Bug Tarball (176.20 KB, application/x-xz)
2021-01-25 16:49 CET, John
Details

Description John 2021-01-21 19:31:07 CET
Description of problem:
	I have found that when I configure the RAID 1 set-up for my home partition in the installer, 
when I boot my computer it fails to auto-mount /home. If the fstab is change to only contain the 
/home reference, but not require it at start-up, I am then able to manually run mdadm and then 
mount /home without issue.

Version-Release number of selected component (if applicable):
	This happened on 5, 6, and 7.

How reproducible:
	Every time.

Steps to Reproduce:
During installation I do the normal:
	0) Set-up my RAID 1 home partition
	1) At the summary, I set-up my inter-net connection.
		a) I do set my hostname to be something other than localhost.
	2) Run all updates
	3) Restart per the installer's instructions
	4) Observe that the home partition is not mounted.


	I investigated it further and found that if I set the hostname via mdadm the issue disappear.
Which leads me to think its the installer does not handle that the name of the host changing.
Comment 1 Lewis Smith 2021-01-24 16:30:40 CET
Thank you for reporting this. You have kept it for a long time: 5, 6, and 7 !
You have probably identified the essential:
> At the summary, I set-up my inter-net connection.
> I do set my hostname to be something other than localhost.
> if I [later] set the hostname via mdadm the issue disappear.
> Which leads me to think its the installer does not handle that the name
> of the host changing.
Assigning to the mageiatools group for the installer. CC'in Martin who knows it well.

Whiteboard: (none) => MGA8TOO ?
CC: (none) => mageia
Assignee: bugsquad => mageiatools

Comment 2 Martin Whitaker 2021-01-24 20:27:45 CET
Please add the /root/drakx/report.bug.xz file from your installed system as an attachment to this bug report.

Keywords: (none) => NEEDINFO

Comment 3 John 2021-01-25 16:49:43 CET
Created attachment 12258 [details]
Report Bug Tarball
Comment 4 Martin Whitaker 2021-01-30 17:11:53 CET
When I use the Mageia installer to create a RAID array from blank disks, it sets the hostname in the RAID metadata to "localhost". In my tests, that allows me to change the system hostname without any problem. Did you start with an existing RAID array with a different hostname?
Comment 5 John 2021-02-02 17:58:50 CET
Nope, these were brand new drives that I had just bought. Completely formatted while in the installer.
Comment 6 Marja Van Waes 2021-09-07 14:09:26 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.