Hi all,
I get en error during boot, saying (iscsi) device /dev/sdb1 doesn't exist, maybe because
iscsi daemon is loaded after mount command, in fact it appears lower in the startup log.
Actually it is not a big issue, because when the system is up and running everything is
in place, but I would like to fix this issue.
Where is the right place to start iscsi correctly ? It seems to be already at an early point in time...
Here is the /etc/rc.d/rc5.d startup listing:
lrwxrwxrwx. 1 root root 17 Jan 16 12:15 S01sysstat -> ../init.d/sysstat
lrwxrwxrwx. 1 root root 22 Jan 16 14:48 S02lvm2-monitor -> ../init.d/lvm2-monitor
lrwxrwxrwx. 1 root root 16 Feb 1 17:17 S07iscsid -> ../init.d/iscsid
lrwxrwxrwx. 1 root root 19 Jan 16 12:09 S08ip6tables -> ../init.d/ip6tables
lrwxrwxrwx. 1 root root 18 Jan 16 12:08 S08iptables -> ../init.d/iptables
lrwxrwxrwx. 1 root root 17 Jan 16 14:48 S10network -> ../init.d/network
lrwxrwxrwx 1 root root 16 Feb 6 00:15 S11auditd -> ../init.d/auditd
lrwxrwxrwx. 1 root root 21 Jan 16 12:10 S11portreserve -> ../init.d/portreserve
lrwxrwxrwx. 1 root root 17 Jan 16 12:13 S12rsyslog -> ../init.d/rsyslog
lrwxrwxrwx. 1 root root 18 Jan 16 12:16 S13cpuspeed -> ../init.d/cpuspeed
lrwxrwxrwx. 1 root root 20 Jan 16 14:51 S13irqbalance -> ../init.d/irqbalance
lrwxrwxrwx 1 root root 15 Feb 6 12:45 S13iscsi -> ../init.d/iscsi
lrwxrwxrwx. 1 root root 17 Jan 16 12:09 S13rpcbind -> ../init.d/rpcbind
lrwxrwxrwx. 1 root root 19 Jan 16 12:12 S15mdmonitor -> ../init.d/mdmonitor
lrwxrwxrwx. 1 root root 16 Jan 16 14:50 S20lldpad -> ../init.d/lldpad
lrwxrwxrwx. 1 root root 14 Jan 16 12:15 S21fcoe -> ../init.d/fcoe
lrwxrwxrwx. 1 root root 20 Jan 16 14:47 S22messagebus -> ../init.d/messagebus
lrwxrwxrwx. 1 root root 24 Jan 16 12:14 S23NetworkManager -> ../init.d/NetworkManager
lrwxrwxrwx. 1 root root 22 Jan 16 12:13 S24avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 17 Feb 6 12:45 S24nfslock -> ../init.d/nfslock
lrwxrwxrwx. 1 root root 14 Feb 5 17:56 S24o2cb -> ../init.d/o2cb
lrwxrwxrwx 1 root root 16 Feb 6 12:45 S24openct -> ../init.d/openct
lrwxrwxrwx 1 root root 17 Feb 6 12:45 S24rpcgssd -> ../init.d/rpcgssd
lrwxrwxrwx 1 root root 19 Feb 6 12:45 S24rpcidmapd -> ../init.d/rpcidmapd
lrwxrwxrwx. 1 root root 14 Jan 16 14:50 S25cups -> ../init.d/cups
lrwxrwxrwx. 1 root root 15 Jan 16 14:48 S25netfs -> ../init.d/netfs
lrwxrwxrwx. 1 root root 15 Feb 5 17:56 S25ocfs2 -> ../init.d/ocfs2
lrwxrwxrwx. 1 root root 15 Jan 16 12:16 S26acpid -> ../init.d/acpid
lrwxrwxrwx. 1 root root 19 Jan 16 12:12 S26haldaemon -> ../init.d/haldaemon
lrwxrwxrwx. 1 root root 19 Jan 16 14:48 S26udev-post -> ../init.d/udev-post
lrwxrwxrwx 1 root root 15 Feb 6 12:45 S27pcscd -> ../init.d/pcscd
lrwxrwxrwx. 1 root root 16 Jan 16 14:50 S28autofs -> ../init.d/autofs
lrwxrwxrwx 1 root root 17 Feb 6 12:45 S50mcelogd -> ../init.d/mcelogd
lrwxrwxrwx. 1 root root 14 Jan 16 14:51 S55sshd -> ../init.d/sshd
lrwxrwxrwx. 1 root root 14 Jan 16 12:34 S58ntpd -> ../init.d/ntpd
lrwxrwxrwx. 1 root root 24 Jan 16 12:16 S70spice-vdagentd -> ../init.d/spice-vdagentd
lrwxrwxrwx. 1 root root 17 Jan 16 12:12 S80postfix -> ../init.d/postfix
lrwxrwxrwx. 1 root root 15 Jan 16 12:13 S90crond -> ../init.d/crond
lrwxrwxrwx. 1 root root 19 Jan 18 15:00 S91vncserver -> ../init.d/vncserver
lrwxrwxrwx. 1 root root 13 Jan 16 12:09 S95atd -> ../init.d/atd
lrwxrwxrwx. 1 root root 21 Jan 16 12:12 S98tog-pegasus -> ../init.d/tog-pegasus
lrwxrwxrwx. 1 root root 20 Jan 16 12:13 S99certmonger -> ../init.d/certmonger
lrwxrwxrwx. 1 root root 24 Jan 31 14:48 S99libvirt-guests -> ../init.d/libvirt-guests
lrwxrwxrwx. 1 root root 11 Jan 16 14:48 S99local -> ../rc.local
Thanks for any hint.
Diabolik
error mounting iscsi device at boot
error mounting iscsi device at boot
Use _netdev on the mount options in /etc/fstab for that mount point. This tells the initscripts that the mount point is dependent on the network and not to try to mount it until the network is available.
-
- Posts: 315
- Joined: 2012/09/15 21:06:54
Re: error mounting iscsi device at boot
[quote]
TrevorH wrote:
Use _netdev on the mount options in /etc/fstab for that mount point. This tells the initscripts that the mount point is dependent on the network and not to try to mount it until the network is available.[/quote]
Or consider whether you could use the automounter to mount the directories when needed and not on boot.
TrevorH wrote:
Use _netdev on the mount options in /etc/fstab for that mount point. This tells the initscripts that the mount point is dependent on the network and not to try to mount it until the network is available.[/quote]
Or consider whether you could use the automounter to mount the directories when needed and not on boot.
-
- Posts: 3
- Joined: 2013/02/06 13:47:44
Re: error mounting iscsi device at boot
[quote]
TrevorH wrote:
Use _netdev on the mount options in /etc/fstab for that mount point. [/quote]
This is exactly what I needed. Thank you. :-)
Diab.
TrevorH wrote:
Use _netdev on the mount options in /etc/fstab for that mount point. [/quote]
This is exactly what I needed. Thank you. :-)
Diab.
-
- Posts: 3
- Joined: 2013/02/06 13:47:44
Re: error mounting iscsi device at boot
Actually there's still a strange behaviour: in the boot log I see:
mount.ocfs2: device or resource busy while mounting device /dev/sdb1 [FAILED]
but when I login after startup the ocfs2 filesystem is correctly there.
Why this fail message during boot ?
mount.ocfs2: device or resource busy while mounting device /dev/sdb1 [FAILED]
but when I login after startup the ocfs2 filesystem is correctly there.
Why this fail message during boot ?