Image Read error block 0 (0) ("Image Lesefeher Block 0

[Guest]

Hi,

i want to restore an image but i get the error "Image Read error block 0 (0)" What the matter? I renamed the image before and it have the parts 000,001,002, is this a problem?

Chris

[THoehne]

Hi!

I get the same error, when trying to restore an multi-volume image file. I seems to happen after the first file is completed.

I'm using Knoppix 3.6 and want to restore over the network.

I tried 2GB and 1.5GB files. I tried NTFS (first) and FAT32 as filesystem of the backup harddisk. I changed the Switch connecting the 2 computers. I tried to use the simulation (same error). I tried to start the daemon in the image directory. I read the FAQ and documentation over and over...

But it still doesn't work...

I'm getting kinda frustrated by now, since the image file, I want to restore was quite a lot of work...

I hope someone can help me!

Thorsten

[THoehne]

Forgot to say, I use 0.6.4.

I went further for testing:

chmodded the image files to 777, moved them to an ext2 partition, but nothing works.

I then created a new 4 GB image file on the ext2 partition, but when I'm trying to restore it, it fails due to "unkown compression level"!! :x

I used the standard gzip level, so what's the problem???

I'm really about to hurt someone, so could anyone please help me..!?


Update:

I tried the 0.6.2 version, but same error. I switched NICs and the daemon machine, but same error.

[fludo]

What could be this famous sector 0 ?
First sector of the Image file, or the MBR of the system ?

kinda sucks anyway....but I'm sure it will be fix soon.....

[fludo]

If I do this :

[/i]partimage restore /dev/hda1 /mnt/disk/image.000[/i]

I obtain the error sector 0 message.

Then I've teste this command :

[/i]partimage restore /dev/hda /mnt/disk/image.000[/i]

it works but the system (60 Go WinXP Fat32) is declared on hda4...
It doesn't start (maybe my partition isn't active)

What's wrong ?

[Viktor]

I could also not restore from splittet images.
I got also the error with the compression level when using gzip.
The only thing that seems to work ist to create one single image file with bzip2. But then you cannot use Samba to store the image on a remote (windows) mashine because the Samba implementation on Linux (at least in Kernel 2.4 [Knoppix 3.7]) does not support files bigger than 2GB.

After 3 days I finally have the image.
Now I'm trying to restore it. Hoping it will work :?

[Guest]

Hello ,

I think I ' ve got the same error:

"Image Lesefehler Block 0 (0)"
(German Knoppix, I don't know the Version, maybe 3.6 or 3.7 of Knoppix)
(I'm using different Knoppix versions form 3.4 to 3.7)

error at 60%, first part of the image I think (moved the second *.001 away for testing, no please enter path to *.001)

Image is from /dev/hda1 (NTFS )
write to IDE HD with USB2IDE controller (Cypress Semiconductor chipset, LSUSB 04b4:6830, cy7c68300a-56p D


Image is split into two pieces
compression Gzip ( I think i used default settings)

I'm using Partimage for a long time.
Never had any problems :(


Take a look at :

http://www.digitalissues.co.uk/html/os/ ... age.html#1

27. What are the known bugs for partimage 0.6.4?
* when using compression, the volumes sizes are a little bigger than the need
size (FIXED for gzip compression)(FIXED but files are far too small)

* some avail space problems

* if the link between server and a client fails for any reason, client
and/or server *may* die.

* partimage imginfo imagefile fails on wrong permissions but with wrong message
'can't find compression level' instead of 'permission denied'

* partimage doesn't rightly detect end of space so corrupts images maid with
compression. Image seems correct but restoring fails with 'invalid magic'.
This doesn't affect non compressed images nor multivolume images based on
size splitting.

* partimage can't restore MBR is image is bzip2 compressed

Maybe I (we) can save our image by extract it manually?

Block 0 = MBR?
If this is the reason , can i skip MBR extraction.?
I don't have any problems to write a new MBR ;)


Michael

[Frederic]

Hi,

I have had a problem with an usb-case for the hdd to, when the hdd is removed from the case and used as a normal ide drive it worked for me without the readerrors!

greetz
Frederic

[Michael]

Interesting Frederic !
What a pity I deleted the image file.
But copy the Image to another HDD under Windows OS was one of my testings.

I'm not sure. Some times I forgot to load USB2 driver (modprobe ehci-hcd, Knoppix) I 've got an error while backing up. Maybe there is a problem with usb1 driver loaded but an USB2 device attached to an USB2 controller under Knoppix.

Maybe I screw up Knoppix with wrong Boot options (cheat code ).

knoppix 2 USB2 dma1
Maybe typo :
space between Knoppix2 or Knoppix 2
knoppix 2 USB 2 or Knoppix 2 USB2


Maybe NTFS is experimental.

Maybe USB2 controller of my notebook is not 100% compatible with Knoppix or USB2IDE-Controller or .........

I don't know the reason of this error. :(
I'm using True Image at the moment for NTFS. (OEM Version from German magazine CT24/04)
But for ext2 and FAT32 I'm using partimage.



Michael

[Frederic]

Hi Michael,

I have done an (uncompressed) image of a 120gb partition via smbmount to a USB-2 Case with a 300gig maxtor in it (connected to a win2k pc). I have splittet the file every 2gig, as smbmount doesnt support files over 2gig.

Making the image give no errors or warnings. But as I must restore it, it breaks down with this read error block 0 (0) after different times. One time after 2% next time 8% best was 20%.

-I then tried to use the same case on the same pc but with Kanotix (Debian like Distro) instead of windows and using smbmount: didnt work.

-I tried it with an pci-usb2 hostadapter directly on the linux-pc but same failures.

-Have tried the internal USB1.1 adapter, but stopped it after i saw the ETA ;)

-Next step I connected the target disk directly to this pc. But this didnt work either.

-Finally I opened the USB-Case and connected the maxtor directly to the ide-bus together with the target disk. This finally works!

Target FS was ReiserFS (dont know version, but i can check if there is need for it)
On the Maxtor disk the FS was NTFS.

So my conclusion is, that there is something wrong with this usb-case. But in normal use it is not noticable.

Greetings
Frederic

[jurij]

http://www.device-image.de

Regards,
jurij