Products > Test Equipment
Agilent E7495 linux root account
walter2:
I recently got 2 E7495A, both booted and worked. Working with a fellow conspirator here in kelowna, we took his known good PCMCIA/Flash update card with 6.25, and did the flash upgrade to the best unit with 6.24 working on it.
the update never completes, it runs for a very long time, gets to anywhere from 70-90% of the flash update, and never goes further. when we transferred the flash card right to the machine (rather than via the pcmcia adaptor), it runs faster, and doesn't complete, but also throws up a strange message "inflate returns -3" repeatedly, then a blosk fo data too fast to read, then stalls again. we tried the normal on-screen update, and the hidden lower right button full refresh, but fail at the end.
we have tried all variants of the process, but cannot get to an updated machine. this appears to indicate that the internal flash on the motherboard is bad at some location, and doesn't permit a valid update. is this right? if so, how can I fix the flash on the motherboard.?? does anybody have ANY internal documentation for this unit? I see nothing at hp/agilent/keysite.
you can email me directly at walter2 -at- sphere.bc.ca
I would really like to get this unit working, and am incredibly sorry I tried this update. any help appreciated.
regards,
walter
technogeeky:
--- Quote from: walter2 on April 15, 2018, 09:54:39 pm ---I recently got 2 E7495A, both booted and worked. Working with a fellow conspirator here in kelowna, we took his known good PCMCIA/Flash update card with 6.25, and did the flash upgrade to the best unit with 6.24 working on it.
the update never completes, it runs for a very long time, gets to anywhere from 70-90% of the flash update, and never goes further. when we transferred the flash card right to the machine (rather than via the pcmcia adaptor), it runs faster, and doesn't complete, but also throws up a strange message "inflate returns -3" repeatedly, then a blosk fo data too fast to read, then stalls again. we tried the normal on-screen update, and the hidden lower right button full refresh, but fail at the end.
we have tried all variants of the process, but cannot get to an updated machine. this appears to indicate that the internal flash on the motherboard is bad at some location, and doesn't permit a valid update. is this right? if so, how can I fix the flash on the motherboard.?? does anybody have ANY internal documentation for this unit? I see nothing at hp/agilent/keysite.
you can email me directly at walter2 -at- sphere.bc.ca
I would really like to get this unit working, and am incredibly sorry I tried this update. any help appreciated.
regards,
walter
--- End quote ---
walter:
From here, inflate() returning -3 is evidently the error Z_DATA_ERROR. This error arises during extraction from a compressed file (hence inflate). Z_DATA_ERROR implies that the source data is missing, invalid, or corrupted. I would get a new or different CF card, or a different CF card to flash adapter.
I know the update process is run during boot (it checks to see if a card with an update is present, and asks you if you want to try and install it). Since this is just some command, it should be possible to run this command from the local memory inside the machine. You can telnet in, use FTP to upload the update file/images, and then run the update manually.
ogden:
--- Quote from: technogeeky on April 15, 2018, 10:59:42 pm ---From here, inflate() returning -3 is evidently the error Z_DATA_ERROR. This error arises during extraction from a compressed file (hence inflate). Z_DATA_ERROR implies that the source data is missing, invalid, or corrupted. I would get a new or different CF card, or a different CF card to flash adapter.
--- End quote ---
Also it is worth checking MD5 checksum of the file(s). It could be so that during download file somehow became corrupted.
walter2:
For "greater clarity" here, I was able to use that SAME update flash card to successfully update my second unit, so there is no question that it works. we also confirmed it was good on three other machines.
I would have thought the messages about inflating were just as others suggested, that it is an update source problem after decompression, but it is certain that is not the issue, the problem is at the destination, the internal flash on the motherboard. I believe this message indicates that a checksum failed after attempted writing, but am not positive. more disturbing is that I have zero info on the mother board. the issue always arises towards the end of the process, which points to a bad or marginal area at the end of the local flash storage.
anyone with motherboard info, and how to fix the on-board flash would be greatly appreciated. there is no local flash card or other easily replaceable memory on the card, other than what appears to be a boot ROM.
regards,
walter
TheSteve:
Is it possible the problem unit had a bunch of user data stored on the internal memory before the upgrade was started so it is running out of space?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version