Hallo allerseits.
Ich habe die december iso mit sha256 überprüft und es passt, dann mit dd auf einen USB-Stick geschrieben.
root ist eine ext4-Partition
home eine btrfs-Partition (ja... ich weiß.. andere Diskussion)
Bei der Installation kommt es zu folgendem Fehler, dann bricht der Installer ab. Neuformatieren der root-Partition änderte nichts:
O: loading modules
O: Initialisation done
O: starting installation
O: starting load_config
O: load the configuration
O: starting prepareHD
O: prepare disk for the installation
O: starting copy2HD
O: copy the CD into the harddisk
E: Error copying iso to harddisk
O: siduction-installer ended abnormally
Irgendwie ist dieses log etwas mikrig. Schreibt der Installer noch andere logs? Wo finde ich diese?
Ich habe auch versucht den USB-Stick mit der Hash-Summe zu überprüfen, welche NICHT übereinstimmen. Allerdings frage ich mich ob das nicht daran liegt, dass md5sum die freien 7GB hinter dem iso mit in den Hash einbeziehen...? Was wäre der richtige Weg, um zu überprüfen, ob beim schreiben (dd) alles rund gelaufen ist?
I updated sidu-installer and cli-installer with aptitude.
When I run sudo cli-installer i get:
O: loading modules
O: Initialisation done
O: starting installation
==========================
siduction-installer started
==========================
O: starting load_config
O: load the configuration
O: starting prepareHD
O: prepare disk for the installation
==========================
Formatting /dev/sda9...
==========================
O: starting copy2HD
O: copy the CD into the harddisk
==========================
Copying files. This can take a while. Please be patient.
==========================
E: Error copying iso to harddisk
O: siduction-installer ended abnormally
==========================
install end, close the terminal
==========================
Some error occured. Looking at /tmp/error_log.F4TZZFoX might provide you with answers
siducer@siduction:~$ sudo cat /tmp/error_log.F4TZZFoX
Cannot stat file /proc/2159/fd/20: Stale NFS file handle
Cannot stat file /proc/2159/fd/21: Stale NFS file handle
Cannot stat file /proc/2176/fd/11: Stale NFS file handle
Cannot stat file /proc/2176/fd/12: Stale NFS file handle
Cannot stat file /proc/2814/fd/30: Stale NFS file handle
Cannot stat file /proc/2814/fd/90: Stale NFS file handle
Cannot stat file /proc/2814/fd/91: Stale NFS file handle
Cannot stat file /proc/3408/fd/15: Stale NFS file handle
Cannot stat file /proc/3408/fd/16: Stale NFS file handle
Cannot stat file /proc/3408/fd/17: Stale NFS file handle
Cannot stat file /proc/3408/fd/20: Stale NFS file handle
Cannot stat file /proc/3408/fd/21: Stale NFS file handle
Cannot stat file /proc/3408/fd/22: Stale NFS file handle
Any ideas?
EDIT:
Sorry for the edits/double posts, but I always think: Now if tried everything. Just after posting I get a new idea...
So, I found a way to compare the USB-Stick to the image:
$ cmp -n `stat -c '%s' ./siduction-13.2.1-december-gnome-amd64-201401272112.iso ` ./siduction-13.2.1-december-gnome-amd64-201401272112.iso /dev/sdb
And the result is:
./siduction-13.2.1-december-gnome-amd64-201401272112.iso /dev/sdb differ: byte 958103553, line 3422242
I'll try to rewrite the USB-Drive from my live siductive-session. Let's see.
Solved:
After rewriting the USB installation device it worked.
And i looove siduction!! it's great and working really well for my situation!
take away:
check the validity of the USB-device with:
$ cmp -n `stat -c '%s' ./siduction-13.2.1-december-gnome-amd64-201401272112.iso ` ./siduction-13.2.1-december-gnome-amd64-201401272112.iso /dev/sdb
Hi toggler,
glad you like it. Nice cmp line btw. :)
So, welcome to siduction. Do not forget to check the 'Upgrade Warnings' section of this forum before dist-upgrades, it's sid after all .
greetz
devil