grub doesn't auto-load kernel, time/date auto-change, k3b cannot load
 

Hi,

Here's HW my specs:
AMD64 2800+
Asus K8V SE Deluxe mobo
1GB DDR400 RAM
Asus ATI 9200 pro
2*200GB Seagate ATA100 HDD
Asus 8x DVD+/-RW
Gigabyte 52x CD-RW

Running as a non-internet fileserver:
software RAID1
Redhat 9 + 2.6.6 kernel
samba 3.0.6

i'm not sure whether the problem is in my settings or my hardware!

Prob 1) at first things are fine with grub, I don't remember doing anything weird but now I have to load the kernel manually. It says loading grub stage 1.5, then i was spit into grub>.
I tried booting with the RH9 CD, went to linux rescue, and did the following in grub prompt:
grub> root (hd0,0)
grub> setup (hd0)
grub> quit
i rebooted but the same problem still persists...

Prob 2) After i manually load root, vmlinuz and initrd, i login to the system and find my time and date changed for no reason.
My hardware clock is normal /usr/sbin/hwclock --show, i had to reset my time everytime i reboot my server...

Prob 3) K3B take forever to load. I installed it from an RPM package.

Prob 4) redhat-samba-config cannot load. It did ask for root passwd but nothing comes out after I type in the passwd...

I tried to simulate the problems above with another test PC:
Intel P4 2.4GHz
Asus P4PE-X mobo
512MG DDR400 RAM
40GB + 80 GB Seagate ATA100 HDD
GeForce MX440
16x DVD-ROM
52x CD-RW

Running as test-internet DNS and fileserver:
software RAID1
Redhat 9 + 2.6.6 kernel
samba 3.0.9

1) I got to install GRUB again, working merrily
2) no problems with date/time
3) I can burn CDs with K3B
4) same problem as the above system, still cannot solve...

Hope to get some tips and comments from you all!

1) Reinstall GRUB with the grub-install command.
2) Did you configured a wrong timezone? Do you use a NTP server?
3) k3b: The RHL9 package from http://fedora.us is good and recommended.
4) Start the tool inside an X terminal, such as xterm. What do you get?

thanks for the reply!

1) I'm using RAID1, will it matter which drive i install grub into? also, do I boot from "linux rescue" or can I do this installation after I log in? just to comfirm, is this correct?
/sbin/grub-install /dev/hda

2) I checked the time zone, here's my /etc/sysconfig/clock
nope, no NTP server

3) Fedora packages work with Redhat? Doesn't matter, I'll give it a try anyway :D
I got my package from http://dag.wieers.com/packages/

4) I did that and here's the error:
I commented out smb ports and tried to start again, the same message appeared but the last line is:
Commented that line out as well and it worked! What's wrong having those 2 lines in my smb.conf?

Cheers misc! :)

~WiLL~

Uhm? With Software (!) RAID1, you install the bootloader into the Master Boot Record and have a separate /boot partition which cannot be RAID1.
Yes.

How big is the clock skew each time you reboot? Remove the /etc/adjtime file prior to rebooting.
You misunderstood me. http://fedora.us started as a Red Hat Linux add-ons provider and still provides those, too. You don't get k3b at Dag Wieer's repository.

Don't know. Maybe those settings are not yet supported. Consider creating a config file from scratch using the tool.

I reckon that if i have 2 drives, the MBR should be in either one of those drives?
How do I check the location of the original MBR?
I've setup hda1 and hdc1 to be md0 which is /boot... what should i do?

From memory, it's 12 hours i think...
i'll just rename it, will get back to you later in the day as users are logged on the server now.

Oh, really? thanks!
I tried installing samba for FC1 on my redhat once and it didn't work... that was long ago though ;)
Well my k3b will load if i load it via xterm but not when i click on the icon...
Here's the message i got from xterm:
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
mcop warning: user defined signal handler found for SIG_PIPE, overriding

I get this sort of message when i run gedit from xterm, it goes:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
What you reckon is wrong?

That's weird... testparm didn't give me any errors. i did write it from scratch, took me ages to do that! :D

:confused: The first sector of every drive can be the MBR.
That doesn't give you full RAID1, since GRUB doesn't do Software RAID. It would load its files from the physical drive you configured to load from (specifically partition (hd0,0) which is /dev/hda1), and in case that fails, it would not load from the mirror drive.

No comment, since you modified Red Hat Linux 9 by replacing core packages. It would be a waste of time trying to debug what impact all the changes could have. It looks as if you somehow misconfigured/disabled X server access authorization.

