[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:25 (UTC)] – [Workarounds for incorrect raid devices naming] 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 338: Line 338:
 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 353: Line 365:
 </code> </code>
  
-take a note!+<note important>take a note!
 disk UUID by  disk UUID by 
  
Line 367: Line 379:
  
 differ, not the same!!! differ, not the same!!!
- in fstab ( lilo too?) you must use UID from /dev/disk/by-uuid/  !+ in fstab ( lilo too?) you must use UID from /dev/disk/by-uuid/  !</note>
  
  
Line 409: Line 421:
    
 ====== Useful commands in this case ====== ====== Useful commands in this case ======
 +
 +show raid array info:
 +
 <code> <code>
 mdadm -Es mdadm -Es
 </code> </code>
  
 +Assemble RAID array based on mdadm.conf
 <code> <code>
 mdadm -As mdadm -As
 </code> </code>
  
 +show array info:
 <code> <code>
 mdadm -D /dev/md127 mdadm -D /dev/md127
 </code> </code>
  
 +show defined array another info:
 <code> <code>
 mdadm -Db /dev/md127 mdadm -Db /dev/md127
 </code> </code>
  
 +show scsi devices info:
 <code> <code>
 lsscsi lsscsi
 </code> </code>
  
 +show assembled raid arrays status:
 <code> <code>
 cat /proc/mdstat cat /proc/mdstat
 </code> </code>
  
 +show UUID info about discs ( or RAID arrays) in system:
 <code> <code>
 ls /dev/disk/by-uuid/ ls /dev/disk/by-uuid/
Line 441: Line 462:
 </code> </code>
  
 +re-run lilo, when booted from another source.
 <code> <code>
 chroot /mnt/hd /sbin/lilo -v 3 chroot /mnt/hd /sbin/lilo -v 3
 </code> </code>
  
 +
 +stop named RAID array:
 <code> <code>
 mdadm --stop /dev/md127 mdadm --stop /dev/md127
Line 454: Line 478:
 $kernelname raid=noautodetect md=1, /dev/sda1,/dev/sdb1 $kernelname raid=noautodetect md=1, /dev/sda1,/dev/sdb1
 </code> </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 ()