Re: write error on 1.8.1
Niko <[email protected]> Thu, 16 Jan 2014 12:41:47 +1030
| Newsgroups | gmane.comp.security.firewalls.m0n0wall |
|---|---|
| Message-ID | <[email protected]> |
Well, I tested another flash drive (should mention it's USB not CF) and the same error in phydiskwrite, and also if i try to boot (correcting myself here, it is a static \ with blinking cursor _ underneath). I can't quite understand what is the difference between 1.34 and 1.8.1 in terms of both of those are signed, how is it so that one can succeed writing without error? Platform is Intel Atom board, Intel DN2800MT which has worked perfectly with all betas. I'm on Windows so I used WinRAR to extract the image.bin from from generic-pc-1.8.1.img. I then wrote this with phydiskwrite without error to USB and successfully booted. I've repeated this several times to make sure it wasn't an anomaly. I can't quite see what is unique to my configuration to cause this, and would expect other users to run into this as well? On 16/01/2014 3:04 AM, Manuel Kasper wrote: > You can also decompress the .img using gunzip (it will say something about trailing garbage ignored, which is the digital signature), and then write the uncompressed file with physdiskwrite. > > What platform are you using the CF card with? > > > On 15.01.2014, at 16:56, Niko <[email protected]> wrote: > >> Hi Manuel, >> >> Thanks for the reply. >> >> I tried booting and it's just at a flashing '\'. If it helps, the duration of physdiskwrite's writing process for the final image was only about half that of the time taken to write the beta. It seems like there really is a write error? >> >> >> I tried 1.34 and it seems okay? >> >> M:\mono>physdiskwrite.exe -u generic-pc-1.34.img >> ..... >> About to overwrite the contents of disk 3 with new data. Proceed? (y/n) y >> Found signed compressed image file >> 10485760/10485760 bytes written in total >> >> >> >> >> On 16/01/2014 2:07 AM, Manuel Kasper wrote: >>> You can ignore this. It's a physdiskwrite bug triggered by the digital signature (which the beta images do not have) - the image will work anyway. >>> >>> - Manuel >>> >>> >>> On 15.01.2014, at 16:23, Niko <[email protected]> wrote: >>> >>>> Firstly thanks to all for the work on 1.8.1. It is great to see a new release with such great improvements. >>>> >>>> I'm having an issue writing generic-pc-1.8.1.img to a flash drive and I feel like a beginner. It fails at the same point each time after the same amount of bytes written. I do not have a spare flash drive handy to test which is my downfall, so i feel silly asking so soon. However indications below appear it might not be the flash drive. >>>> >>>> >>>> I've checksummed the downloaded image (e18e752577e24c7a61df525e4d962b4a) and verified it against the MD5 on the download page. I've used diskpart to clean the drive and still can't get it to place nicely. >>>> >>>> What's the diagnosis if I can write the beta but I get a write error using the final image? >>>> >>>> >>>> >>>> M:\mono>physdiskwrite.exe -u generic-pc-1.8.1.img >>>> ..... >>>> About to overwrite the contents of disk 3 with new data. Proceed? (y/n) y >>>> Found signed compressed image file >>>> 14516224 bytes writtenWrite error after 14516224 bytes (2182). >>>> >>>> >>>> Inside the Mono folder above where phydiskwrite is, i've a few beta images. I can select any of them and they write to completion, eg. the last beta: >>>> >>>> M:\mono>physdiskwrite.exe -u generic-pc-1.8.1b561.img >>>> ..... >>>> About to overwrite the contents of disk 3 with new data. Proceed? (y/n) y >>>> Found compressed image file >>>> 26972160/26972160 bytes written in total >>>> >>>> >>>> Thanks for any pointers! >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > >