Hi Andrea,
You asked if I have tried most recent version, no I have not!
Version 3.6.3 was the only stable version I found.
Do you recommend any specific version of systemimager for my issue? And
where would I get it from?
Thx
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Zubair, Mohammad
Sent: Thursday, January 04, 2007 4:39 PM
To: [email protected]
Subject: Re: [Sisuite-users] Any resolution to "could not stat
device/dev/sda" error?
Bear w/ me as I am a newbie :-(
Our HP BL35P blades are equipped w/ SAS controllers.
"lsmod" command on failed client shows:
Module Size Used by
sd_mod 15440 - - Live 0xf8836000
scsi_mod 93796 - - Live 0xf888f000
Does that mean that my disk module got loaded?
Please note, I am using pxe (no floppy/cd to boot from). Which file
should I look into for a kernel module for my hardware?
Also, I am not sure if I follow INSMOD_COMMAND portion of your response.
Would you please elaborate on this as I am not 100% familiar w/ either
Linux or Systemimager.
My /proc/diskstats has some entries in it not nothing related to sda.
/proc/partions is empty.
Thanks for looking into it.
=======================================================================
An 'lsmod' on the client you're trying to image (within BOEL) should
list the module \
for the SCSI/SATA controller if it's recognized.
Check the disk controller in the HP machine you are trying to image. If
the \
Autoinstall CD does not contain a kernel module for the actual hardware
present in \
the machine, disk enumeration won't happen as expected by the Master
script. The \
device identified therein will not be recognized, and cannot be
formatted.
If you have built the client image on one of these blades, be sure that
the modules \
are loaded. You may need to copy the module into the 'my_modules'
directory in the \
initd_template directory and add a line in INSMOD_COMMANDS.
Checking /proc/diskstats and /proc/partitions should yield some
additional clues as \
well. If the device is recognized, it will be present here as sda.
If this is the case, check the .master script and autoinstall.conf and
be sure that \
it is referencing the correct device.
I may not be entirely correct, but I hope this helps.
_____________________________________________
From: Zubair, Mohammad
Sent: Thursday, January 04, 2007 9:48 AM
To: '[email protected]'
Subject: Any resolution to "could not stat device /dev/sda" error?
Hi I have posted this a long time ago but have not heard back if there
is a resolution to this.
To recap, I am running system imager version 3.6.3 on my server as well
as client. My server and my client both are HP blade BL35P and I am
trying to deploy a RedHat ES4.0 image. Image capture process gets
completed just fine but when I am ready to deploy this image to my
client (again an hp blade bl35p), it fails w/ the following message:
NO DISK DEVICE FILES WERE FOUND. THIS USUALLY MEANS THE KERNEL DID NO
RECOGNIZE ANY OF THE ATTACHED DISKS.
<snip>
Partitioning /dev/sda...
Old partition table for /dev/sda:
Error: could not stat device /dev/sda - no such file or directory.
Parted -s -- /dev/sda mklabel msdos || shellout
Error: could not stat device /dev/sda - no such file or directory.
Killing off running processes.
Please help, I have about 300 systems to build.
Thx
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
