errors are displayed over the menu
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
#65 errors are displayed over the menu
When I start clonezilla I see error messages, which just appear over the menu. I just reproduced:
At the Start Clonezilla menu:
Start_Clonezilla Start Clonezilla
Enter_shell Enter command line prompt
<Ok> <Cancel>
The following error messages start to appear, and the first appears right over the "Start_Clonezilla Start Clonezilla" menu option, the next ones appear on the left:
[ 52.330373] tda 10048_firmware_upload: Upload failed (file not found?)
[ 53.388299] tda 18271_write_regs: ERROR: i2c_transfer returned: -5
[ 53.448745] tda 18271_write_regs: ERROR: i2c_transfer returned: -5
[ 54.747393] tda 18271_write_regs: ERROR: i2c_transfer returned: -5
When I go up and down in the menu the option appears again over the error.
The backups are fine.
The errors are probably no problem and may come from my TV Tuner card (the first one at least), but they shouldn't be displayed over the menu.
How about Clonezilla live 20100330-karmic?
Steven.
I tried clonezilla-live-20100403-lucid.iso 2 times and the problem was still
there one time.
Should I still also test Clonezilla live 20100330-karmic?
I believe there is a hardware on your machine need firmware, however, it can not be loaded. Looks like the firmware is not found. Do you know if your hardware "tda" is supported by Linux?
The bug report is not about the error messages, but about them appearing over the menu.
The hardware is part of the Hauppauge HVR1100 (HVR1120) radio/tv tuner card is supported in linux, but you need to extract the firmware from the windows driver, so this can probably not be included in a linux distribution.
I see the same errors in dmesg if the firmware is not in place.
"about them appearing over the menu" -> Could you take a photo and show us? Thanks.
Steven.
error over menu
error over menu - after cursor moved
error over menu - after cursor moved again
I added 3 files, these are screenshots taken over a vnc session (intel vpro has a vnc server built in). They are in 1080p format. because the monitor of the other pc was smaller I had to take screenshots of parts and puzzle them together.
I actually came to report this same issue as a bug.
The problem is that the ncurses menus and status dialogs get badly corrupted by kernel/dmseg errors being printed to tty1.
This is extremely annoying when attempting to run ddrescue on a drive with damaged sectors, and makes the status window completely unusable.
(I'll try to upload a photograph of this after I have the data off of the drive I'm dealing with.)
I'm not 100% certain my syntax is correct, but running clonezilla from tty2 and adding
"chvt 2"
to the initial init scripts (just before starting clonezilla) should switch the display to tty2, and avoid the display corruption completely.
Alternately, the menus and status screens could be completely redrawn every refresh, but that would prevent savvy users from being able to easily see the dmesg output.
Thanks for reporting this.
Do you have any idea how to modify /etc/syslog.conf to avoid this?
I just can not find how...
Steven.
As far as I am aware, syslog/dmesg/kernel panic/"everything else low level will print to tty1 by default.
You would have to edit more than just syslog.conf to avoid the messages, and the first time an in-kernel ide driver throws a read error you'll have the corruption issue again anyway.
There may be something in the kernel config that can be changed (hopefully without recompiling) but I'm not aware of it, and a quick google didn't turn up anything either...
Eldorel
I dig more, however, I still could not find how to make it...
If anyone knows, please let us know.
Steven.
i'm also experiencing this bug with latest clonezilla installed from tuxboot.. it is especially bad because the read errors i'm getting (disk has some bad sectors) are not only displayed over the menu/progress on tty1--corrupting it (screenshot attached of partclone progress)--but they are displayed on whichever tty is active! that means if i switch to tty2 to try and do something, all of the sector read errors are now piped to tty2, rendering it unusable. the errors will be piped to whatever tty i decide to try.
This looks like hard drive I/O errors. Therefore you'd better to backup your data asap.
Steven.
well yes that's why i was running CloneZilla silly :3
No, I meant to use other tools to do that. Like dd_rescue or something similar. Clonezilla is OK for working hard drive, not for that has bad sectors.
Steven.
BTW it was cloned successfully after many hours and i was able to get my system running again!
thanks i'll keep that in mind
Dd-rescue is included in clonezilla, under the expert options.
The only reason not to use clonezilla to recover data from a drive with bad sectors is the way it screws up its readout.
Which, incidentally, is exactly what this bug is about.
Steven, just an fyi: The fix for this is probably to add
dmesg -n 1
to an init script executed as root.
from the dmesg man page
-n, --console-level level
Set the level at which printing of messages is done to the con-
sole. The level is a level number or abbreviation of the level
name. For all supported levels see the --help output.
For example, -n 1 or -n alert prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so sys- logd(8) can still be used to control exactly where kernel mes- sages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer.@Greg,
Thanks. Yes, "dmesg -n 1" should solve this issue, and this should be the default mode for Clonezilla live. We will add this in the future release.
Steven.