LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-16-2016, 01:04 PM   #1
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Rep: Reputation: 72
Question repair lilo on software RAID1 ?


Hello folks!
I have an interesting problem - yesterday i feel, my life is too easy, and try to upgrade my slackware desktop system.
on that moment it be a slaskware64 14.1, and software raid1 disks set - /dev/md1
as /
i update 14.1 to latest - all going fine, kernel too upgrades, and i check lilo, restart, and get working system!
that was surprise, especially as i use /boot/vmlinuz, huge kernel, without mkinitrd!
but all is fine, and md1 / md2, and md3 is there. great.

then i went to upgrade to 14.2

i make my editing of slackpkg to 14.2, ipdate, upgrade-all,
then slackpkg upgrade glibc-solibs, install new - all looks ok, lilo run after upgrade-all also looks good, as so i do restart.

for my surprise, kernel start loading, there is some white dots on start, and then all stop. nothing else happens - not start flowing terminal info lines from kernel and so on. i restart machine, but the same happens.

today i write slackware64 live 1.1.4 disc, and now i be there - dont know, how i can try repair lilo. do at startup kernel parameter for livecd as root=/dev/sda1 or /dev/md1 does to situation, kernel cant mount root.

if i start in livecd, it assembles raid from md124 to 126.
if i try to mount /dev/md124 /mnt/hd , it mounts ok, my root partition is there.
but if i try do
chroot /mnt/hd /bin/lilo -v -v
i get warning /proc/partitions does not exist
fatal: unable to open /dev/md124


what can i do? there is some instructions for such cases?

that was not very problem for me in this case - i think, i always have made my home partition backup, or just erase all system, leave my personal folders, and try install slack14.2 from scratch without reformatting discs, but that situation was interesting by its own. -there is any
way to someone can restore system via small efforts?

and interesting also - why system become that after i upgrade to 14.2...
i see no evidence for that...
 
Old 11-16-2016, 01:11 PM   #2
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Rep: Reputation: 36
Try this before chroot:
mount -o bind /proc /mnt/hd/proc
mount -o bind /sys /mnt/hd/sys
mount -o bind /dev /mnt/hd/dev
 
Old 11-16-2016, 01:20 PM   #3
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
i do. now:
fatal: illegal "root=" specification: /dev/md1

remember, now, on slackware live it become /dev/md124. dont know - why....
 
Old 11-16-2016, 02:11 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,881

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
I would recommend using a Slackware installation image to boot from rather than the Slackware Live distro. I don't think there'd be changes that would affect your partitions, but it's better to be safe than sorry.

Once you boot the Slackware install and you get to the prompt, mount your raid to /mnt/hd, then bind mount the proc, sys, and dev filesystems as slacker1337 showed. Then chroot your install. From there, check and see how everything is being read (partitions and whatnot) and then make sure your /etc/lilo.conf entries match. Once that is done, you should be able to run lilo to reinstall it.

Also, as an FYI, to use verbose mode, you need to use lilo -v [1-5]. 1 is the lowest verbosity and 5 is the highest -- 5 will dump more information than you can fathom... on my system with 9 kernels in my lilo.conf, it would dump out 156,193 lines. I ended up being curious and the various verbosity levels were:
  • no verbosity = 10 lines
  • level 1 = 59 lines
  • level 2 = 124 lines
  • level 3 = 205 lines
  • level 4 = 2932 lines
  • level 5 = 156193 lines

Sorry for the random, unneeded info that satisfied my curiosity
 
Old 11-16-2016, 02:28 PM   #5
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
thanks for info about lilo loglevels, but i boot from slackware64 14.1 install dvd ( i do not have 14.2 yet), do all that, and get the same result.
also i found, my primary md ( sda / b1) again become as md124, but other partitions come right / md2, md3... why md1 not came as md1 then, but as md124?

i feel, mdraid in linux is build to act in very idiotic behaviour...
 
Old 11-16-2016, 04:00 PM   #6
TracyTiger
Member
 
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 489

Rep: Reputation: 229Reputation: 229Reputation: 229
This LQ thread from a few years ago may be helpful regarding the naming of RAID block devices.
 
1 members found this post helpful.
Old 11-17-2016, 10:59 AM   #7
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
Quote:
Originally Posted by TracyTiger View Post
This LQ thread from a few years ago may be helpful regarding the naming of RAID block devices.
thank you very much!

try to start read https://bugzilla.redhat.com/show_bug.cgi?id=606481

previous link do nothing for me - i try receipt with mdadm -As and so on, and nothing - there is again md124 125 and so on.

