RE: Re: [Oscar-users] systemimager cannot recognize SATA HD

Wed, 07 Dec 2005 09:24:11 -0800

It does help. Thank you, Bernard.

Bernard Li <[EMAIL PROTECTED]> wrote:
Hi Andy:
 
Do you have pfilter package installed?  If so, then try disabling it by running "/etc/init.d/pfilter stop" prior to imaging - see if that helps.
 
Cheers,
 
Bernard

From: ANDY SIU [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 10:18
To: Bernard Li
Subject: RE: Re: [Oscar-users] systemimager cannot recognize SATA HD

Hi Bernard,
 
We are now one step further. The sata disk can be recognized as SCSI 80G. (I saw it from the screen, though the messages jump off the screen quickly). Thanks!
 < /DIV>
Now I have another problem. Let me tell you what did I do.
 
1. For the old installed headnode (FC3) that we were talking last week, since I had already updated the kernel to 2.6.12, which should contain the sata driver that I need, I tried to installed Oscar-4.2 with SystemImager-3.5.4 RPMs, and also added the line to hardware.lst after the client image was built. When I booted the compute node, it did see the disk (DISK=1) and I could see the size of my disk is 80G. However, error happened during deploy.
 
......(much much outputs)
......
/lib/modules/2.6.12-prep/kernel/drivers/mtd/maps/scx200_docflash.ko
 
------ ( It stopped at here for long time, then continued to give the following) --------
 
rsync: read error: connection refused (111)
rsync error: error in rsync protocol data stream (code 12) at io.c (584)
rsync: connection unexpectedly closed (961310 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c (434)
killing off running processes.

2. Then I reinstalled the headnode with FC4 (without any updates) and Oscar-4.2.1beta. Same procedures as above. Boot up the compute node.  Deploy start. However, the similar error happened. Each time I tried to deploy the compute node, it stopped at different point. "/lib/modules/........................."
Then error due to rsync happened.
 
Thank you very much
Andy

Bernard Li <[EMAIL PROTECTED]>< /I> wrote:
Hi Andy:
 
Okay try this tarball:
 
 
This is OSCAR 4.2.1 beta 2 with SystemImager 3.5.4 (from SVN, non-released) integrated already, you still need to do this extra step:
 
9) After you have created the image and before you deploy it, add the following to:
 
/var/lib/systemimager/images/<imagename>/etc/systemconfig/hardware.lst:
 
8086   27c0   scsi   ata_piix
 
(if the file does n ot exist, create it)
 
Hopefully the tarball works (I haven't tested my integration, but it should).
 
Cheers,
 
Bernard

From: ANDY SIU [mailto:[EMAIL PROTECTED]
Sent: Friday, December 02, 2005 10:31
To: Bernard Li
Subject: RE: Re: [Oscar-users] systemimager cannot recognize SATA HD

Hi Bernard,
 
The problem is most likely due to FC3. It doesn't recognize my disk, and FC4 does. So now, I should install FC4 to the headnode. Where can I get oscar-4.2.1? Should I still follow the procedure in your last mail to reinstall the systemimager after I get everything done?
Thank you very much!
Andy

Bernard Li <[EMAIL PROTECTED]> wrote:
Hi Andy:
 
Okay the new SystemImager RPMs are ready, here's what you need to do...
 
I want to make sure your system is clean - while you can probably just upgrade the SystemImager RPMs, it is probably best that you do a fresh installation of the OS + OSCAR just so we know what's going on.
 
Here're the steps:
 
1) Re-install OS
2) Grab OSCAR tarball
3) Untar
4) Do ./configure && make install
5) cd /opt/oscar/packages/sis/distro/common-rpms
6) Delete all systemimager-3.5.3 RPMs
7) Copy the SystemImager 3.5.4 RPMs found here to that directory:
 
 
You don't need to get the src.rpm, just grab the RPMs. (Note this is an _unreleased_ SystemImager version taken from SVN trunk)
 
8) Do a normal OSCAR installation
9) After you have create d the image and before you deploy it, add the following to:
 
/var/lib/systemimager/images/<imagename>/etc/systemconfig/hardware.lst:
 
8086   27c0   scsi   ata_piix
 
(if the file does not exist, create it)
 
Boot up your node and i t should hopefully recognize your SATA adapter.
 
However, before you do all this, remember to double check to make sure that Fedora Core 3 actually works with your SATA adapter, if it doesn't, you may want to try Fedora Core 4.  OSCAR 4.2 does not support Fedora Core 4 but OSCAR 4.2.1 does, I can send you a link to the beta tarball if you need that.
 
Hope this helps, please let me know how it goes.
Cheers,
 
Bernard

From: ANDY SIU [mailto:[EMAIL PROTECTED]
Sent: Thu 01/12/2005 13:23
To: Bernard Li
Subject: RE: Re: [Oscar-users] systemimager cannot recognize SATA HD

Hi Bernard,
 
Just want to make sure you are looking at the correct information, so I have removed all RE: messages in this mail. The outputs of "lsmod" and "cat /proc/pci" on one of my compute node are in the attachement files.
 
Of course, I would like to test your new RPMs for systemimager definitely. I have played around with my monster almos t two weeks already.......
 
Thank you very much
Andy
 

 



Reply via email to