Olá Helio,

Sou eu mesmo.
Assunto resolvido.

Valeu

Sérgio Abrantes


2014-07-04 13:46 GMT-03:00 Helio Loureiro <he...@loureiro.eng.br>:

> Foi vc que postou essa dúvida no facebook, e acabou resolvendo?
>
> Abs,
> Helio Loureiro
> http://helio.loureiro.eng.br
> http://br.linkedin.com/in/helioloureiro
> http://twitter.com/helioloureiro
> http://gplus.to/helioloureiro
>
>
> 2014-06-28 22:16 GMT-03:00 Sérgio Abrantes Junior <
> sergioabran...@gmail.com>:
>
> Olá pessoal,
>>
>> Estou montando um servidor com RAID1.
>> Fiz o RAID na instalação e com um cat em /proc/mdstat não apresenta
>> problema como abaixo:
>>
>> sergio@firewall:~$ cat /proc/mdstat
>> Personalities : [raid1]
>> md3 : active (auto-read-only) raid1 sda5[0] sdb5[1]
>>       3973056 blocks super 1.2 [2/2] [UU]
>>
>> md2 : active raid1 sda3[0] sdb3[2]
>>       258658112 blocks super 1.2 [2/2] [UU]
>>
>> md1 : active raid1 sda2[0] sdb2[2]
>>       48795520 blocks super 1.2 [2/2] [UU]
>>
>> md0 : active raid1 sda1[0] sdb1[2]
>>       975296 blocks super 1.2 [2/2] [UU]
>>
>> unused devices: <none>
>> sergio@firewall:~$
>>
>> Fazendo teste de boot apenas com o disco 1 e depois com o disco 2, apenas
>> com um disco funciona.
>> Ele aparece o kernel para escolha na inicialização, mas depois não
>> continua a sequência de inicialização do linux.
>> Alguém já passou por isso?
>>
>> Segue abaixo mais alguns confs que possam ajudar:
>>
>> sergio@firewall:~$ cat /etc/fstab
>> # /etc/fstab: static file system information.
>> #
>> # Use 'blkid' to print the universally unique identifier for a
>> # device; this may be used with UUID= as a more robust way to name devices
>> # that works even if disks are added and removed. See fstab(5).
>> #
>> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
>> # / was on /dev/md2 during installation
>> UUID=86cb1813-97e4-4c77-8bef-4b51db654929 /               ext4
>> errors=remount-ro 0       1
>> # /boot was on /dev/md0 during installation
>> UUID=033fb59a-1158-4117-ae09-1207cc0a3515 /boot           ext4
>> defaults        0       2
>> # /var/log/squid3 was on /dev/md1 during installation
>> UUID=db91f114-4f55-47cf-8c58-bfbb938419a2 /var/log/squid3 xfs
>> defaults        0       2
>> # swap was on /dev/md3 during installation
>> UUID=507e3064-3f8b-4829-b85c-80be6b12a3b0 none            swap
>> sw              0       0
>> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
>> /dev/sdc1       /media/usb0     auto    rw,user,noauto  0       0
>>
>>
>> sergio@firewall:~$ cat /etc/mdadm/mdadm.conf
>> # mdadm.conf
>> #
>> # Please refer to mdadm.conf(5) for information about this file.
>> #
>>
>> # by default (built-in), scan all partitions (/proc/partitions) and all
>> # containers for MD superblocks. alternatively, specify devices to scan,
>> using
>> # wildcards if desired.
>> #DEVICE partitions containers
>>
>> # auto-create devices with Debian standard permissions
>> CREATE owner=root group=disk mode=0660 auto=yes
>>
>> # automatically tag new arrays as belonging to the local system
>> HOMEHOST <system>
>>
>> # instruct the monitoring daemon where to send mail alerts
>> MAILADDR xx@xx
>>
>> # definitions of existing MD arrays
>> ARRAY /dev/md/0 metadata=1.2 UUID=9ae2e8d4:5f169306:bef7d42d:a8049ecf
>> name=firewall:0
>> ARRAY /dev/md/1 metadata=1.2 UUID=55d87a74:44b932f3:9b6fe3f1:fad68002
>> name=firewall:1
>> ARRAY /dev/md/2 metadata=1.2 UUID=2bbb8f3d:17406b01:74235ee3:e38a9956
>> name=firewall:2
>> ARRAY /dev/md/3 metadata=1.2 UUID=65bc2a88:3ad32bcd:cdf3d0e2:a746221e
>> name=firewall:3
>>
>> # This file was auto-generated on Sat, 28 Jun 2014 17:04:02 -0300
>> # by mkconf 3.2.5-5
>> sergio@firewall:~$
>>
>>
>>
>> root@firewall:/boot/grub# cat grub.cfg
>> #
>> # DO NOT EDIT THIS FILE
>> #
>> # It is automatically generated by grub-mkconfig using templates
>> # from /etc/grub.d and settings from /etc/default/grub
>> #
>>
>> ### BEGIN /etc/grub.d/00_header ###
>> if [ -s $prefix/grubenv ]; then
>>   load_env
>> fi
>> set default="0"
>> if [ "${prev_saved_entry}" ]; then
>>   set saved_entry="${prev_saved_entry}"
>>   save_env saved_entry
>>   set prev_saved_entry=
>>   save_env prev_saved_entry
>>   set boot_once=true
>> fi
>>
>> function savedefault {
>>   if [ -z "${boot_once}" ]; then
>>     saved_entry="${chosen}"
>>     save_env saved_entry
>>   fi
>> }
>>
>> function load_video {
>>   insmod vbe
>>   insmod vga
>>   insmod video_bochs
>>   insmod video_cirrus
>> }
>>
>> insmod raid
>> insmod mdraid1x
>> insmod part_msdos
>> insmod part_msdos
>> insmod ext2
>> set root='(mduuid/2bbb8f3d17406b0174235ee3e38a9956)'
>> search --no-floppy --fs-uuid --set=root
>> 86cb1813-97e4-4c77-8bef-4b51db654929
>> if loadfont /usr/share/grub/unicode.pf2 ; then
>>   set gfxmode=640x480
>>   load_video
>>   insmod gfxterm
>>   insmod raid
>>   insmod mdraid1x
>>   insmod part_msdos
>>   insmod part_msdos
>>   insmod ext2
>>   set root='(mduuid/9ae2e8d45f169306bef7d42da8049ecf)'
>>   search --no-floppy --fs-uuid --set=root
>> 033fb59a-1158-4117-ae09-1207cc0a3515
>>   set locale_dir=($root)/grub/locale
>>   set lang=pt_BR
>>   insmod gettext
>> fi
>> terminal_output gfxterm
>> set timeout=5
>> ### END /etc/grub.d/00_header ###
>>
>> ### BEGIN /etc/grub.d/05_debian_theme ###
>> set menu_color_normal=cyan/blue
>> set menu_color_highlight=white/blue
>> ### END /etc/grub.d/05_debian_theme ###
>>
>> ### BEGIN /etc/grub.d/10_linux ###
>> menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian
>> --class gnu-linux --class gnu --class os {
>>     load_video
>>     insmod gzio
>>     insmod raid
>>     insmod mdraid1x
>>     insmod part_msdos
>>     insmod part_msdos
>>     insmod ext2
>>     set root='(mduuid/9ae2e8d45f169306bef7d42da8049ecf)'
>>     search --no-floppy --fs-uuid --set=root
>> 033fb59a-1158-4117-ae09-1207cc0a3515
>>     echo    'Loading Linux 3.2.0-4-amd64 ...'
>>     linux    /vmlinuz-3.2.0-4-amd64
>> root=UUID=86cb1813-97e4-4c77-8bef-4b51db654929 ro  quiet
>>     echo    'Loading initial ramdisk ...'
>>     initrd    /initrd.img-3.2.0-4-amd64
>> }
>> menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode)'
>> --class debian --class gnu-linux --class gnu --class os {
>>     load_video
>>     insmod gzio
>>     insmod raid
>>     insmod mdraid1x
>>     insmod part_msdos
>>     insmod part_msdos
>>     insmod ext2
>>     set root='(mduuid/9ae2e8d45f169306bef7d42da8049ecf)'
>>     search --no-floppy --fs-uuid --set=root
>> 033fb59a-1158-4117-ae09-1207cc0a3515
>>     echo    'Loading Linux 3.2.0-4-amd64 ...'
>>     linux    /vmlinuz-3.2.0-4-amd64
>> root=UUID=86cb1813-97e4-4c77-8bef-4b51db654929 ro single
>>     echo    'Loading initial ramdisk ...'
>>     initrd    /initrd.img-3.2.0-4-amd64
>> }
>> ### END /etc/grub.d/10_linux ###
>>
>> ### BEGIN /etc/grub.d/20_linux_xen ###
>> ### END /etc/grub.d/20_linux_xen ###
>>
>> ### BEGIN /etc/grub.d/30_os-prober ###
>> ### END /etc/grub.d/30_os-prober ###
>>
>> ### BEGIN /etc/grub.d/40_custom ###
>> # This file provides an easy way to add custom menu entries.  Simply type
>> the
>> # menu entries you want to add after this comment.  Be careful not to
>> change
>> # the 'exec tail' line above.
>> ### END /etc/grub.d/40_custom ###
>>
>> ### BEGIN /etc/grub.d/41_custom ###
>> if [ -f  $prefix/custom.cfg ]; then
>>   source $prefix/custom.cfg;
>> fi
>> ### END /etc/grub.d/41_custom ###
>> root@firewall:/boot/grub#
>>
>>
>

Responder a