i think, i must do somehow to remount md125 to md1 ( my root partition ), then i can try chroot /mnt/hd /usr/sbin/lilo -v 3

unless i get md1, lilo do fatal error on my directive in lilo.conf root= /dev/md1

as so i stopped there.

PS it is very, very bad, as from slackware install disc there is no mc. that was really terrible. midnight commander is super useful when trying to repair something, or so on.

and AlienBob livecd also do not have option for runlevel 3 - i must wait until x session manager start, and that is a long time. cd drive do many seeks, and load time is terrible. why OS not read entire CD sector by sector, to RAm, and then deal with all that? that much be far faster, and there is rarely machines with less than 4 Gb RAm novadays...
 
Old 11-17-2016, 11:34 AM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,881

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
You can still install packages once you boot up the installer. Just run installpkg /location/to/mc*.txz and it will install it to the tmpfs. However, you might need to install additional dependencies, depending on what it requires.
 
Old 11-17-2016, 11:43 AM   #9
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
Quote:
Originally Posted by bassmadrigal View Post
You can still install packages once you boot up the installer. Just run installpkg /location/to/mc*.txz and it will install it to the tmpfs. However, you might need to install additional dependencies, depending on what it requires.

do not understand anything.
sorry, english not my pri language, and i was no good at it, sadly...yet.

cant get a point - why i .....aaa! get!
you suppose, i may install mc in tmpfs of working installation environment?
but there is a lot new problems to try doing this, i suppose. i think, is much better for all of us, to next slacjwares dvd include mc in default environment after loading kernel for start installation / setup of slackware...?

but anyway, my primary interest now - is how to repair my lilo?

very strange as linux / software raid systems, who used so many peoples, so many years, do not have a step-by-step guide for that, not very rare, situation....

good, i have linux for spirit and sex, and macos for everyday work....
 
Old 11-17-2016, 12:33 PM   #10
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,881

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
Well, I'm not sure how strong of a reason there is to add mc to the installer. In my 10+ years using/installing Slackware, I've never felt a need for a file manager during the install. Pat probably doesn't want to bloat the installer, so he has to carefully weigh the benefits to the downsides of adding extra software to the installer.

But, the installer is complete enough that you can install any desired packages into the tmpfs it creates (you may need to install additional dependencies if the programs require it). This flexibility allows you to tailor the environment to your needs, no matter what Pat includes in the installer.

Either way, instead of directly referencing your device based on names that can change, maybe you'd be better off using UUIDs. I think that's what TracyTiger was referencing in his link. UUIDs won't change without you reformating your partition. Based on his post within that link, you can set up your /etc/mdadm.conf with UUIDs for the individual partitions on each drive in your raid, and then you can set an overall UUID for your raid device that covers those drives.

I've never used raid, so figuring out that information will be up to you or others who may chime in to help.
 
Old 11-17-2016, 01:43 PM   #11
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
during install - yes, i too not much use of mc. but - slackware installation disc has usage in case of problems with system loading too, like with lilo configs, software raid problems and so on.
and in this situation mc may be very useful, and in any way - mc weight only few megabytes, as so it not takes much space in any way.

UUID is good thing, but not complete. about 4 years ago, when i try to make lilo work via UUID ( to use mobile usb HDD to boot on various machines), i found out, that UUID not work on lilo side. sadly, but in slackware 13.37 times, that's it. maybe now it was different, but i have doubt in that. linux world in many ways is conservative, and strange. -there may be elementar error, who bother many, but it can stay there for years, and no one take count on it...
 
Old 11-17-2016, 02:20 PM   #12
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,881

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
UUID and lilo definitely works in at least 14.1 and up, because I've been using it on my computer for quite a while (it might've even been back in the 14.0 days). I actaully wrote up a slackwiki page on it.

http://docs.slackware.com/howtos:sla...sistent_naming

As to mc in the installer, yes, it is small, but that's just your use case. What about someone who needs some other utility included, and then someone else, and suddenly you have a several hundred MBs added? This is why you're able to install packages into the tmpfs as needed. Either way, I'm not one you'd need to convince. You'd have to make your argument to Pat and ultimately, as with all things Slackware, he will decide if it is worth it to add. But I'd imagine, since it likely wouldn't be needed for install, or even to rescue a system (since other utilities can do everything mc can do, although, maybe not as easily), Pat would probably pass on it.
 
1 members found this post helpful.
Old 11-21-2016, 10:59 AM   #13
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
ok, thanks for info, i try check it in near future.
that must be good thing -UUID throught lilo and fstab!

But i have new great problems, and do not understand, what i can do at all!
Please, consider, after that battle and investigation i suppose to write article for clckware wiki ( docs) as so, you there help not only me, but many, who encounter similar problem
and so - i read, and read, and read that redhat page about what a animal is mdadm, and today i try to do some things:

i boot from last slackware live ( 1.1.4 xfce one) cd.
then i log in as root in CLI, and do:
dmesg | grep md

on a output i see what md numbers i now have, and what is their size for each - from that size i get understand, what md device is what - what is swap, what - root, what home, and what - "secondary" partition.

then i mount "root" one:

mount /dev/md125 /mnt/hd

then i start great "mc", and start do things - see fstab in my root partition, to remember, what md number must be for root, for swap, and home, and Second.

then i do
mdadm -Db /dev/md124 >>mnt/hd/etc/mdadm.conf
mdadm -Db /dev/md125 >>mnt/hd/etc/mdadm.conf
mdadm -Db /dev/md126 >>mnt/hd/etc/mdadm.conf
mdadm -Db /dev/md127 >>mnt/hd/etc/mdadm.conf

then i edit /mnt/hd/etc/mdadm.conf to make it looks right -md1, md2 instead of md125, md127 and so on:


#ARRAY /dev/md1 UUID=7cc47bea:832f8260:208cdb8d:9e23b04b
#ARRAY /dev/md2 UUID=cce81d3a:78965aa5:208cdb8d:9e23b04b
#ARRAY /dev/md3 UUID=f0bc71fc:8467ef54:208cdb8d:9e23b04b
#ARRAY /dev/md4 UUID=3f4daae2:cbf37a2a:208cdb8d:9e23b04b

#ARRAY /dev/md125 metadata=0.90 UUID=7cc47bea:832f8260:208cdb8d:9e23b04b #100 gb partition: \ md1
#ARRAY /dev/md124 metadata=0.90 UUID=f0bc71fc:8467ef54:208cdb8d:9e23b04b # 375 gb partition - \home - md3
#ARRAY /dev/md126 metadata=0.90 UUID=3f4daae2:cbf37a2a:208cdb8d:9e23b04b # 514 Gb partition - second-md4
#ARRAY /dev/md127 metadata=0.90 UUID=cce81d3a:78965aa5:208cdb8d:9e23b04b # 2 Gb partition - swap - md2

##HOMEHOST drago
#drago.domain.com
#darkstar.example.net


###ARRAY /dev/md1 metadata=0.90 UUID=7cc47bea:832f8260:208cdb8d:9e23b04b
###ARRAY /dev/md2 metadata=0.90 UUID=cce81d3a:78965aa5:208cdb8d:9e23b04b
###ARRAY /dev/md3 metadata=0.90 UUID=f0bc71fc:8467ef54:208cdb8d:9e23b04b
###ARRAY /dev/md4 metadata=0.90 UUID=3f4daae2:cbf37a2a:208cdb8d:9e23b04b

## mdadm -Es >>
ARRAY /dev/md1 UUID=7cc47bea:832f8260:208cdb8d:9e23b04b
ARRAY /dev/md2 UUID=cce81d3a:78965aa5:208cdb8d:9e23b04b
ARRAY /dev/md3 UUID=f0bc71fc:8467ef54:208cdb8d:9e23b04b
ARRAY /dev/md4 UUID=3f4daae2:cbf37a2a:208cdb8d:9e23b04b


then i copy that mdadm file from my rot ( /mnt/hd/etc ) to current ( /etc), and umount /dev/md125

then i do mdadm --stop /dev/md124
mdadm --stop /dev/md125
mdadm --stop /dev/md126
mdadm --stop /dev/md127

so far look good.

then i do mdadm -As.

it shows make up /md1, md2, md3, md4 -great, great!!!

now i again mount root fs:
mount /dev/md1 /mnt/hd

and do
chroot /mnt/hd /sbin/lilo -v 3


lilo worked out without serious errors.
then i press ctrl-alt-del, take off bootable cd from drive, and see, what happens.
lilo appear, then kernel start loading, go farther, running lines appear -excellent!

login prompt appears, and i log in as root.

good, i have back in my desktop system!

but then i do df -h, mount - and see, something is wrong.

there is no md3, nor md4. but at the same time, there is md1 and md2 ( root, and swap).
very strange. i try reboot, i check mdadm.conf, - cant see, why md1 and md2 assembles ok, but md3 and md4 again becomes as md124 and md125. ....? :-O

anyone have any ideas, or advice?


there is some system information from where i stand now:

df -h :

