Displaying 6 results from an estimated 6 matches for "401c".
Did you mean:
401
2016 Jul 07
3
no boot, no message
...;40 #30ffffff #00000000 std
LABEL slack64
MENU LABEL Slackware 14.2
LINUX ../slackware/vmlinuz--huge-4.4.14
APPEND root=/dev/sda7
LABEL gentoo
MENU LABEL Gentoo
LINUX ../gentoo/vmlinuz
APPEND root=/dev/sda2
# APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
#
#LABEL gentoo
# MENU LABEL Gentoo
# LINUX ../gentoo/vmlinuz
## APPEND root=/dev/sda1
# APPEND root=PARTUUID=645c1577-e5d7-41eb-9c43-bfee52088197
#
LABEL gentoo_uuid
MENU LABEL Gentoo (UUID)
LINUX ../gentoo/vmlinuz
# APPEND root=/dev...
2016 Jul 07
0
no boot, no message
...ompare it with the one being used in the syslinux.cfg:
vmlinuz--huge-4.4.14
Do you note the extra dash symbol "-"?
>
> LABEL gentoo
> MENU LABEL Gentoo
> LINUX ../gentoo/vmlinuz
> APPEND root=/dev/sda2
> # APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
>
> #
> #LABEL gentoo
> # MENU LABEL Gentoo
> # LINUX ../gentoo/vmlinuz
> ## APPEND root=/dev/sda1
> # APPEND root=PARTUUID=645c1577-e5d7-41eb-9c43-bfee52088197
> #
>
> LABEL gentoo_uuid
> MENU LABEL Gentoo (UUID)
&...
2016 Jul 07
3
no boot, no message
I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I
installed another linux system in other partitions of the same drive
(a 64 bit system), updated syslinux.cfg, setup the new system as
default, and the new entry appears in the menu. Problem is: it doesn't
boot. On timeout, it starts counting down again, and that's it. No
error message whatsoever. Selecting the old system
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...0E72892AE7B10FF (b0c0c85d-f3b4-4564-b28f-59b08089d521) on home-client-2
[2017-10-25 10:14:18.793380] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/5B754C0965DFAE3ACB2B865AD82D3CFEF25ED8D5 (06323d68-c013-401c-9bc4-da488c548092) on home-client-2
[2017-10-25 10:14:18.803249] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/0A71093C1F957EBF411EF3D7913919CDCFF14D14 (f36fdafe-91fb-4d97-b13f-59003fafecf9) on home-cli...