[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
howtos:misc:software_raid_troubleshoot_howto [2016/11/27 12:20 (UTC)] – [Software RAID troubleshoot] wisedracohowtos:misc:software_raid_troubleshoot_howto [2017/06/26 15:08 (UTC)] (current) – [Workarounds for incorrect raid devices naming] wisedraco
Line 65: Line 65:
 Then i do massive system update via slackpkg update-all, including kernel update too.\\ Then i do massive system update via slackpkg update-all, including kernel update too.\\
 check lilo.conf, restart - all looks ok. then i decide to upgrade system to 14.2 via the same slackpkg \\ check lilo.conf, restart - all looks ok. then i decide to upgrade system to 14.2 via the same slackpkg \\
-( looks like live on macos is too boring, too predictable - all work, and so on...:D )+( looks like live on macos is too boring, too predictable - all work, and so on...:D )\\
 always, i check lilo.conf, check the new kernel is named right, have no old kernel for backup - \\ always, i check lilo.conf, check the new kernel is named right, have no old kernel for backup - \\
 only one entry in lilo ( who was not good thing at all! ), and do reboot. only one entry in lilo ( who was not good thing at all! ), and do reboot.
Line 331: Line 331:
  
  do a   do a 
 +
 +<code>
 ls /dev/disk/by-uuid/ ls /dev/disk/by-uuid/
 +</code>
  
 or better, go in that location with midnight commander, and youl see, there is a "files" named as numbers -  or better, go in that location with midnight commander, and youl see, there is a "files" named as numbers - 
 that was the raid array disk uuid - and symlink to /dev/mdx. that was the raid array disk uuid - and symlink to /dev/mdx.
 +
 +for automate info feed into fstab you can use this way:
 +
 +<code>
 +
 +cd /dev/disk/by-uuid
 +
 +ls -d -l $PWD/* >> /etc/fstab
 +</code>
 +
 +after that you must immediately edit /etc/fstab and make in a right way, otherwise you may have problems with mounting in next boot...
 +
  
 <code> <code>
Line 350: Line 365:
 </code> </code>
  
-take a note!+<note important>take a note!
 disk UUID by  disk UUID by 
  
Line 356: Line 371:
  
 and that one, who you get via  and that one, who you get via 
 +
 +<code>
 mdadm -D mdadm -D
 mdadm -Db mdadm -Db
 mdadm -Es mdadm -Es
 +</code>
  
-differ! in fstab ( lilo too?) you must use UID from /dev/disk/by-uuid/  !+differ, not the same!!! 
 + in fstab ( lilo too?) you must use UID from /dev/disk/by-uuid/  !</note>
  
  
Line 367: Line 386:
   - 2. Using initramd.   - 2. Using initramd.
  
 +<code>
 # #
 # mkinitrd_command_generator.sh revision 1.45 # mkinitrd_command_generator.sh revision 1.45
Line 380: Line 400:
 mkinitrd -c -k 3.2.29 -f ext4 -r /dev/md1 -m mbcache:jbd2:ext4 -R -u -o /boot/initrd.gz mkinitrd -c -k 3.2.29 -f ext4 -r /dev/md1 -m mbcache:jbd2:ext4 -R -u -o /boot/initrd.gz
  
-rightly edited mdadm.conf then must be copied in/boot/tree??? before you run this mkinitrd conf.+</code> 
 +\\ 
 +\\ 
 +rightly edited mdadm.conf then must be copied in/boot/tree??? before you run this mkinitrd conf.\\
  
 after you run that mkinitrd, you must update lilo. after you run that mkinitrd, you must update lilo.
Line 399: Line 422:
 ====== Useful commands in this case ====== ====== Useful commands in this case ======
  
 +show raid array info:
 +
 +<code>
 mdadm -Es mdadm -Es
 +</code>
 +
 +Assemble RAID array based on mdadm.conf
 +<code>
 mdadm -As mdadm -As
 +</code>
  
 +show array info:
 +<code>
 mdadm -D /dev/md127 mdadm -D /dev/md127
 +</code>
 +
 +show defined array another info:
 +<code>
 mdadm -Db /dev/md127 mdadm -Db /dev/md127
 +</code>
  
 +show scsi devices info: 
 +<code>
 lsscsi lsscsi
 +</code>
 +
 +show assembled raid arrays status:
 +<code>
 cat /proc/mdstat cat /proc/mdstat
 +</code>
 +
 +show UUID info about discs ( or RAID arrays) in system:
 +<code>
 ls /dev/disk/by-uuid/ ls /dev/disk/by-uuid/
 +</code>
  
 +<code>
 dmesg |grep md dmesg |grep md
 +</code>
  
 +re-run lilo, when booted from another source.
 +<code>
 chroot /mnt/hd /sbin/lilo -v 3 chroot /mnt/hd /sbin/lilo -v 3
 +</code>
  
 +
 +stop named RAID array:
 +<code>
 mdadm --stop /dev/md127 mdadm --stop /dev/md127
 +</code>
  
 kernel options: kernel options:
 +
 +<code>
 +$kernelname raid=noautodetect md=1, /dev/sda1,/dev/sdb1
 +</code>
 +
 +turn on not to autodetect RAID arrays, and define raid array /dev/md1, from two partitions ( members? )
  
  

Trace:

howtos:misc:software_raid_troubleshoot_howto ()