[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug 788062, os-prober, KVM Gaeste



Hallo,

unter Jessie wird nach einem Kernel-Update versucht, jede Partition zu
mounten. Das äußert sich durch Logeinträge wie:


Jul 17 07:51:05 vm1 kernel: [2277034.713375] XFS (vda2): Invalid
superblock magic number
Jul 17 07:51:05 vm1 kernel: [2277034.836134] FAT-fs (vda2): utf8 is not a
recommended IO charset for FAT filesystems, filesystem will be case
sensitive!
Jul 17 07:51:05 vm1 kernel: [2277034.836392] FAT-fs (vda2): bogus number
of reserved sectors
Jul 17 07:51:05 vm1 kernel: [2277034.836629] FAT-fs (vda2): Can't find a
valid FAT filesystem
Jul 17 07:51:05 vm1 kernel: [2277034.838443] FAT-fs (vda2): utf8 is not a
recommended IO charset for FAT filesystems, filesystem will be case
sensitive!
Jul 17 07:51:05 vm1 kernel: [2277034.838691] FAT-fs (vda2): bogus number
of reserved sectors
Jul 17 07:51:05 vm1 kernel: [2277034.838816] FAT-fs (vda2): Can't find a
valid FAT filesystem
Jul 17 07:51:05 vm1 kernel: [2277034.842796] ntfs: (device vda2):
read_ntfs_boot_sector(): Primary boot sector is invalid.
Jul 17 07:51:05 vm1 kernel: [2277034.843134] ntfs: (device vda2):
read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting
without trying to recover.
.....
Jul 17 07:51:05 vm1 kernel: [2277034.851199] >>>WARNING<<< Wrong ufstype
may corrupt your filesystem, default is ufstype=old
Jul 17 07:51:05 vm1 kernel: [2277034.854545] hfs: can't find a HFS
filesystem on dev vda2


Bug 788062 wurde in os-Prober 1.72 gefixt, Jessie verwendet noch 1.65.

Reicht es in /etc/default/grub

	GRUB_DISABLE_OS_PROBER=true

einzutragen? Muss man danach update-grub von Hand aufrufen?

Besteht ohne die Änderung die Gefahr, dass der Host KVM-Gast Partitionen
beschädigt?

Gruß,
Christian


Reply to: