Enjoy Slackware 15.0!

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 revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
howtos:misc:software_raid_troubleshoot_howto [2016/11/27 11:50 (UTC)]
wisedraco [Sources]
howtos:misc:software_raid_troubleshoot_howto [2016/11/27 12:45 (UTC)]
wisedraco [Useful commands in this case]
Line 1: Line 1:
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
 +
 ====== Software RAID troubleshoot ====== ====== Software RAID troubleshoot ======
  
Line 5: Line 6:
 i be done with system, who,after lilo menu,\\ i be done with system, who,after lilo menu,\\
  write "loading kernel ............................." \\  write "loading kernel ............................." \\
 +\\
 and then stops completely - nothing more.\\ and then stops completely - nothing more.\\
 +\\
 Initial configuration was:\\ Initial configuration was:\\
 Intel DG965SS motherboard, core 2 duo 2.2 gHz E4500 CPU, 8 Gb RAM, \\ Intel DG965SS motherboard, core 2 duo 2.2 gHz E4500 CPU, 8 Gb RAM, \\
 2 x 1000 Gb Seagate SATA HDD ( as sda and sdb)\\ 2 x 1000 Gb Seagate SATA HDD ( as sda and sdb)\\
 ST1000DM003-1CH1\\ ST1000DM003-1CH1\\
-dvd-writer on sata4 port+dvd-writer on sata4 port
  
 both seagate discs is partitioned as FD type ( linux autodetect raid) and 4 partitions ( mbr type) -  both seagate discs is partitioned as FD type ( linux autodetect raid) and 4 partitions ( mbr type) - 
-   * 100 Gb root (md1) +  * 100 Gb root (md1) 
-  *  2 Gb swap (md2) +  * 2 Gb swap (md2) 
-  *  350 Gb /home (md3) +  * 350 Gb /home (md3) 
-  *  550 Gb /Second (md4) +  * 550 Gb /Second (md4) 
 +\\ 
 +\\
 cat /proc/mdstat : cat /proc/mdstat :
  
Line 37: Line 40:
 unused devices: <none> unused devices: <none>
 </code> </code>
 +\\ 
 +\\
 mdadm -Es : mdadm -Es :
  
Line 61: 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 327: 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 - 
Line 346: Line 353:
 </code> </code>
  
-take a note!+<note important>take a note!
 disk UUID by  disk UUID by 
  
Line 352: Line 359:
  
 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 363: Line 374:
   - 2. Using initramd.   - 2. Using initramd.
  
 +<code>
 # #
 # mkinitrd_command_generator.sh revision 1.45 # mkinitrd_command_generator.sh revision 1.45
Line 376: Line 388:
 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 395: Line 410:
 ====== 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
-mdadm -Db /dev/md127+</code>
  
 +show defined array another info:
 +<code>
 +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? )
  
  

In Other Languages
QR Code
QR Code howtos:misc:software_raid_troubleshoot_howto (generated for current page)