Hi Cyril,
On Sun, 2019-03-03 at 17:24 +0100, Cyril Brulebois wrote:
>
> > My complete Debian installation is on an iSCSI target. So for
> booting I
> > use U-Boot to start iPXE (snp.efi), which loads grubaa64.efi from
> the
> > iSCSI target.
> >
> > As I am booting from an iSCSI target the reboot sequence must be:
> > - unmount all drives
> > - logoff iSCSI target
> > - shutdown network
> >
> > Unfortunately when I tried to reboot the board started hanging in a
> loop
> > trying to raise network interfaces.
> >
> > The fix was to add the option _netdev to all iSCSI mounts in
> /etc/fstab:
> >
> > UUID=.. / ext4 _netdev,errors=remount-ro 0 1
> > UUID=.. /boot ext2 _netdev,nofail,noatime,nodiratime 0 2
> > UUID=.. /boot/efi vfat _netdev,nofail 0 2
> > UUID=.. /home ext4 _netdev,nofail,noatime,nodiratime 0 2
> > tmpfs /tmp tmpfs nosuid 0 0
> > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> >
> > Please, change the installer scripts such that iSCSI partitions
> > automatically receive the _netdev attribute in /etc/fstab.
>
> Thanks for your report.
>
> I'd be happy to get some input from the Debian iSCSI maintainers
> before
> changing anything on the d-i side. Are those _netdev additions
> mandatory
> and/or welcome?
Yes. We've always required "_netdev" marked on traditional sysvinit.
And now, on the default systemd init, we still need it.
Quoting systemd.mount manpage:
Mount units referring to local and network file systems are distinguished by their file system type specification. In some cases this
is not sufficient (for example network block device based mounts, such as iSCSI), in which case _netdev may be added to the mount
option string of the unit, which forces systemd to consider the mount unit a network mount.
So, by specifying _netdev, we are just making it more explicit.
Thanks,
Ritesh
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
Attachment:
signature.asc
Description: This is a digitally signed message part