Filesystem Size Used Avail Use% Mounted on
/dev/root 99G 85G 9.3G 91% /
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.8G 1008K 3.8G 1% /run
tmpfs 3.8G 0 3.8G 0% /dev/shm
cgroup_root 3.8G 0 3.8G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs

mount :

/dev/md1 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)

dmesg | grep md :

[ 0.215951] amd_nb: Cannot enumerate AMD northbridges
[ 0.316910] ata7: PATA max UDMA/100 cmd 0x2018 ctl 0x2024 bmdma 0x2000 irq 17
[ 0.318177] ata9: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
[ 3.335294] ata10: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
[ 3.494385] md: linear personality registered for level -1
[ 3.494518] md: raid0 personality registered for level 0
[ 3.494649] md: raid1 personality registered for level 1
[ 3.494781] md: raid10 personality registered for level 10
[ 3.494956] md: raid6 personality registered for level 6
[ 3.495092] md: raid5 personality registered for level 5
[ 3.495223] md: raid4 personality registered for level 4
[ 3.495355] md: multipath personality registered for level -4
[ 3.825256] md: Waiting for all devices to be available before autodetect
[ 3.825390] md: If you don't use raid, use raid=noautodetect
[ 3.825718] md: Autodetecting RAID arrays.
[ 3.933280] md: Scanned 8 and added 8 devices.
[ 3.933422] md: autorun ...
[ 3.933550] md: considering sdb4 ...
[ 3.933683] md: adding sdb4 ...
[ 3.933812] md: sdb3 has different UUID to sdb4
[ 3.933943] md: sdb2 has different UUID to sdb4
[ 3.934078] md: sdb1 has different UUID to sdb4
[ 3.934211] md: adding sda4 ...
[ 3.934340] md: sda3 has different UUID to sdb4
[ 3.934471] md: sda2 has different UUID to sdb4
[ 3.934602] md: sda1 has different UUID to sdb4
[ 3.934910] md: created md125
[ 3.935045] md: bind<sda4>
[ 3.935187] md: bind<sdb4>
[ 3.935327] md: running: <sdb4><sda4>
[ 3.935667] md/raid1:md125: active with 2 out of 2 mirrors
[ 3.935830] md125: detected capacity change from 0 to 514872442880
[ 3.935971] md: considering sdb3 ...
[ 3.936107] md: adding sdb3 ...
[ 3.936237] md: sdb2 has different UUID to sdb3
[ 3.936368] md: sdb1 has different UUID to sdb3
[ 3.936501] md: adding sda3 ...
[ 3.936630] md: sda2 has different UUID to sdb3
[ 3.936761] md: sda1 has different UUID to sdb3
[ 3.937055] md: created md124
[ 3.937183] md: bind<sda3>
[ 3.937323] md: bind<sdb3>
[ 3.937464] md: running: <sdb3><sda3>
[ 3.937787] md/raid1:md124: active with 2 out of 2 mirrors
[ 3.937941] md124: detected capacity change from 0 to 375809572864
[ 3.938087] md: considering sdb2 ...
[ 3.938219] md: adding sdb2 ...
[ 3.938349] md: sdb1 has different UUID to sdb2
[ 3.938481] md: adding sda2 ...
[ 3.938610] md: sda1 has different UUID to sdb2
[ 3.938902] md: created md2
[ 3.939035] md: bind<sda2>
[ 3.939176] md: bind<sdb2>
[ 3.939317] md: running: <sdb2><sda2>
[ 3.939646] md/raid1:md2: active with 2 out of 2 mirrors
[ 3.939799] md2: detected capacity change from 0 to 2147418112
[ 3.939938] md: considering sdb1 ...
[ 3.940076] md: adding sdb1 ...
[ 3.940207] md: adding sda1 ...
[ 3.940495] md: created md1
[ 3.940624] md: bind<sda1>
[ 3.940765] md: bind<sdb1>
[ 3.940905] md: running: <sdb1><sda1>
[ 3.941233] md/raid1:md1: active with 2 out of 2 mirrors
[ 3.941388] md1: detected capacity change from 0 to 107374116864
[ 3.941526] md: ... autorun DONE.
[ 3.943359] EXT4-fs (md1): couldn't mount as ext3 due to feature incompatibilities
[ 3.985138] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: (null)
[ 9.235215] Adding 2097084k swap on /dev/md2. Priority:-1 extents:1 across:2097084k
[ 9.998237] EXT4-fs (md1): re-mounted. Opts: (null)
[ 105.253940] md124: detected capacity change from 375809572864 to 0
[ 105.253950] md: md124 stopped.
[ 105.253959] md: unbind<sdb3>
[ 105.258033] md: export_rdev(sdb3)
[ 105.258083] md: unbind<sda3>
[ 105.262015] md: export_rdev(sda3)
[ 107.749713] md125: detected capacity change from 514872442880 to 0
[ 107.749723] md: md125 stopped.
[ 107.749733] md: unbind<sdb4>
[ 107.754051] md: export_rdev(sdb4)
[ 107.754084] md: unbind<sda4>
[ 107.759025] md: export_rdev(sda4)
[ 114.843287] md: md3 stopped.
[ 114.844140] md: bind<sdb3>
[ 114.844329] md: bind<sda3>
[ 114.850069] md/raid1:md3: active with 2 out of 2 mirrors
[ 114.850109] md3: detected capacity change from 0 to 375809572864
[ 114.910224] md: md4 stopped.
[ 114.911789] md: bind<sdb4>
[ 114.911992] md: bind<sda4>
[ 114.923705] md/raid1:md4: active with 2 out of 2 mirrors
[ 114.923745] md4: detected capacity change from 0 to 514872442880

