Imaging Size
sala...@lycoming.edu
I am using zen 4 to pull a computer lab image up to the server. We used
to have the 4 GB image limit size problem until we updated the server
files and client to 4.9. We fixed that, however, I have one image that
reverts back to the same problem every time I collect it. It either
reports the same size (1,411,304 or something close to that) and the
image is not valid or it changes at some point later on to that size. I
found out that if you access the file server space with a 4.83 client it
can corrupt the files. So, I thought that was the problem. We are not
browsing that file server space any more with a 4.83 client, but the
problem still persists with this one image. I have serveral images on
this server and all of them are fine with the exception of this one. I
have even tried collecting the image using another computer in this
computer lab, but that does the same thing. I do have one image on that
server that is collected from a computer that has the 4.83 client, but I
cannot see why that would cause a problem. Could there be something on
these machines in this lab causing the problem. Any help would be
appreciated!
Thanks, Diane
Jared L Jennings
to pull the image from?(before you collect the image)
--
Jared L Jennings, CNE
Novell Support Forums SysOp.
http://support.novell.com/forums/faq_nntp.html
Perusing with XanaNews Reader 1.15.8.5
Geek by Nature, NetWare by Choice.
sala...@lycoming.edu
and it came up clean. I also built a new image from scratch for the
computers in this lab (from format to installing all programs) and my
image still is indicating a size of 4,194,304. There is actually nothing
in the image file on the server. When you try to copy it the file cannot
be found. I have four other computer labs that I image and they are
fine. It is just the image for this lab. Could there possibly be a
conflict with hardware?
Thanks, Diane
> Have you tried running chkdsk (spelling) on this PC that you are trying
> to pull the image from?(before you collect the image)4,194,304
Jared L Jennings
And are you using the same CD as the other PC's that work?
I suppose it could be hardware, but would think it must be with the
network, either NIC or wiring or switch.
salamone@lycoming..edu
I am sorry it took me so long to respond back to you. I found out that I
can take an image from another computer lab that is under 4 GBs in size
and image the lab I am trying to with it. So, I just updated that image
to include the programs it needed. I collected the image, but it failed
to collect properly. As soon as it gets past 4 GB it has a problem. The
image size is a definate issue here. We have everything updated to
handle the 4 GB limitation. We even double checked. Any thoughts?
Thanks, Diane
Jared L Jennings
> I am sorry it took me so long to respond back to you. I found out
> that I can take an image from another computer lab that is under 4
> GBs in size and image the lab I am trying to with it. So, I just
> updated that image to include the programs it needed. I collected
> the image, but it failed to collect properly. As soon as it gets
> past 4 GB it has a problem. The image size is a definate issue here.
> We have everything updated to handle the 4 GB limitation. We even
> double checked. Any thoughts?
What patch level, someone else in the backrooom is reporting something
like this.
--
Jared L Jennings, CNE
Novell Support Forums SysOp.
http://support.novell.com/forums/faq_nntp.html
Perusing with XanaNews Reader 1.16.1.3
sala...@lycoming.edu
>
> > I am sorry it took me so long to respond back to you. I found out
> > that I can take an image from another computer lab that is under 4
> > GBs in size and image the lab I am trying to with it. So, I just
> > updated that image to include the programs it needed. I collected
> > the image, but it failed to collect properly. As soon as it gets
> > past 4 GB it has a problem. The image size is a definate issue here.
> > We have everything updated to handle the 4 GB limitation. We even
> > double checked. Any thoughts?
>
> What patch level, someone else in the backrooom is reporting something
> like this.
>
>
Jared L Jennings
sala...@lycoming.edu
the files as indicated in TID 10078353. I did find another update
(zfd4sp1bagentu3.exe, zfd4sp1bservru3.exe)in my research and I will check
with our network administrator to see if these patches were installed.
Any additional thoughts would be appreciated.
Thanks, Diane
Jared L Jennings
> Is this a separate patch that we need to apply. We already have
> updated the files as indicated in TID 10078353. I did find another
> update (zfd4sp1bagentu3.exe, zfd4sp1bservru3.exe)in my research and I
> will check with our network administrator to see if these patches
> were installed.
Yes, sp1b is the same as 4.0.1.
P2 has a lot of fixes in it. I wouldn't do the U3 patch though since
you are having imaging issues.
sala...@lycoming.edu
Ok, we will not apply the U3 patch. We did update the files on the
server as indicted in TID 10078353. This TID said that the fix to the
4GB image limitation was to replace the following image files with more
recent files dated 1/16/03 or newer: bootcd.iso, bootflop.zim, root.gz,
root2.tgz, root4.tgz, etc. These files all have the more recent dates on
them. The new dates are as follows:
bootcd.iso 9/3/03
bootflop.zim 9/3/03
root.gz 9/3/03
root2.tgz 9/3/03
root4.tgz 9/3/03
etc ??
Is this what you mean by applying the P2 patch? If so, we have done this
and we are still experiencing the 4GB limitation. What is meant by etc.
in this TID?
Thanks, Diane