Topic: GRUB work but no timeout

[FredoO]

Hello!

I use SME server for a few weeks and I am very happy with its functions for multiple sites and an email server that works better than my internet provider !

So I decided to change my server that consumes too much against a mini-pc Giada i35v (fully compatible with sme server  )

I have 2 little problem:

-When I reboot the server, GRUB have no timeout, I have to tap the Enter key on the keyboard to continue.

-2nd problem, perhaps related to the first, on the old server I had two hard drives in RAID1, but in the new I have one disk : how can I remove the error "A DegradedArray event has-been detected on md device / dev/md1." (i have restored the new server from the old)

Thank you

[idp_qbn]

I can help (sort of) with Problem (2).
SME expects to find two disks at least and create/operate a 2-disk RAID1 array.
When it finds only 1 disk, it reports the RAID1 array as being degraded.
If you had two disks and got this message, it would indicate you have a problem.
With 1 disk, it is just SME having a little whinge and nothing is really broken.

HOWEVER - get a second disk and install it. Let SME have its 2-disk RAID1 array and it will stop giving you that error message.
Actually, don't think of it as an error message... think of it as a gentle hint.

If availability and reliability are important to you, take the hint.

Cheers
Ian

[FredoO]

Thanks for your quick response !

I can't had second hard drive ,cause this little computer use mSATA drive and i'm not very sure there is a 2nd port for internal drive (there is not too much info on the web about this mini-pc :/ )

There is a way to 'teach" mdadm there is just one disk now?

(sorry for my bag english...)

[idp_qbn]

There is a way to 'teach" mdadm there is just one disk now?

No - I don't think you can unless you modify the base code and then you are on your own.....

Either: Just accept the error message and carry on regardless, (in your case, remember the message is a HINT rather than a WARNING)
OR: use a PC that has 2 disks. (that way, if one disk dies, the other disk carries on - and the message is a WARNING not a HINT)

Sorry, but you have just paddled your Canoe of Hope into the Rapids of Reality.

Looks like a nice little PC, though (the Giada 135V)
And your English is pretty good, FredoO

Cheers
Ian

[FredoO]

OK

I think I'll invest --> http://www.materiel.net/disque-ssd/crucial-m4-32-go-msata-sata-iii-6-gb-s-81260.html


It's not a real warning like you say ,but the raid1 is really great for have  tranquillity .

For who want to invest in the giada i35v for personal use ,know the fan is very loud (4500rpm ,i think it's operating system related) BUT ,you can adjust manually the speed of fan in the bios setting and everything is silent at 2500rpm , or PMW=90 ,and the temp stay below 50°C )

There is not too much info on the net about this machine ,so if you are intersted do not hesitate to ask me questions .

For my problem with GRUB ,it's not really important because i don't want reboot the server often ,but it's a strange bug.

[stephdl]

for your timeout problem you can look to this file

Code: [Select]

nano  /boot/grub/grub.conf
and modify

Code: [Select]

timeout=5
with your values

for your raid problem, i think you have to  get two disks if you want to protect at least your data...but if you want to avoid your error message, you can play with mdadm to kick the second disk.
this is an example for /dev/sdb (i suppose that your missing disk is sdb)

http://wiki.contribs.org/Raid:Manual_Rebuild#Fail_and_remove_the_disk.2C_sdb_in_this_case

Code: [Select]

Fail and remove the disk, sdb in this case

[root@ ~]# mdadm --manage /dev/md2 --fail /dev/sdb2
mdadm: set /dev/sdb2 faulty in /dev/md2
[root@ ~]# mdadm --manage /dev/md2 --remove /dev/sdb2
mdadm: hot removed /dev/sdb2
[root@ ~]# mdadm --manage /dev/md1 --fail /dev/sdb1
mdadm: set /dev/sdb1 faulty in /dev/md1
[root@ ~]# mdadm --manage /dev/md1 --remove /dev/sdb1
mdadm: hot removed /dev/sdb1


[FredoO]

I check the grub.conf ,everything look good.

Code: [Select]

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/main/root
#          initrd /initrd-version.img
#boot=/dev/md1
default=0
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
title SME Server (2.6.18-348.4.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-348.4.1.el5 ro root=/dev/main/root
initrd /initrd-2.6.18-348.4.1.el5.img
title SME Server (2.6.18-308.4.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-308.4.1.el5 ro root=/dev/main/root
initrd /initrd-2.6.18-308.4.1.el5.img

Thanks you for the tip :make the drive in fail statut then remove it ! (impossible to find again this link ,thx !)

[stephdl]

-2nd problem, perhaps related to the first, on the old server I had two hard drives in RAID1, but in the new I have one disk : how can I remove the error "A DegradedArray event has-been detected on md device / dev/md1." (i have restored the new server from the old)

where the message is seen, in the admin console by ssh 

http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter6

or by mail from root every night ?

[stephdl]

I check the grub.conf ,everything look good.

have you tryed to change to any other values to see if something can be changed....10 for example
after that you simply need to reboot the server

[FredoO]

where the message is seen, in the admin console by ssh 

http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter6

or by mail from root every night ?

By mail ,every time i reboot (my new hardware have less than 4H of uptime ^^)

Code: [Select]

# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda1[0]
      104320 blocks [2/1] [U_]
     
md2 : active raid1 sda2[0]
      31157952 blocks [2/1] [U_]

Code: [Select]

# mdadm --manage /dev/md1 --fail /dev/sda1
mdadm: set device faulty failed for /dev/sda1:  Device or resource busy

[stephdl]

STOP

your good device is sda1, don't try to kick it from your raid array

[stephdl]

all your command need to be for sdb which is the raid device missed

Code: [Select]

# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda1[0]
      104320 blocks [2/1] [U_]
     
md2 : active raid1 sda2[0]
      31157952 blocks [2/1] [U_]
so you have to play as i  wrote

Code: [Select]

[root@ ~]# mdadm --manage /dev/md2 --fail /dev/sdb2
mdadm: set /dev/sdb2 faulty in /dev/md2
[root@ ~]# mdadm --manage /dev/md2 --remove /dev/sdb2
mdadm: hot removed /dev/sdb2
[root@ ~]# mdadm --manage /dev/md1 --fail /dev/sdb1
mdadm: set /dev/sdb1 faulty in /dev/md1
[root@ ~]# mdadm --manage /dev/md1 --remove /dev/sdb1
mdadm: hot removed /dev/sdb1