Based on in-depth analysis, I found the cause of the error:
“Apr 03 12:59:15 ubuntu systemd[1]: Failed to set up mount unit: Device or resource busy”
call tree on systemd mount.c & unit.c: mount_dispatch_io -> mount_load_proc_self_mountinfo -> mount_setup_unit -> mount_setup_existing_unit -> mount_add_extras -> unit_set_default_slice: -> unit_set_slice: if (unit_active_state(u) != UNIT_INACTIVE) return -EBUSY;
"unit_set_slice" return EBUSY always, because of nfsroot always active state in netbooting,
"mount_dispatch_io" give up updating mount state when "mount_load_proc_self_mountinfo" return the error.
finally, all systemd mount service failed and then goto emergency shell.
Based on in-depth analysis, I found the cause of the error:
“Apr 03 12:59:15 ubuntu systemd[1]: Failed to set up mount unit: Device or resource busy”
call tree on systemd mount.c & unit.c: proc_self_ mountinfo existing_ unit default_ slice:
-> unit_set_slice:
if (unit_active_ state(u) != UNIT_INACTIVE)
return -EBUSY;
mount_dispatch_io
-> mount_load_
-> mount_setup_unit
-> mount_setup_
-> mount_add_extras
-> unit_set_
"unit_set_slice" return EBUSY always, because of nfsroot always active state in netbooting,
"mount_dispatch_io" give up updating mount state when "mount_ load_proc_ self_mountinfo" return the error.
finally, all systemd mount service failed and then goto emergency shell.