Corrupt VNC files 2.4.1-beta001

You can report problems, make suggestions, about the new BETA versions in this forum. For stuff related to final releases, please post a message in other forums
Post Reply
Bockeman
Posts: 3
Joined: 15 Nov 2011, 21:00

Corrupt VNC files 2.4.1-beta001

Post by Bockeman » 15 Nov 2011, 21:16

Various files needed for VNC appear to be corrupt.
Tried several times, with 2.4.0 and 2.4.1-beta001.
Tried with and without docache.
512MB USB created using sysresccd-installer-1.1.2.exe

find /usr -type f -exec file {} \; | egrep ERROR
/usr/bin/vncconfig: ERROR: cannot read `/usr/bin/vncconfig' (Input/output error)
/usr/bin/vncpasswd: ERROR: cannot read `/usr/bin/vncpasswd' (Input/output error)
/usr/bin/vncserver: ERROR: cannot read `/usr/bin/vncserver' (Input/output error)
/usr/bin/whois: ERROR: cannot read `/usr/bin/whois' (Input/output error)
/usr/bin/wipe: ERROR: cannot read `/usr/bin/wipe' (Input/output error)
/usr/bin/wizard: ERROR: cannot read `/usr/bin/wizard' (Input/output error)
/usr/bin/wnck-urgency-monitor: ERROR: cannot read `/usr/bin/wnck-urgency-monitor' (Input/output error)
/usr/bin/wnckprop: ERROR: cannot read `/usr/bin/wnckprop' (Input/output error)
/usr/share/consolefonts/ERRORS: ASCII English text

Is this a problem with the iso, or a problem with the installer or USB memory stick?

gernot
Posts: 1130
Joined: 07 Apr 2010, 16:19

Re: Corrupt VNC files 2.4.1-beta001

Post by gernot » 16 Nov 2011, 05:27

Maybe your sysrcd.dat is corrupt.

I test with 2.4.0
you can this check with

md5sum /livemnt/boot/sysrcd.dat;cat /livemnt/boot/sysrcd.md5
ba12fcf22d6192973f0f173a9c078910 /livemnt/boot/sysrcd.dat
ba12fcf22d6192973f0f173a9c078910 sysrcd.dat

l /livemnt/boot/sysrcd.dat
8636 -rw-r--r-- 1 root root 298156032 Nov 16 06:19 /livemnt/boot/sysrcd.dat

Try to wait a minute after you wrote the USBstick or copy sysrcd.dat manual to the stick.
Checked you the md5sum from the downloaded iso?

Gernot

Bockeman
Posts: 3
Joined: 15 Nov 2011, 21:00

Re: Corrupt VNC files 2.4.1-beta001

Post by Bockeman » 16 Nov 2011, 22:35

Thanks for your response Gernot.

I checked the md5 sums for the iso images, and they all match.
I had not realised there was a separate, embedded checksum for the sysrc.dat. (Good to find).
However, the md5 sum for embedded sysrc.dat does not match, though the file size does.

I repeated the format and install to USB stick, waiting a further 5 minutes. Still no good.

I need to eliminate
a) Something wrong with the PC, Windows XP, USB connectivity, drivers.
b) Something wrong or incompatible with sysresccd-installer-1.1.2.exe (checksum is ok).
c) Something wrong with my 512MB USB stick. (I need to locate another of equivalent size).

gernot
Posts: 1130
Joined: 07 Apr 2010, 16:19

Re: Corrupt VNC files 2.4.1-beta001

Post by gernot » 17 Nov 2011, 15:44

I tested 2.4.0 with sysresccd-installer-1.1.2.exe.
All work well. Used you the "save remove" button from win?
I think its the stick or a bad antivirus.

Gernot

Bockeman
Posts: 3
Joined: 15 Nov 2011, 21:00

Re: Corrupt VNC files 2.4.1-beta001

Post by Bockeman » 18 Nov 2011, 18:14

I did not have a spare 512GB USB stick, and I was reluctant to give up on this particular stick which I have been using for many years, and on many machines, to hold the latest rescuecd.

After a series of experiments, I think I have found the cause of the problem.

When using sysresccd-installer-1.1.2.exe on a WinXP Pro machine to upgrade the version of rescuecd, it complains about not enough space. The obvious (to me) thing to do is to wipe the USB stick clean by formatting it (FAT16). It appears that this formatting process (regular [not quick] Win XP Pro format) discards any bad sector reallocation, thus any use thereafter is likely to fall foul of bad sectors.

It would be really good if sysresccd-installer-1.1.2.exe took care of this and deleted any previous similar files, or a least advised the user to delete the files (rather than format the USB stick).

Also, it would be really good if sysresccd-installer-1.1.2.exe could read back from the USB stick (not from any write cache) and checksummed the files written.

The solution in my case was to repair the USB stick on a linux machine using:
dosfsck -a -w -v /dev/sdc1
and delete all files before using sysresccd-installer-1.1.2.exe.

I now I have a working rescuecd and the checksum on sysrcd.dat matches.

I hope this proves useful to any other users who may reluctant to ditch a useable USB stick.

PS If anyone thinks I have misdiagnosed any of the above (or can confirm similar behaviour), please let us know.

gernot
Posts: 1130
Joined: 07 Apr 2010, 16:19

Re: Corrupt VNC files 2.4.1-beta001

Post by gernot » 19 Nov 2011, 08:44

The fsck you showed don't detect bad physical blocks. It corrects filesystem errors which occurre e.g. while disconnecting the device before all data written.
Windows should show a error message while writing such a bad filesystem.
Running badblocks for this device is a good idea.

Gernot

Post Reply