search for: vdal

On Fri, May 5, 2017 at 2:38 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 3:15 ??, Gianluca Cecchi wrote: > > ... >> grub2-install /dev/vda >> ... >> Was this one of the command you already tried? >> > > Yes, I have tried that multiple times, both from Troubleshooting Mode > (booting using CentOS 7 Installation CD) and from within the

On 5/5/2017 8:34 ??, Gianluca Cecchi wrote: > Your /mnt/sysimage/boot is under tmpfs not real disk... Sorry, I am not an expert, but it does seem to NOT be under tmpfs: Filesystem Size Used Avail Use% Mounted on ... /dev/vdal 497M 192M 306M 39% /mnt/sysimage/boot ... Why do you say that the boot partition is under tmpfs? Nick

...rpm package already has created a "nut" user and therefore deletes the nutmon user but forgets to update upsmon.conf. In this case usbmon will fail silently to start up, without any clues why. Please add some code to usbmon to output a descriptive error message in this case. BR H?kon L?vdal

...pfs 1001M 8.3M 993M 1% /run tmpfs 1001M 0 1001M 0% /sys/fs/cgroup /dev/sr0 680M 680M 0 100% /run/install/repo tmpfs 1001M 300K 1001M 1% /tmp /dev/mapper/centos-root 18G 1.5G 16G 9% /mnt/sysimage /dev/vdal 497M 192M 306M 39% /mnt/sysimage/boot /tmpfs 1001M 0 1001M 0% /mnt/sysimage/dev/shm > If it is mounted on another mount point in your live env go and umount it > and run > mount /dev/vda1 /mnt/sysimage/boot Didn't need to. > then > ch...

On 5/5/2017 8:29 ??, Nikolaos Milas wrote: > I am very puzzled with "unknown filesystem". After more googling, I found this bug report with a very recent fix: https://bugzilla.redhat.com/show_bug.cgi?id=1399487 It seems to me that this may be relevant in our case. If so, may it be that this fix has not been rolled out to CentOS repos yet? What is your opinion and your

...pfs 1001M 8.3M 993M 1% /run tmpfs 1001M 0 1001M 0% /sys/fs/cgroup /dev/sr0 680M 680M 0 100% /run/install/repo tmpfs 1001M 300K 1001M 1% /tmp /dev/mapper/centos-root 18G 1.5G 16G 9% /mnt/sysimage /dev/vdal 497M 192M 306M 39% /mnt/sysimage/boot /tmpfs 1001M 0 1001M 0% /mnt/sysimage/dev/shm If it is mounted on another mount point in your live env go and umount it > and run > mount /dev/vda1 /mnt/sysimage/boot > Didn't need to. then > chroot...

On 5/5/2017 5:11 ??, Barry Brimer wrote: > Are the correct volumes referenced in your /etc/default/grub file? Thanks Barry for your feedback. Here is the output: http://iweb.noa.gr/files/centos7/scratchvm-data-20170505-01.png What can you tell from that? Cheers, Nick

...487 > > It seems to me that this may be relevant in our case. > > If so, may it be that this fix has not been rolled out to CentOS repos yet? > > What is your opinion and your advice/suggestion(s)? Yes, it's relevant, and the solution appears to be: xfs_admin -U restore /dev/vdal -- Marcelo "?No ser? acaso que esta vida moderna est? teniendo m?s de moderna que de vida?" (Mafalda)

On 5/5/2017 9:10 ??, Marcelo Roccasalva wrote: > xfs_admin -U restore /dev/vdal Bingo! I had to unmount the boot partition (being in Troubleshooting mode), run the above command, which provided a new UUID and at last the partition was recognized as xfs. (I forgot to copy the output to paste here.) I then mounted the boot partition again, chrooted, grub2-install'ed su...

.../vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x942d1f03 Device Boot Start End Blocks Id System dev/vdal * 2048 1026047 512000 83 Linux dev/vda2 * 1026048 41943039 20458496 8e Linux LVM Hmm, it seems that the boot flag should be removed from /dev/vda2 partition? (How we do that?) > BTW: are you using virt-manager to configure/run your VMs? Or direct virsh > commans or what? It&...