Re: [sisuite-users] Booting from SALI, but install script doesn't run, & fails when run manually

2010-08-17 Thread Chris Pepper 
Dennis & Tristam,

Thanks! I also had to remove " -v1" from mkswap in a few places. 
Something is still broken, but I think I have reached an underlying hardware 
problem, so hopefully I'm done with software problems! ;)

Do you have any idea why the serial console echoes but otherwise 
ignores input, while the VGA console accepts input but sends its output to the 
serial console? I have never seen this behavior before.

Thanks again,

Chris

-- 
Chris Pepper:
  

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Booting from SALI, but install script doesn't run, & fails when run manually

2010-08-17 Thread Dennis Stam 



On 2010-08-17 01:33, Tristam MacDonald wrote:

On Aug 16, 2010, at 7:24 PM, Chris Pepper  wrote:


Tristam MacDonald wrote:

On Aug 16, 2010, at 5:07 PM, Chris Peppermailto:pep...@reppep.com>>  wrote:


With SALI our nodes connect to the imageserver and fetch scripts, but
they do not actually install. It's a bit confusing -- the VGA console
shows the correct hostname (c15), runs 99all.harmless_example_script,
then says "No script defined, opening console", "write_variables", and
"Starting console...".


You need to pass the SCRIPTNAME=whatever option to the kernel. See my
thread about tmpfs a few weeks ago - about halfway through is a detailed
description.


Tristam,

I'm pretty sure our older installation of 4.0.2 detected this
automatically from cluster.xml, but I will try tomorrow.


Systemimager does this fine, but it is listed as a current limitation
of SALI on the webpage (https://subtrac.sara.nl/oss/sali).



Any ideas why parted is choking when I run the script manually?


The reason that parted fails is because of this line in your install script:
{{{
DISK_SIZE=`parted -s $DISK0 unit MB print | grep 'Disk geometry for' | 
sed 's/^.*-//g' | sed 's/\..*$//' | sed 's/MB//' `

}}}

The line 'Disk geometry for' does not exist any more in the current 
version of parted. You can replace that line with the following:

{{{
DISK_SIZE=$(get_disksize $DISK0)
}}}

An other remark is when you are using Grub on a ext* partition. The 
newer e2fsprogs will set the inode block size of 256 by default. Grub 
does not support this. So you must add the parameter -I 128 to the 
mkfs.ext* command.




Despite it being stated several places that SALI supports default
system imager scripts, I didn't find that to be the case on our Dell
cluster. I ended up writing a custom script using the newer
'partition' command, since I decided to support ext4 and grub2 as
well.


Your right that SALI is not fully compatible with the installation 
scripts generated by systemimager. The main reason is that SALI uses 
newer versions of parted and e2fsprogs ( see previous comment ). This 
means you must adjust the DISK_SIZE variable and perhaps the inode block 
size when creating a ext* partition where grub is installed.


We shall update our documentation.



--
Tristam MacDonald
http://swiftcoder.wordpress.com
Sent from my iPad




--
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


--

Dennis Stam



smime.p7s
Description: S/MIME Cryptographic Signature
--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Booting from SALI, but install script doesn't run, & fails when run manually

2010-08-16 Thread Tristam MacDonald 
On Aug 16, 2010, at 7:24 PM, Chris Pepper  wrote:

> Tristam MacDonald wrote:
>> On Aug 16, 2010, at 5:07 PM, Chris Pepper > > wrote:
>>
>>> With SALI our nodes connect to the imageserver and fetch scripts, but
>>> they do not actually install. It's a bit confusing -- the VGA console
>>> shows the correct hostname (c15), runs 99all.harmless_example_script,
>>> then says "No script defined, opening console", "write_variables", and
>>> "Starting console...".
>>
>> You need to pass the SCRIPTNAME=whatever option to the kernel. See my
>> thread about tmpfs a few weeks ago - about halfway through is a detailed
>> description.
>
> Tristam,
>
>   I'm pretty sure our older installation of 4.0.2 detected this
> automatically from cluster.xml, but I will try tomorrow.

Systemimager does this fine, but it is listed as a current limitation
of SALI on the webpage (https://subtrac.sara.nl/oss/sali).

>
>   Any ideas why parted is choking when I run the script manually?

Despite it being stated several places that SALI supports default
system imager scripts, I didn't find that to be the case on our Dell
cluster. I ended up writing a custom script using the newer
'partition' command, since I decided to support ext4 and grub2 as
well.

--
Tristam MacDonald
http://swiftcoder.wordpress.com
Sent from my iPad
>

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Booting from SALI, but install script doesn't run, & fails when run manually

2010-08-16 Thread Chris Pepper 
Tristam MacDonald wrote:
> On Aug 16, 2010, at 5:07 PM, Chris Pepper  > wrote:
> 
>> With SALI our nodes connect to the imageserver and fetch scripts, but 
>> they do not actually install. It's a bit confusing -- the VGA console 
>> shows the correct hostname (c15), runs 99all.harmless_example_script, 
>> then says "No script defined, opening console", "write_variables", and 
>> "Starting console...".
> 
> You need to pass the SCRIPTNAME=whatever option to the kernel. See my 
> thread about tmpfs a few weeks ago - about halfway through is a detailed 
> description.

Tristam,

I'm pretty sure our older installation of 4.0.2 detected this 
automatically from cluster.xml, but I will try tomorrow.

Any ideas why parted is choking when I run the script manually?

Thanks!

Chris

-- 
Chris Pepper:
  

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Booting from SALI, but install script doesn't run, & fails when run manually

2010-08-16 Thread Tristam MacDonald 
On Aug 16, 2010, at 5:07 PM, Chris Pepper  wrote:

With SALI our nodes connect to the imageserver and fetch scripts, but they
do not actually install. It's a bit confusing -- the VGA console shows the
correct hostname (c15), runs 99all.harmless_example_script, then says "No
script defined, opening console", "write_variables", and "Starting
console...".


You need to pass the SCRIPTNAME=whatever option to the kernel. See my thread
about tmpfs a few weeks ago - about halfway through is a detailed
description.

--
Tristam MacDonald
http://swiftcoder.wordpress.com
Sent from my iPad
--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users