mariogolf wrote:
Fox_exe wrote:
What arhive you use?
Try original_v3.04.01-230.tar.gz (For restore original v3 firmware)
For clean debian use Kernel and rootfs v3.7z (use p7zip for extract)
* Sometime .zip arhives extract with errors (Because i use 7zip for create hem)
* Compare md5 sums:
dd if=rootfs.img bs=64k count=31247 | md5sum
dd if=/dev/md0 bs=64k count=31247 | md5sum
Its must be same (See .md5 file in arhive to check)
Hi Fox, thank for your help!
md5sum of my rootfs.img is
d41d8cd98f00b204e9800998ecf8427e
First of all: Is it right?
(for md0, now I power off the system, plug the disk, turn on and calculate the md5sum of md0)
Same md5sum of my rootfs.img for /dev/md0 .
Yesterday I downloaded
“debian_wheezy_omv_1.0.23.zip” (md5sum ac586235c7c9816703fc31acf983e516 ) with inside:
ceaf83959498c0bb34fffc8ab5db77bb kernel.img
192125cb31cb93f241f60be9887aa514 rootfs.img
“Autoinstall.zip” (md5sum 9cdbc542c33698101a5f4902162ec218) with inside:
6fdf983068dbed31b91a71b7b531ff7b config_md0.img
c706bcac3b4d16e4f6f1115d0feff5b3 config_md1.img
b242d9c71be821d53e63afe65bf6c95a install.sh
de70f9a259a8874ea5e931ff89e99fa3 run_me_after_reboot.sh
Is they the same of your original files?
Or - the same thing - where I find original/your md5sum ?
Because I didn’t find it in your goggle drive folder.
I installed p7zip but it is only for compress file. How can I decompress by cli ypur .zip files?
I suppose that google drive can “open” zip archives and text files, so it modify them. I think this is the cause of change of the install.sh line endings.
So, can you give me another link to files, not stored in google drive?
Thank you so much!
Mario
Sorry, for my long post: I want fix as soon as possible…