<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Something is fishy.<BR>
<BR>
The below described symptoms can all be seen with build 160.<BR> <BR>For a little while I thought I may have been alarming everyone without properly checking possible hardware causes. I ran drive tests and one sata cable has come under suspicion of being the culprit. It turned out to be non reliable. It caused an intermittent contact problem that got previously covered up by a running (CentOS) raid 6.<BR>But replacing the sata cable and running the hdd manufacturer's utilities didn't fix it (low level format of all 4 drives. Then ran diagnostics on them. No errors).<BR>Removing just (any) one drive seems to make the install work.<BR> <BR>I am confused by the XS setup messages:<BR>After the line: Starting HAL daemon: [ok]<BR>comes: FATAL: module md not found.<BR>then come several raid6 lines - 1st one: raid6: int 32x1 738MB/s<BR>[...]<BR>last one: raid6: using algorithm sse2x2 (3511 MB/s)<BR> <BR>Raid6 without module md and with only 3 hdds?<BR> <BR> <BR> <BR>The setup with four hdds leads to (mostly cyrillic) character soup and crashes offering an anaconda dump (see attached file).<BR> <BR>With three hdds the setup finishes (with the same confusing raid6 message lines quoted above)<BR>and df -a -h reports the following:<BR>Filesystem Size Used Avail Use% Mounted on<BR>/dev/sda2 7.9G 1.4G 6.5G 18 /<BR>proc 0 0 0 - /proc<BR>sysfs 0 0 0 - /sys<BR>devpts 0 0 0 - /dev/pts<BR>/dev/sda1 99M 12M 82M 13% /boot<BR>tmpfs 1014M 0 1014M 0% /dev/shm<BR>/dev/mapper/VolGroup00-LogVol00<BR> 442G 199M 419G 1% /library<BR>none 0 0 0 - /proc/sys/fs/binfmt_misc<BR> <BR>This makes me think there is no raid and only sda is being used. With module md not found this is only to be expected. But little do I know and my expectations are pretty non-consequential in this realm ;-)<BR>
The hardware provided 3 500GB hdds (actually 4, but I had to unplug one to get a set-up to finish). <BR>
<BR>
What do you think is going on?<BR>
Anybody ever tried this using a different mobo / sata controller (mine is the on-board nVidia MCP61)?<BR> <BR><BR>Stefan<BR><BR>
<BR>
<BR>> Date: Sun, 6 Apr 2008 16:54:14 -0300<BR>> From: martin.langhoff@gmail.com<BR>> To: wad@laptop.org<BR>> Subject: Re: [Server-devel] XS server: raid 6 configuration with build 160, 161, 162 not ok<BR>> CC: stefan_w_reitz@hotmail.com; server-devel@lists.laptop.org<BR>> <BR>> On Fri, Apr 4, 2008 at 10:31 PM, John Watlington <wad@laptop.org> wrote:<BR>> > Thanks for warning us. There are places where the kickstart script<BR>> > explicitly<BR>> > references and formats /dev/sda. Does the device name change when soft<BR>> > RAIDed ? I can't think of any script changes from build 150 to<BR>> > build 160 that<BR>> > would explain this.<BR>> <BR>> Hmmm. I wonder if we can provide a default template for<BR>> diskdruid/gparted and allow the user to override the partitioning.<BR>> <BR>> I will look into it when I have a chance.<BR>> <BR>> cheers,<BR>> <BR>> <BR>> <BR>> martin<BR>> -- <BR>> martin.langhoff@gmail.com<BR>> martin@laptop.org -- School Server Architect<BR>> - ask interesting questions<BR>> - don't get distracted with shiny stuff - working code first<BR>> - http://wiki.laptop.org/go/User:Martinlanghoff<BR><BR><BR><br /><hr />Windows Live Messenger <a href='http://redirect.gimas.net/?cat=hmtl&n=M0804WLM&d=http://get.live.com/de-de/messenger/overview' target='_new'>Automatisch über neue E-Mails informiert!</a></body>
</html>