Hello,
I have a small system:
- 6GB drive
- ext4 partition mounted readonly
- swap partition that is not listed in fstab and not enabled. (I will
swapon it every few weeks or so if I need it for a large compile job)
- 2 GB RAM
When the system boots it processing video from a USB camera.
I see boot problems on two of my machines ... very likely related to
lvm2 as far as I can tell so far.
Downgraded and even disabled systemd, re-emerged stuff ... I am still at
trying to find the reason. Maybe it is with the mdadm raids also ...
I just want to ask you other gentoo users if
Am 03.05.2014 12:12, schrieb Stefan G. Weichinger:
I see boot problems on two of my machines ... very likely related to
lvm2 as far as I can tell so far.
Downgraded and even disabled systemd, re-emerged stuff ... I am still at
trying to find the reason. Maybe it is with the mdadm raids
On 3 May 2014 12:12:09 CEST, Stefan G. Weichinger li...@xunil.at wrote:
I see boot problems on two of my machines ... very likely related to
lvm2 as far as I can tell so far.
Downgraded and even disabled systemd, re-emerged stuff ... I am still
at
trying to find the reason. Maybe it is with the
I can't answer all your questions, but here is what I can answer:
On Saturday 03 May 2014 08:16:24 Chris Stankevitz wrote:
Hello,
I have a small system:
- 6GB drive
- ext4 partition mounted readonly
- swap partition that is not listed in fstab and not enabled. (I will
swapon it
Am 03.05.2014 12:27, schrieb J. Roeleveld:
On 3 May 2014 12:12:09 CEST, Stefan G. Weichinger li...@xunil.at wrote:
I see boot problems on two of my machines ... very likely related to
lvm2 as far as I can tell so far.
Downgraded and even disabled systemd, re-emerged stuff ... I am still
at
On Saturday, May 03, 2014 12:28:03 PM Stefan G. Weichinger wrote:
Am 03.05.2014 12:12, schrieb Stefan G. Weichinger:
I see boot problems on two of my machines ... very likely related to
lvm2 as far as I can tell so far.
Downgraded and even disabled systemd, re-emerged stuff ... I am
On Saturday, May 03, 2014 12:33:11 PM Stefan G. Weichinger wrote:
Am 03.05.2014 12:27, schrieb J. Roeleveld:
On 3 May 2014 12:12:09 CEST, Stefan G. Weichinger li...@xunil.at
wrote:
I see boot problems on two of my machines ... very likely related to
lvm2 as far as I can tell so far.
Am 03.05.2014 12:49, schrieb J. Roeleveld:
Interesting.
In your other email you mentioned you can access the LVM volumes using a
rescue-cd.
Are there any snapshots in there? Or did you do any recent changes to the LVs?
I am wondering if there might be an issue with the metadata causing
On Saturday, May 03, 2014 12:56:11 PM Stefan G. Weichinger wrote:
Am 03.05.2014 12:49, schrieb J. Roeleveld:
Interesting.
In your other email you mentioned you can access the LVM volumes using a
rescue-cd.
Are there any snapshots in there? Or did you do any recent changes to the
LVs? I
Am 03.05.2014 12:54, schrieb J. Roeleveld:
I don't use systemd, but as it's pushed by Redhat and redhat, by default,
uses
LVM, I would expect that part to work correctly together.
Yes ... but I still don't fully get what services to enable to get it
set up correctly. lvmetad yes or no,
Am 03.05.2014 13:05, schrieb J. Roeleveld:
dracut = initramfs
Did you update the initramfs recently? If out-of-sync with what is on the
main environment, it could lead to issues.
I worked with exactly this box around 10hrs ago and it booted fine then.
I will check genlop what I upgraded
On Saturday, May 03, 2014 01:06:03 PM Stefan G. Weichinger wrote:
Am 03.05.2014 12:54, schrieb J. Roeleveld:
I don't use systemd, but as it's pushed by Redhat and redhat, by default,
uses LVM, I would expect that part to work correctly together.
Yes ... but I still don't fully get what
On Saturday, May 03, 2014 01:12:45 PM Stefan G. Weichinger wrote:
Am 03.05.2014 13:05, schrieb J. Roeleveld:
dracut = initramfs
Did you update the initramfs recently? If out-of-sync with what is on the
main environment, it could lead to issues.
I worked with exactly this box around
Am 03.05.2014 13:19, schrieb J. Roeleveld:
Sounds like an issue with the mdadm-raid devices.
Try setting those up WITHOUT systemctl (or init.d-scripts)
Then checking
- /proc/mdstat
- dmesg
- logging
Any of those might show an error.
Maybe ssh-in from a seperate machine to enable the
On Saturday, May 03, 2014 01:26:23 PM Stefan G. Weichinger wrote:
Am 03.05.2014 13:19, schrieb J. Roeleveld:
Sounds like an issue with the mdadm-raid devices.
Try setting those up WITHOUT systemctl (or init.d-scripts)
Then checking
- /proc/mdstat
- dmesg
- logging
Any of those
Am 03.05.2014 13:26, schrieb Stefan G. Weichinger:
Am 03.05.2014 13:19, schrieb J. Roeleveld:
Sounds like an issue with the mdadm-raid devices.
Try setting those up WITHOUT systemctl (or init.d-scripts)
Then checking
- /proc/mdstat
- dmesg
- logging
Any of those might show an error.
On Saturday, May 03, 2014 01:39:06 PM Stefan G. Weichinger wrote:
Am 03.05.2014 13:26, schrieb Stefan G. Weichinger:
Am 03.05.2014 13:19, schrieb J. Roeleveld:
Sounds like an issue with the mdadm-raid devices.
Try setting those up WITHOUT systemctl (or init.d-scripts)
Then checking
-
Am 03.05.2014 14:03, schrieb J. Roeleveld:
Booted with rd.auto=1 and now I also get a funny start job
running/waiting for /dev/sda1 (/ on the SSD).
Oh my! :-)
That's no good.
Something is not playing well.
I would check the boot-scripts/unit-files/dependencies
Yep, I do .. see other
* Stefan G. Weichinger li...@xunil.at [140503 08:09]:
Am 03.05.2014 13:39, schrieb Stefan G. Weichinger:
Booted with rd.auto=1 and now I also get a funny start job
running/waiting for /dev/sda1 (/ on the SSD).
Oh my! :-)
pasta now.
So, back from speed-lunch now ;-)
While
On Saturday, May 03, 2014 02:08:26 PM Stefan G. Weichinger wrote:
Am 03.05.2014 13:39, schrieb Stefan G. Weichinger:
Booted with rd.auto=1 and now I also get a funny start job
running/waiting for /dev/sda1 (/ on the SSD).
Oh my! :-)
pasta now.
So, back from speed-lunch now ;-)
On Saturday, May 03, 2014 02:09:39 PM Stefan G. Weichinger wrote:
Am 03.05.2014 14:03, schrieb J. Roeleveld:
Booted with rd.auto=1 and now I also get a funny start job
running/waiting for /dev/sda1 (/ on the SSD).
Oh my! :-)
That's no good.
Something is not playing well.
I would
Am 03.05.2014 14:17, schrieb Todd Goodman:
* Stefan G. Weichinger li...@xunil.at [140503 08:09]:
Am 03.05.2014 13:39, schrieb Stefan G. Weichinger:
Booted with rd.auto=1 and now I also get a funny start job
running/waiting for /dev/sda1 (/ on the SSD).
Oh my! :-)
pasta now.
So, back
Am 03.05.2014 14:19, schrieb J. Roeleveld:
On Saturday, May 03, 2014 02:09:39 PM Stefan G. Weichinger wrote:
Am 03.05.2014 14:03, schrieb J. Roeleveld:
Booted with rd.auto=1 and now I also get a funny start job
running/waiting for /dev/sda1 (/ on the SSD).
Oh my! :-)
That's no good.
Am 03.05.2014 14:17, schrieb J. Roeleveld:
(Don't ask for the strange setup with sdb3/sdc6 and sdb6/sdc3,
historically grown somehow ...)
Seen stranger, it works.
What do the logs show when enabling them? Any odd messages?
Just looked it up, nothing odd. To me it seems that the assembling
On Sat, May 3, 2014 at 8:08 AM, Stefan G. Weichinger li...@xunil.at wrote:
Box boots now with kernel 3.14.1 and with commented LVs in fstab.
When I login and check there are no mdadm-raids assembled.
When I mdadm -A --scan they get correctly assembled:
# cat /proc/mdstat
Personalities :
On Saturday, May 03, 2014 02:43:39 PM Stefan G. Weichinger wrote:
Am 03.05.2014 14:17, schrieb J. Roeleveld:
(Don't ask for the strange setup with sdb3/sdc6 and sdb6/sdc3,
historically grown somehow ...)
Seen stranger, it works.
What do the logs show when enabling them? Any odd
Am 03.05.2014 14:52, schrieb J. Roeleveld:
If you boot without those in fstab, then do the mdadm and lvm steps manually,
do you then have it working ?
yes ... everything up and accessible then.
If yes, I would leave it for now and wait for Canek to come online in a few
hours. (Mexico
* J. Roeleveld jo...@antarean.org [140503 08:24]:
On Saturday, May 03, 2014 08:17:37 AM Todd Goodman wrote:
snipped
FWIW, I have a similar problem with mdadm and dracut and do something
similarly to what's described in:
Am 03.05.2014 15:08, schrieb Todd Goodman:
I wouldn't think so, but when I set up a new server somewhat recently I
needed to do the same.
I've heard of others who don't need to do anything special so it's
likely some misconfiguration on my part.
In my case it seems to be related to the
Am 03.05.2014 14:52, schrieb Tom H:
Has mdadm.service to be enabled as well? Or is that redundant in a way?
Try rd.md.uuid=... for all the md arrays that you want to bring up.
Tested that right now, no mdadm-array assembled!
Thanks anyway, Stefan
On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld jo...@antarean.org wrote:
[snip]
Sounds like an issue with the mdadm script/unit.
Where is Canek with his knowledge of systemd?
Canek was sleeping because it was 6:37 AM on a Saturday morning.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura,
Am 03.05.2014 15:46, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld jo...@antarean.org wrote:
[snip]
Sounds like an issue with the mdadm script/unit.
Where is Canek with his knowledge of systemd?
Canek was sleeping because it was 6:37 AM on a Saturday morning.
On Sat, May 3, 2014 at 7:52 AM, J. Roeleveld jo...@antarean.org wrote:
[...]
If you boot without those in fstab, then do the mdadm and lvm steps manually,
do you then have it working ?
If yes, I would leave it for now and wait for Canek to come online in a few
hours. (Mexico should be awake
Am 03.05.2014 15:50, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 7:52 AM, J. Roeleveld jo...@antarean.org wrote:
[...]
If you boot without those in fstab, then do the mdadm and lvm steps manually,
do you then have it working ?
If yes, I would leave it for now and wait for Canek to
On Sat, May 3, 2014 at 8:48 AM, Stefan G. Weichinger li...@xunil.at wrote:
Am 03.05.2014 15:46, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld jo...@antarean.org wrote:
[snip]
Sounds like an issue with the mdadm script/unit.
Where is Canek with his knowledge of
Am 03.05.2014 15:59, schrieb Canek Peláez Valdés:
Regarding your problem; as I said to Joost, I have no idea what could
possibly cause the problem, but from the experiments I conducted
trying to understand what happened with systemd+LVM2, I got the
impression that this kind of issue happens
On 3 May 2014 15:46:07 CEST, Canek Peláez Valdés can...@gmail.com wrote:
On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld jo...@antarean.org
wrote:
[snip]
Sounds like an issue with the mdadm script/unit.
Where is Canek with his knowledge of systemd?
Canek was sleeping because it was 6:37 AM on a
On 3 May 2014 15:48:03 CEST, Stefan G. Weichinger li...@xunil.at wrote:
Am 03.05.2014 15:46, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld jo...@antarean.org
wrote:
[snip]
Sounds like an issue with the mdadm script/unit.
Where is Canek with his knowledge of systemd?
On Sat, May 3, 2014 at 10:08 AM, J. Roeleveld jo...@antarean.org wrote:
On 3 May 2014 15:48:03 CEST, Stefan G. Weichinger li...@xunil.at wrote:
Am 03.05.2014 15:46, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 6:37 AM, J. Roeleveld jo...@antarean.org
wrote:
[snip]
Sounds like an issue
Am 03.05.2014 15:57, schrieb Stefan G. Weichinger:
Am 03.05.2014 15:50, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 7:52 AM, J. Roeleveld jo...@antarean.org wrote:
[...]
If you boot without those in fstab, then do the mdadm and lvm steps
manually,
do you then have it working ?
If
Am 03.05.2014 18:40, schrieb Stefan G. Weichinger:
Am 03.05.2014 15:57, schrieb Stefan G. Weichinger:
Am 03.05.2014 15:50, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 7:52 AM, J. Roeleveld jo...@antarean.org wrote:
[...]
If you boot without those in fstab, then do the mdadm and lvm
Am 03.05.2014 18:51, schrieb Stefan G. Weichinger:
Am 03.05.2014 18:40, schrieb Stefan G. Weichinger:
Am 03.05.2014 15:57, schrieb Stefan G. Weichinger:
Am 03.05.2014 15:50, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 7:52 AM, J. Roeleveld jo...@antarean.org wrote:
[...]
If you boot
On Saturday 03 May 2014 14:17:53 J. Roeleveld wrote:
With genkernel, I have a lvm and mdadm boot parameter.
With dracut, that might also be necessary.
I would prefer the initramfs to do it automagically without extra
parameters.
Hope I'm not butting in here, but...
Although I don't run
On Sat, May 3, 2014 at 12:00 PM, Stefan G. Weichinger li...@xunil.at wrote:
[snip]
An older kernel (3.13.4) boots OK ... the newer ones are screwed up
(their initramfs) ...
Back to the start.
As I don't boot from LVM or mdadm-raid I consider to not need any
DRACUT_MODULES= in
Am 03.05.2014 19:25, schrieb Canek Peláez Valdés:
I'll give you my confs in my LVM2 virtual machine; my normal machines
don't use LVM2, so I don't think they'll help in any way.
Also, if my normal machines are lagging on updates, the virtual ones
are even more behind: my LVM vm has systemd
On Sat, May 3, 2014 at 12:25 PM, Canek Peláez Valdés can...@gmail.com wrote:
[...]
Let me try to update this test VM to see if I can hit the same issue as you.
Total: 124 packages (107 upgrades, 1 downgrade, 5 new, 2 in new slots,
9 reinstalls, 1 uninstall), Size of downloads: 663,051 kB
This
Am 03.05.2014 19:25, schrieb Canek Peláez Valdés:
Do you want to see any other config?
The version numbers would be interesting:
grub
dracut
lvm2
systemd
...
Thanks! I configured my machine similar to yours and try the next booting ..
On Sat, May 3, 2014 at 1:30 PM, Stefan G. Weichinger li...@xunil.at wrote:
Am 03.05.2014 19:25, schrieb Canek Peláez Valdés:
Do you want to see any other config?
The version numbers would be interesting:
grub
dracut
lvm2
systemd
sys-boot/grub-2.00_p5107-r1:2
sys-kernel/dracut-033:0
On Saturday, May 03, 2014 01:30:43 PM Canek Peláez Valdés wrote:
On Sat, May 3, 2014 at 12:25 PM, Canek Peláez Valdés can...@gmail.com
wrote: [...]
Let me try to update this test VM to see if I can hit the same issue as
you.
Total: 124 packages (107 upgrades, 1 downgrade, 5 new, 2 in new
Am 03.05.2014 20:33, schrieb Canek Peláez Valdés:
sys-boot/grub-2.00_p5107-r1:2
sys-kernel/dracut-033:0
sys-apps/systemd-204:0
sys-fs/lvm2-2.02.100-r2:0
great, thanks
I am able to boot a kernel 3.13.4 with its initramfs which was built
back then with dracut-034-r1. No mdadm-raids assembled
On Saturday, May 03, 2014 06:09:21 PM Peter Humphrey wrote:
On Saturday 03 May 2014 14:17:53 J. Roeleveld wrote:
With genkernel, I have a lvm and mdadm boot parameter.
With dracut, that might also be necessary.
I would prefer the initramfs to do it automagically without extra
On Saturday, May 03, 2014 02:38:08 PM Stefan G. Weichinger wrote:
Am 03.05.2014 14:19, schrieb J. Roeleveld:
On Saturday, May 03, 2014 02:09:39 PM Stefan G. Weichinger wrote:
Pasta, which kind?
Plain spaghetti with veggie sugo ... not very inspired.
Can still be nice.
My daughter
On Saturday, May 03, 2014 08:37:49 PM Stefan G. Weichinger wrote:
Am 03.05.2014 20:33, schrieb Canek Peláez Valdés:
sys-boot/grub-2.00_p5107-r1:2
sys-kernel/dracut-033:0
sys-apps/systemd-204:0
sys-fs/lvm2-2.02.100-r2:0
great, thanks
I am able to boot a kernel 3.13.4 with its
Am 03.05.2014 20:47, schrieb J. Roeleveld:
On Saturday, May 03, 2014 08:37:49 PM Stefan G. Weichinger wrote:
Am 03.05.2014 20:33, schrieb Canek Peláez Valdés:
sys-boot/grub-2.00_p5107-r1:2
sys-kernel/dracut-033:0
sys-apps/systemd-204:0
sys-fs/lvm2-2.02.100-r2:0
great, thanks
I am able to
On Saturday, May 03, 2014 08:51:14 PM Stefan G. Weichinger wrote:
Am 03.05.2014 20:47, schrieb J. Roeleveld:
On Saturday, May 03, 2014 08:37:49 PM Stefan G. Weichinger wrote:
Am 03.05.2014 20:33, schrieb Canek Peláez Valdés:
sys-boot/grub-2.00_p5107-r1:2
sys-kernel/dracut-033:0
Am 03.05.2014 20:56, schrieb J. Roeleveld:
Thanks for the offer, I am not yet there ;-)
Ok. I hardly ever delete anything these days. So those are likely to remain
available in their current form for the foreseeable future.
My current goal is to get a working 3.13.11 with systemd and
On Sat, May 3, 2014 at 1:35 PM, J. Roeleveld jo...@antarean.org wrote:
On Saturday, May 03, 2014 01:30:43 PM Canek Peláez Valdés wrote:
On Sat, May 3, 2014 at 12:25 PM, Canek Peláez Valdés can...@gmail.com
wrote: [...]
Let me try to update this test VM to see if I can hit the same issue as
On Sat, May 3, 2014 at 1:51 PM, Stefan G. Weichinger li...@xunil.at wrote:
[snip]
and a shiny new bug for dracut as well:
https://bugs.gentoo.org/show_bug.cgi?id=509492
That looks like a reasonable explanation. But it could be something else.
So even more moving parts for me no :-P
In my
Am 03.05.2014 21:33, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 1:35 PM, J. Roeleveld jo...@antarean.org wrote:
On Saturday, May 03, 2014 01:30:43 PM Canek Peláez Valdés wrote:
On Sat, May 3, 2014 at 12:25 PM, Canek Peláez Valdés can...@gmail.com
wrote: [...]
Let me try to update
On Sat, May 3, 2014 at 2:38 PM, Stefan G. Weichinger li...@xunil.at wrote:
Am 03.05.2014 21:33, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 1:35 PM, J. Roeleveld jo...@antarean.org wrote:
On Saturday, May 03, 2014 01:30:43 PM Canek Peláez Valdés wrote:
On Sat, May 3, 2014 at 12:25 PM,
Am 03.05.2014 21:41, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 2:38 PM, Stefan G. Weichinger li...@xunil.at wrote:
Am 03.05.2014 21:33, schrieb Canek Peláez Valdés:
On Sat, May 3, 2014 at 1:35 PM, J. Roeleveld jo...@antarean.org wrote:
On Saturday, May 03, 2014 01:30:43 PM Canek
Am 03.05.2014 21:53, schrieb Stefan G. Weichinger:
As per the bug you posted, can you show us the contents of your
initramfs, to check that the LVM binaries are included? And confirm
that the binaries are the same as in your normal system?
Hm, yes ... I was a bit faster and already applied
Am 03.05.2014 22:23, schrieb Stefan G. Weichinger:
So I got some decent cleanup today ... removed one of the RAID-arrays
(obsolete/unused), redid my fstab completely and modified the whole
dracut/grub2/kerninst-setup ... phew!
[...]
I wonder if I should keep or remove the option
On Saturday 03 May 2014 20:40:47 J. Roeleveld wrote:
On Saturday, May 03, 2014 06:09:21 PM Peter Humphrey wrote:
Hope I'm not butting in here, but...
Although I don't run systemd nor do I have an initramfs, the grub.conf
entry for my LVM2 setup is just these two lines:
title=Gentoo
Am 03.05.2014 22:50, schrieb Peter Humphrey:
Yes, I noticed that annoyance myself. I would much prefer it to default to
more logical names.
If the docs had included that little snippet I'd have saved myself many a
frustrating hour. I'll only look stupid if I tell you how many ;-)
I had a similar issue after upgrading to sys-apps/systemd-212-r3. Turned
out it was due to udev rules.d directory location. I still had a bunch
of udev rules under /usr/lib64/udev/rules.d and it looks like the new
systemd/udev is only looking at rules under /lib/udev/.
The particular issue was
67 matches
Mail list logo