That's the problem I had when I first used RAID1 with grub, but later on I found on article on Dell's website regarding using RAID1 with grub on RHEL3. So their workaround was to install grub on the MBR of the second drive as well:
I've tried this method on a test system and it works OK. The only problam is you have to do this everytime you do raidhotadd your /boot back into the RAID array.


Well, i've been getting this message since the first time I installed redhat half a year ago.
What can I do to enable authorization? programs work fine though, just that the message is kinda irritating...

Try running "xhost +" as a test.

btw, i'm logged into the machine as a user but as root in console

My server's time/date is working fine now, thanks!

I tried installing grub into the MBR using:
and I get this:
/dev/md0 does not have any corresponding BIOS drive
removed /dev/hda1 from the /dev/md0 array but it still gave me the same message...

kenji1903

my howto does not have any raid as I don't use it.

WHICH MEANS MY ADVICE IS SUSPECT

FYI I believe hardware failure....the only reason for raid is a risk I am prepared to take. If you are in business....well good for you.

2) Have you read this which is mentioned in one of your thread replies
http://lists.us.dell.com/pipermail/l...ly/014331.html

3) I would modify that slightly....
you mention that grub that with the find command finds
hd0 and hd1

so you would in a terminal ....NOT grub-install as I want you to get feedback....
root (hd0,0)
setup (hd0)

root (hd1,0)
setup (hd1)

4) I started a thread that no-one else replied to (boo hoo) that has some links I recommend you view that may help you
http://www.linuxquestions.org/questi...aid+controller

in particular if you are pressed for time is this raid howto on another forum
http://forums.gentoo.org/viewtopic.p...ight=grub+raid

additional comments ....I am still SUSPECT

the reason for putting grub into both mbrs....remember every floppy...cd....hd has a mbr is that when your hd fails....the reason for having raid to begin with....you change your bios to boot drive 2 which would find the drive2 mbr which has grub in mbr which has grub booting files in /boot

do you agree?

2) Instead of raid.....would you consider, if no-one solves this current issue of using your drives in non-raid ie normal mode.....with backups to cdrs or tape drives and /or backup of partitions with www.partimage.org?

G'day Aus,

It has been a long time ;)
I reformatted my server last night but reckon this problem will occur again some time later, so it's better if i can get a solution now. Feedback (before I reformat):
Looks OK to me, but grub still won't boot by itself...
Your posts are pretty informative, cheers! :D

Agree~

I'm using RAID as an addition to my DVD backups, I'm using tar by the way ;)
The power supply in China's new industrial areas are not stable as i get voltage spikes and power outages pretty often... I do have a UPS connected to the server, just that local Chinese products are of very low quality :(

ok so we now have grub in mbr because your feedback shows .......succeeded

so grub fails for only 3 reasons

1 grub can not handle the hardware......but as grub on screen i don't think so
2 you have not built a kernel or are using a kernel that does not have sata support built in or correct modules found.......likely
3 your bios is soooo old you have a cylinder 1024 issue mentioned in my howto.......unlikely but go into bios and look for lba SETTING
make sure its turned on........or flash your bios if you have a real old one like 5 years old.

so lets assume its the SATA drive......as you can see from my specs......i am on a sata and guess what I have grub heh heh
/boot/config is the file for how the kernel was compiled

open this file and do a control F for find function to search for this entry ......I have a via sata....you need to check what ASUS uses
CONFIG_SCSI_SATA=y.......this is good for all mobos
when you find this line you will notice some more juicy stuff.
my std MDK kernel included this line
CONFIG_SCSI_SATA_VIA=m but my own kernel was made yes....but this is for only VIA CHIPSETS

yours may differ

I reckon that was the problem too, but my drives are PATA so GRUB must have support for them...
My BIOS is flashed to the lastest one already :D

Hmm... are SATA drives playing nice with Linux now?
I am planning to upgrade my existing drives to SATA, heard the support can be better though. Any problems and comments from a current user such as yourself?

I'll keep that in mind when i compile kernels for SATA drives, what about those Promise, etc drivers in the kernel? Are you using them as well?

don't know about promise support as I have VIA chipsets on a gigabyte board.

Mdk installed without any hiccups so its not be an issue for me.....but because I had a slooow old computer and dial up modem.....I knew I would have a problem with my old slackware system.

so compiling a kernel with either inbuilt support or with ramdisk image with promise you may need to check out?

is you want to wait there is sata2 coming out at some time......more transfer speed

Yup, I will! Cheers, mate!