berryParticipant29 March 2013 at 10:22Post count: 3
Anybody tested the new Firmware from Experte 4?
It looks same 2.10.
There are two firmware included .fschneidParticipant29 March 2013 at 11:42Post count: 2
I can’t find an HS_4.0.TGZ File in the firmare directory anymore. It is not possible to untar the new INTRD File? Any Help?gediaParticipant29 March 2013 at 12:56Post count: 6
You can unzip it with 7-zip under Windows. I’ll update this thread if I get it to work…
P.S. hstrans is gone.fschneidParticipant29 March 2013 at 13:02Post count: 2
yes, unzip was possible but not more like untar, becaust it seems to be a initrd ramdisk file now.
I can extract all files with the following command. It is not necessary to unzip the file before!
zcat INITRD | cpio -iv
But the Homeserver will not start, becaus of missing libraries?
/hs/bin/hs_main: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directorygediaParticipant29 March 2013 at 15:48Post count: 6
You’re most probably missing some dependencies. I ran some preliminary tests with a clean debian 6.0.7 i386 installation and only minimal changes seem to be needed:
1) Install debian squeeze using the netinstall ISO on your VM. I went with Roel’s suggestion of using two disks: /dev/vda for the OS installation, /dev/vdb for use by hs_main
2) You need a valid MAC for this to work. hs_main seems to be OK with ifconfig reporting the MAC address in lowercase now
3) Copy the following directories from the firmware image to the root of your filesystem: /hs and /scripts
4) run: “apt-get install python-imaging”
5) Provided your MAC is valid, running /scripts/starths.sh will go through the initialization procedure and then start hs_main
6) Symlinking doesn’t really work right for block devices, use a hex editor to change all instances of /dev/hdb or /dev/hdc in the hs_main binary to whatever you’re using. If I’m not mistaken, it was Borgal who first suggested doing this, so the credit goes to him (or her).
P.S. I used the image for HS3, not HS4.damiandmParticipant29 March 2013 at 16:41Post count: 5
Can someone please provide a 2.10 image for VM to download?
THXCharlyParticipant8 April 2013 at 22:03Post count: 2
Can anyone give an instruction, how to create an INITRD file after modifying the starths.sh without having a linux system? I want to change first my backup-system to 4.0 and I don’t want to use VM.
Charlyhs815Participant16 April 2013 at 11:11Post count: 1
i figured out, that with new kernel you dont nee dhc or hdb anymore..
it just works with sda…
thats what i did:
i updated my old HS3 (on kvm) to the new 4.0
the major change was the harddisk is now sda and no longer hdc
i use a suse11.3 64bit (know its not the newest).
created 4 partitions:
/dev/sda1 1 132 1060258+ 82 Linux swap / Solaris
/dev/sda2 133 1177 8393962+ 83 Linux
/dev/sda3 1178 1309 1060290 6 FAT16
/dev/sda4 1310 1441 1060290 6 FAT16
then i extracted the firmware file from experte 4 (zip) for HS3
(because i works with my old mac-address)
therefor i unpacked the inird with
gzip -dc ../INITRD | cpio -id
to a dir..
then i copied the hs dir to the rootpath of my linux
and when i started i needed to install some python-packages..
but first i copied all the python-dirs to my linux /usr/lib/python
there is a PIL dir which is needed..
then i can start it. With a script.
hwclock –hctosys –utc
setserial /dev/ttyS0 autoconfig
setserial /dev/ttyS1 autoconfig
#only needed for serial transfer 1 time:
#killall -9 python
The communication for the first time I did with a nullmodem cable to windows8
The serialport on the new hs was ttys0…. It also changed…
Now it works fine…
on original HS4-hardware there are
all dos formatted, but the do something strange with turbodisk..
and then start it with loadlin to a ram -image. with busybox