uname -a :

Linux drago 4.4.29 #2 SMP Mon Oct 31 15:02:12 CDT 2016 x86_64 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz GenuineIntel GNU/Linux
drago.domain.com


mdadm -Es:

ARRAY /dev/md1 UUID=7cc47bea:832f8260:208cdb8d:9e23b04b
ARRAY /dev/md2 UUID=cce81d3a:78965aa5:208cdb8d:9e23b04b
ARRAY /dev/md124 UUID=f0bc71fc:8467ef54:208cdb8d:9e23b04b
ARRAY /dev/md125 UUID=3f4daae2:cbf37a2a:208cdb8d:9e23b04b
 
Old 11-21-2016, 01:39 PM   #14
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,881

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
I have basically no experience with mdadm, so I may be completely wrong here, but what causes the "md124/md125 and/or md3/md4" devices to mount? Is it the mdadm.conf or the fstab.conf?

Either way, you should be able to reference them more directly. Instead of using /dev/md3 and /dev/md4, which can change, use /dev/disk/by-uuid/f0bc71fc:8467ef54:208cdb8d:9e23b04b and /dev/disk/by-uuid/3f4daae2:cbf37a2a:208cdb8d:9e23b04b. That should reference the drives directly and shouldn't matter how they're labelled as far as /dev/md* (which can change unexpectedly).
 
Old 11-21-2016, 02:27 PM   #15
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
Quote:
Originally Posted by bassmadrigal View Post
I have basically no experience with mdadm, so I may be completely wrong here, but what causes the "md124/md125 and/or md3/md4" devices to mount? Is it the mdadm.conf or the fstab.conf?

Either way, you should be able to reference them more directly. Instead of using /dev/md3 and /dev/md4, which can change, use /dev/disk/by-uuid/f0bc71fc:8467ef54:208cdb8d:9e23b04b and /dev/disk/by-uuid/3f4daae2:cbf37a2a:208cdb8d:9e23b04b. That should reference the drives directly and shouldn't matter how they're labelled as far as /dev/md* (which can change unexpectedly).
no, no, that looks completely wrong.

mdadm assemble raid arrays, ang give names for it ( say, /dev/md3 for array from sda3 and sdb3). mount is via fstab, but that is second step, and there is no any problems with mount - problems is with raid arrays naming. md1 and md2, strangely, is ok, but md3 and md4 become as md124 and md125 - and i cannot understand, why? why half of my raid1 arrays work as it must be, and another half - not? :-O

in right configuring system raid arrays naming must not be changed, that is the point and idea. and i am not sure, that mounting raid arrays via UUID is a right thing - never before encounter that idea. and in any way, i want to get arrays naming thing done...

Last edited by WiseDraco; 11-21-2016 at 02:30 PM.
 
  


Reply

Tags
lilo, raid1, slackpkg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
raid1 mdadm repair degraded array with used good hard drive catbird Linux - Hardware 7 07-09-2009 12:31 AM
Have software raid1, but like to change to raid1+0 or 0+1, how? spaceuser Debian 8 03-17-2008 02:07 PM
I need a Linux OS other than Ubuntu which has a repair disk or repair software jhmac77 Linux - Newbie 1 03-17-2008 07:04 AM
How to repair Lilo on Macbook using rEFIt dr_jared88 Debian 1 09-22-2007 09:45 PM
lilo + raid1 = 99 99 99 99 99 .... tct1501 Linux - Software 3 11-02-2006 03:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:38 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration