Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Recognise /home on mdadm at MX Linux 18.3 install time

Post Reply
User avatar
Red_Stag
Forum Novice
Forum  Novice
Posts: 19
Joined: Thu Feb 21, 2019 4:27 am

Recognise /home on mdadm at MX Linux 18.3 install time

#1

Post by Red_Stag » Sat Jun 08, 2019 5:33 pm

Dear All,

Would someone please advise if there is a way to get the MX LInux 18.3 install process to recognise a /home located on mdadm RAID. When I install the mdadm RAID is not listed as a device along with the other devices / partitions. This seems reasonable to me because at that point in time not sure how an install process would be able to see / recognise an mdadm RAID. I have looked in "Options" under "persistence" but not sure I am going down a path which is helping me.

How would a person navigate an install where the existing /home is on a mdadm RAID device and the desire is to retain the /home because of the data in there?

Code: Select all

System:    Host: Picasso Kernel: 4.9.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Compaq 8000 Elite CMT PC v: N/A 
           serial: <filter> 
           Mobo: Hewlett-Packard model: 3647h serial: <filter> BIOS: Hewlett-Packard 
           v: 786G7 v01.14 date: 10/14/2015 
CPU:       Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP arch: Penryn 
           rev: A L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11969 
           Speed: 1998 MHz min/max: 1998/3000 MHz Core speeds (MHz): 1: 1998 2: 1998 
Graphics:  Device-1: Intel 4 Series Integrated Graphics vendor: Hewlett-Packard driver: i915 
           v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel Q45/Q43 v: 2.1 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel 82801JD/DO HD Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.9.0-9-amd64 
Network:   Device-1: Intel 82567LM-3 Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: 3.2.6-k port: 3100 bus ID: 00:19.0 
           IF: eth0 state: down mac: <filter> 
           Device-2: Belkin F5D7000 v7000 Wireless G Desktop Card [Realtek RTL8185] 
           driver: rtl818x_pci v: kernel port: 2100 bus ID: 10:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 4.36 TiB used: 145.43 GiB (3.3%) 
           ID-1: /dev/sda type: USB model: USB 3.0 size: 465.76 GiB 
           ID-2: /dev/sdb type: USB vendor: Maxtor model: OneTouch III size: 149.05 GiB 
           ID-3: /dev/sdc vendor: Silicon Power model: SPCC Solid State Disk size: 119.24 GiB 
           ID-4: /dev/sdd vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
           ID-5: /dev/sde vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
RAID:      Device-1: md0 type: mdraid status: active Components: online: sde~c1 sdd~c0 
           Info: raid: mirror blocks: 1953383488 report: 2/2 UU chunk size: N/A 
Partition: ID-1: / size: 14.93 GiB used: 7.44 GiB (49.8%) fs: ext4 dev: /dev/sdc1 
           ID-2: /home size: 1.79 TiB used: 26.57 GiB (1.4%) fs: ext4 dev: /dev/md0 
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb https://mirrors.evowise.com/mxlinux-packages/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.au.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.au.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirrors.evowise.com/mxlinux-packages/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 221 Uptime: 54m Memory: 3.76 GiB used: 989.1 MiB (25.7%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33 
Many thanks
Red_Stag
Red_Stag
***********
HP Elite 8000, Intel Core 2 Duo, 4GB Ram, SP SSD 120GB,
2X WD 1TB mdadm RAID 1, MX-18.2_x64 & Kernel 4.19.0-1
***********

User avatar
fehlix
Developer
Posts: 4890
Joined: Wed Apr 11, 2018 5:09 pm

Re: Recognise /home on mdadm at MX Linux 18.3 install time

#2

Post by fehlix » Sat Jun 08, 2019 7:48 pm

Red_Stag wrote:
Sat Jun 08, 2019 5:33 pm
Would someone please advise if there is a way to get the MX LInux 18.3 install process to recognise a /home located on mdadm RAID.
Have a look how @m_pav wrote about it here: Intel Rapid Storage mount on MX Linux
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Red_Stag
Forum Novice
Forum  Novice
Posts: 19
Joined: Thu Feb 21, 2019 4:27 am

Re: Recognise /home on mdadm at MX Linux 18.3 install time

#3

Post by Red_Stag » Thu Aug 22, 2019 5:47 pm

Dear All, I have tried for several weeks now and simply cannot get this to work. @m_pav's instructions are somewhat clear enough but the install process simply does not allow an mdadm Raid to be detected or if it does then despite trying every permutation and combination that I can think of I was still unable to find one that worked.

[Aside: I also incurred a loss of connectivity between the PC and the keyboard during the remastering process. I am currently using a wifi keyboard and would have switched to a cable keyboard to overcome this problem, but can you believe the cupboard only has wifi keyboards, aaarrgghh. The other thing I have found is that the remastering process using a USB 2.0 device is incredibly ssslllloooowwww. ]

The reason why I was seeking the MX Linux installable / bootable device was I saw this as a flexible why of rebuilding the operating system in the event of a drive/partition failure. Think of it as a backup that has the characteristics of a "operating system rebuild" nature rather than a "clone" nature.

Workaround employed at this time: I am reverting to a distribution version snapshot because it seems to be my only means of creating a bootable / installation ready MX Linux device which will see the mdadm RAID. After weeks and weeks of trying I am giving up on getting the remastering process to work and the installation process to see an mdadm device.

This also means that I as yet have not resolved the issue of "backups" for Operating system partition. I tried CloneZilla but that process is hampered by irrational naming of devices by my PC's BIOS. I am now trying FsArchiver. It seems to have some advantages but I cannot work out how to drop down to a cli from XFCE GUI environment.

Many thanks
Red_Stag
***********
HP Elite 8000, Intel Core 2 Duo, 4GB Ram, SP SSD 120GB,
2X WD 1TB mdadm RAID 1, MX-18.2_x64 & Kernel 4.19.0-1
***********

User avatar
kwe
Forum Novice
Forum  Novice
Posts: 3
Joined: Wed Aug 21, 2019 4:40 pm

Re: Recognise /home on mdadm at MX Linux 18.3 install time

#4

Post by kwe » Fri Aug 23, 2019 10:42 am

fehlix wrote:
Sat Jun 08, 2019 7:48 pm

Have a look how @m_pav wrote about it here: Intel Rapid Storage mount on MX Linux
:puppy:
Nice post but you have to realize you cannot remaster a LiveUSB made from an ISO, because no one will tell you that. If you are starting from scratch, you can make a LiveUSB on a Windows machine with Rufus, then you need to boot that LiveUSB and make ANOTHER LiveUSB using the tools in MX Linux. You select the option to make the new LiveUSB writeable, then you boot THAT LiveUSB and use the "remaster and persistence" tool to make root and home persistent. Don't remaster. Then you reboot again and create new passwords and logons and from then on, your USB will update when you reboot or shutdown. I don't know yet whether all those fumbulations will result in mdadm (which you have to install on your LiveUSB once root is persistent) being able to setup RAID and THEN FINALLY and maybe SUCCESSFULLY setup RAID arrays and install MX Linux on a root array.

Somebody needs to sell a LiveUSB with all this stuff already done.

User avatar
fehlix
Developer
Posts: 4890
Joined: Wed Apr 11, 2018 5:09 pm

Re: Recognise /home on mdadm at MX Linux 18.3 install time

#5

Post by fehlix » Fri Aug 23, 2019 11:30 am

kwe wrote:
Fri Aug 23, 2019 10:42 am
You select the option to make the new LiveUSB writeable, then you boot THAT LiveUSB and use the "remaster and persistence" tool to make root and home persistent.
Just select persistence boot option when you boot the LiveUSB, which creates persistence during boot.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
kwe
Forum Novice
Forum  Novice
Posts: 3
Joined: Wed Aug 21, 2019 4:40 pm

Re: Recognise /home on mdadm at MX Linux 18.3 install time

#6

Post by kwe » Sun Aug 25, 2019 12:45 pm

That's easier. Thanks.

User avatar
Red_Stag
Forum Novice
Forum  Novice
Posts: 19
Joined: Thu Feb 21, 2019 4:27 am

Re: Recognise /home on mdadm at MX Linux 18.3 install time

#7

Post by Red_Stag » Thu Sep 05, 2019 5:07 am

Dear All,

Yes I agree with kwe, that is much easier. Genuine thanks to fehlix, he is a Wizard. In addition to talking fehlix's advice I have also opted for the autosave option to overcome the loss of connectivity to the keyboard. For the moment this solution works for all my needs except that it does cater for the scenario where one is seeking to have a mdadm RAID detected at the moment of installing MX Linux.

Thank you again to all who contributed, your generous contribution of time is acknowledged. I bow to you.

Kind regards
Red_Stag
***********
HP Elite 8000, Intel Core 2 Duo, 4GB Ram, SP SSD 120GB,
2X WD 1TB mdadm RAID 1, MX-18.2_x64 & Kernel 4.19.0-1
***********

Post Reply

Return to “Software / Configuration”