[ previous ] [ next ] [ threads ]
 
 From:  Hilton Travis <Hilton at QuarkAV dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  RE: [m0n0wall] generic-pc-pb27r630.img corrupt?
 Date:  Wed, 11 Feb 2004 07:48:24 +1000
Hi taharka,

On Wed, 2004-02-11 at 00:33, taharka wrote:
> > -----Original Message-----
> > From: Hilton Travis [mailto:Hilton at QuarkAV dot com]
> >
> > Hi Joachim,
> >
> > On Tue, 2004-02-10 at 20:05, Christiaens Joachim wrote:
> > > > -----Original Message-----
> > > > From: Hilton Travis [mailto:Hilton at QuarkAV dot com]
> > > >
> > > > Hi All,
> > > >
> > > > This is the second time I have seen this issue - the first was when
> > > > trying to update to the pb26r610 image (the installed image (pb25r595)
> > > > was an ftp-upload only, this was the first image that allowed for http
> > > > firmware uploads).
> > > >
> > > > What happens is that I download the image then try to upload
> > > > it and get
> > > > the following error:
> > > >
> > > > The following input errors were detected:
> > > >
> > > >       * The image file is corrupt.
> > > >
> > > > Of course, I cannot proceed from here.
> > > >
> > > > When this first happened, I followed Manuel's advice and removed 
> > > > the HDD from the system and did a manual update - re-imaging the 
> > > > hard drive.  However, I don't want to have to do this with every 
> > > > new m0n0wall version - and it seems that is what's happening 
> > > > (for some reason).
> > > >
> > > > So, anyone else seen this issue, and does anyone have a suggestion 
> > > > for what I can look at to see what's causing the issue?
> > > >
> > > > As before, I have run "gunzip -S .img generic-pc-pb2xrxyz.img" on 
> > > > the file and it unzips without error.  Same result last time, too.
> > > >
> > > > The image files were downloaded on an Arch Linux system running 
> > > > Mozilla Firebird 0.7 and were attempted to be uploaded on the same 
> > > > system.  Trying the same thing on a Windows XP Pro system with 
> > > > MSIE - downloading and uploading - results in the exact same error.
> > > >
> > >
> > > Just a guess, as many people seem to be using old HDD's for their m0n0:
> > > any chance of a damaged hdd or maybe geometry issues?
> >
> > That's quite possible.  I'll replace the HDD with another - this is a
> > 400-odd MB drive, and I'll try a later 2.5 GB drive to see if I see the
> > same issues - I'll even go back to the older image and try it all again.
> >
> > I'll keep you posted.
> Is your m0n0wall's box BIOS capable of booting from a CDROM? If so, you
> could install one of the newer CDROM drives (one that will read CD-RWs) &
> use the m0n0wall CD version. A new version of m0n0wall becomes available &
> you can eject the m0n0wall CD-RW (while the system is live), erase the
> m0n0wall CD-RW, burn the new version, stick it back in the m0n0wall box &
> reboot it. The m0n0wall system is only down for the time it takes it to
> reboot. Never had an upgrade problem here using this procedure.

I *could* do this, but I'm not normally someone known to run away from a
problem.  I'd rather sort the problem out.

-- 

Regards,

Hilton Travis                   Phone: +61-(0)7-3343-3889
Manager, Quark AudioVisual      Phone: +61-(0)419-792-394
         Quark Computers         http://www.QuarkAV.com/
(Brisbane, Australia)            http://www.QuarkAV.net/

Open Source Projects:		http://www.ares-desktop.org/
				http://www.mamboband.org/

Non Linear Video Editing Solutions & Digital Audio Workstations
 Network Administration, SmoothWall Firewalls, NOD32 AntiVirus
  Conference and Seminar AudioVisual Production and Recording

War doesn't determine who is right. War determines who is left.