5

F16 - pb mount at boot

view full story
linux-howto

http://forums.fedoraforum.org – hi everybody, I have an error when trying to mount my LaCie network kdisque at boot. it seems to me that mount is coming too early during the boot process when network is not established. see extract from /var/log/messages. larger extract of /var/log/messages. Code: Apr 30 10:07:51 PCSalon kernel: [  27.306387] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) Apr 30 10:07:52 PCSalon avahi-daemon[737]: Successfully called chroot(). Apr 30 10:07:52 PCSalon avahi-daemon[737]: Successfully dropped remaining capabilities. Apr 30 10:07:52 PCSalon ava (HowTos)

leex's picture
Submitted by leex on 04/30/2012 – Made popular on 04/30/2012

Stories similar to F16 - pb mount at boot

root fs error on boot 43 weeks 13 hours ago

When I boot, I always get these messages:

Code: [    5.916703] EXT4-fs warning (device dm-1): ext4_clear_journal_err:4401: Filesystem error recorded from previous mount: IO failure [    5.916775] EXT4-fs warning (device dm-1): ext4_clear_journal_err:4402: Marking fs in need of filesystem check. [    5.917544] EXT4-fs (dm-1): mounted filesystem with ordered d

Hello all, perhaps this is an odd request, but I have the requirement none the less. Every time I mount a filesystem (at least an ext4 filesystem), I get a line indicating such in the syslog:

Oct 9 22:26:28 sulaco kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts:

I would like to not have these in the syslog.

My system dual boots Ubuntu and Fedora, I believe both have a boot partition installed but Ubuntu is the one that actually has the boot loader and autodetects the fedora kernels.

Selecting other F17 kernels works fine, but when I select the fedup kernel until part way through the boot, the following is incompletely transcribed from a picture because I couldn't find logs anywhere.

Code:

After my Upgrade from F15 to F17 I'm seeing alot of these messages , just wondering if they are significant and/or how do I fix it?

Code: Sep  2 14:27:35 mythbox dbus-daemon[711]: dbus[711]: [system] Successfully activated service 'org.freedesktop.UDisks2' Sep  2 14:27:35 mythbox udisksd[1889]: Acquired the name org.freedesktop.UDisks2 on the system message bus Sep  2 14:2

I'm trying to do the same of this question (multiple linux installation on same filesystem) but I get this result (root filesystem mounted as read-only) . I'm using debian/sid, have successfully modified the initrd /init script and patched the busybox switch_root to chroot into a subdirectory, the filesystem is ext4. The kernel boot but the filesystem is mounted read-only and any variant of mount

I've installed KDE desktop, that depends on avahi. It has two daemons avahi-daemon and avahi-dnsconfd.

In ArchLinux wiki there is no info about avahi-dnsconfd. I've tried Daemon and Avahi pages.

CUPS 1.6 changed the behavior of printer sharing and essentially moved its print advertising out to DNSSD. If you don't have Avahi installed on the server, install it and enabled the avahi-daemon and avahi-dnsconfd (initscripts) or avahi and avahi-daemon (systemd). You may need to configure Avahi in order for it to work.

So I've successfully mounted my own partitions /md0p1, /md0p3 to folders I've created in the root (i.e. /srv or /backup). I've also edited fstab accordingly. All that is tested and done.

Now, how would I go about mounting /var from /dev/md0p2? I can get it mounted as /var2, but I simply cannot get it to mount successfully as /var.

Changing boot sequence order 28 weeks 56 min ago

Hi,

on my machine, it trys to mount the network drives before it's started idmapd and the nfs mount daemon. The drives mount fine after bootup, but I'd like to correct the boot sequence so I don't have to do it manually.

I can't see anything useful in /etc/init.d or in the systemctl manual.

Does anybody know how to rearrange the boot order?