Hi,
letztes Problem, dass ich von der v6 in die v7 rüberschleppe und mit Hardware oder Linbo zu tun hat: Manchmal starten die Rechner nicht, normalerweise schon.
Jetzt hab ich mal die in „dmesg“ einen hinweis gefunden:
cloop: loading out-of-tree module taints kernel.
cloop: Initializing cloop v4.3
cloop: loaded (max 8 devices)
cloop: file xenialmate1812-2.cloop version 2, 120000 blocks of 131072 bytes, header first.
cloop: xenialmate1812-2.cloop: 120000 blocks, 131072 bytes/block, largest block is 131118 bytes.
EXT2-fs (cloop0): error: couldn't mount because of unsupported optional features (240)
cloop: unloaded.
urandom_read: 1 callbacks suppressed
random: dropbear: uninitialized urandom read (32 bytes read)
random: dropbear: uninitialized urandom read (32 bytes read)
random: dropbear: uninitialized urandom read (32 bytes read)
random: crng init done
random: 1 urandom warning(s) missed due to ratelimiting
EXT4-fs (sda1): re-mounted. Opts: data=ordered
EXT4-fs (sda1): re-mounted. Opts: data=ordered
EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: acl,user_xattr
EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: acl,user_xattr
cloop: Initializing cloop v4.3
cloop: loaded (max 8 devices)
cloop: file xenialmate1812-2.cloop version 2, 120000 blocks of 131072 bytes, header first.
cloop: xenialmate1812-2.cloop: 120000 blocks, 131072 bytes/block, largest block is 131118 bytes.
EXT4-fs (cloop0): mounted filesystem with ordered data mode. Opts: acl,user_xattr
cloop: unloaded.
Beim automatischen Start kam da: EXT2-fs (cloop0): error: couldn't mount because of unsupported optional features (240) cloop: unloaded.
während ich danach von hand den sync
angeworfen habe, da steht dann keine Fehlermeldung mehr drin.
Ist das ein timingproblem, das ich vllt. auffangen könnte?
VG, Tobias