On 5/5/2017 2:22 πμ, Marcelo Roccasalva wrote:
when you boot via supergrub2, you get this kernel version (uname -r)?
every kernel has it own initramfs where some binaries, libraries,
modules and configuration files get copied from the running VM, so you
need to boot from a newly created initramf
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
On Fri, May 5, 2017 at 11:54 AM, Nikolaos Milas wrote:
> 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/c
On 5/5/2017 1:19 μμ, Gianluca Cecchi wrote:
Could you verify, if /dev/sda is your boot disk, with the command
fdisk -l /dev/sda
?
It's /dev/vda in my case:
# fdisk -l /dev/vda
Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (log
On 5/5/2017 1:42 μμ, Nikolaos Milas wrote:
Hmm, it seems that the boot flag should be removed from /dev/vda2
partition?
Actually, I tried this and left the boot flag only to /dev/vda1. I
rebooted and I am still getting the same error. :-(
I was hoping we were close to a solution...
Nick
__
On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas wrote:
> On 5/5/2017 1:42 μμ, Nikolaos Milas wrote:
>
> Hmm, it seems that the boot flag should be removed from /dev/vda2
>> partition?
>>
>
> Actually, I tried this and left the boot flag only to /dev/vda1. I
> rebooted and I am still getting the s
On 5/5/2017 1:57 μμ, Gianluca Cecchi wrote:
what do you get when you boot the VM (I imagine with supergrub2 you
described) and run this
lspci
lspci -kn
Here you are:
# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 823
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ.
On 05/05/2017 12:57, Gianluca Cecchi wrote:
grub-install /dev/vda2 didn't work ?
On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas wrote:
On 5/5/2017 1:42 μμ, Nikolaos Milas wrote:
Hmm, it seems that the boot flag should be removed from /dev/vda2
partition?
Actually, I tried this and left
On Fri, May 5, 2017 at 2:05 PM, Bernard Lheureux <
bernard.lheur...@bbsoft4.org> wrote:
> On 05/05/2017 12:57, Gianluca Cecchi wrote:
>
> grub-install /dev/vda2 didn't work ?
>
>
As this is a CentOS 7.x system, I would say this, if you want to install it
on MBR:
grub2-install /dev/vda
as detaile
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 actual
system (booted using super-grub2
On Fri, May 5, 2017 at 2:38 PM, Nikolaos Milas 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 Ins
On 5/5/2017 3:45 μμ, Gianluca Cecchi wrote:
BTW: see also this paragraph in the provided RH EL link:
24.7.3. Resetting and Reinstalling GRUB 2
But i think is not your problem
Yes, I have done that, without change in behavior.
Also, after changing partitions flag does your fdisk command
Il 05 Mag 2017 19:30, "Nikolaos Milas" ha scritto:
On 5/5/2017 3:45 μμ, Gianluca Cecchi wrote:
BTW: see also this paragraph in the provided RH EL link:
> 24.7.3. Resetting and Reinstalling GRUB 2
>
> But i think is not your problem
>
Yes, I have done that, without change in behavior.
Also
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 f
On 5/5/2017 8:46 μμ, Nikolaos Milas wrote:
If so, may it be that this fix has not been rolled out to CentOS repos
yet?
Note: Both the original (backed up) and the restored (clone) VM are
up-to-date. No new updates available in the standard CentOS repos.
Nick
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/vdal497M 192M 306M 39% /mnt/sysimage/boot
...
Why do you say
On Fri, May 5, 2017 at 2:46 PM, Nikolaos Milas wrote:
> 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
I thought this worked. Many web pages tell you it works. But bash is
ignoring tabs in my here docs. Worst, where there are two tabs, it is
functioning as a command expand in bash, where all files in the current
directory are listed to complete the command.
The following is the here doc I am
On 5/5/2017 11:16 AM, Robert Moskowitz wrote:
But bash is ignoring tabs in my here docs.
tab in bash is indeed filename expansion. what are 'my here' docs ?
not familiar with that phrase.
--
john r pierce, recycling bits in santa cruz
___
Cen
On 05/05/2017 02:40 PM, John R Pierce wrote:
On 5/5/2017 11:16 AM, Robert Moskowitz wrote:
But bash is ignoring tabs in my here docs.
tab in bash is indeed filename expansion. what are 'my here' docs ?
not familiar with that phrase.
A *here document* is a special-purpose code block
On Fri, May 5, 2017 at 8:06 PM, Nikolaos Milas wrote:
> 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
On Fri, May 5, 2017 at 7:46 PM, Nikolaos Milas wrote:
> 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 m
On Fri, May 05, 2017, Robert Moskowitz wrote:
>I thought this worked. Many web pages tell you it works. But bash is
>ignoring tabs in my here docs. Worst, where there are two tabs, it is
>functioning as a command expand in bash, where all files in the current
>directory are listed to complete th
On 05/05/2017 03:33 PM, Bill Campbell wrote:
On Fri, May 05, 2017, Robert Moskowitz wrote:
I thought this worked. Many web pages tell you it works. But bash is
ignoring tabs in my here docs. Worst, where there are two tabs, it is
functioning as a command expand in bash, where all files in t
More research...
On 05/05/2017 04:35 PM, Robert Moskowitz wrote:
On 05/05/2017 03:33 PM, Bill Campbell wrote:
On Fri, May 05, 2017, Robert Moskowitz wrote:
I thought this worked. Many web pages tell you it works. But bash is
ignoring tabs in my here docs. Worst, where there are two tabs,
On 5/5/2017 1:41 PM, Robert Moskowitz wrote:
I just did a test where I created a file, xit, with the here document
in it and ran it with ./xit
This way, the tabs remained. So the 'problem' is when I am pasting
the same lines (with tabs) into the terminal window. There bash is
interpreting
On 05/05/2017 04:46 PM, John R Pierce wrote:
On 5/5/2017 1:41 PM, Robert Moskowitz wrote:
I just did a test where I created a file, xit, with the here document
in it and ran it with ./xit
This way, the tabs remained. So the 'problem' is when I am pasting
the same lines (with tabs) into t
On 5/5/17 1:52 PM, Robert Moskowitz wrote:
On 05/05/2017 04:46 PM, John R Pierce wrote:
On 5/5/2017 1:41 PM, Robert Moskowitz wrote:
I just did a test where I created a file, xit, with the here document
in it and ran it with ./xit
This way, the tabs remained. So the 'problem' is when I am
It's certainly possible to include tabs in here documents, in shell
scripts it works as expected.
However, when you input the here document on the command line in an
interactive shell, the moment you enter the tab it immediately triggers
Bash' programmable completion and the tab never reaches
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 h
Excellent!
On 05/05/2017 05:11 PM, Robbert Eggermont wrote:
It's certainly possible to include tabs in here documents, in shell
scripts it works as expected.
However, when you input the here document on the command line in an
interactive shell, the moment you enter the tab it immediately
tri
32 matches
Mail list logo
