Recently, I switched from initscript to systemd followed this wiki, and I got error like this during boot:
Job dev-md126p5.device/start timed out
This is my fstab:
/dev/mapper/VGLinux-lvroot / ext4 rw,relatime,stripe=64,data=ordered 0 1 /dev/mapper/VGLinux-lvhome /home ext4 rw,relatime,stripe=64,data=ordered 0 2 /swapfile none swap defaults 0 0 /dev/md126p5 /media/data ntfs-3g uid=xiaoxing,gid=users 0 0
Here is my partition scheme: I have two hard drives which are identical and as default, it is a raid0. Three partitions like this:
- windows 7, 200GB, ntfs
- linux, 100GB, lvm / , 30GB, ext4 /home , 30GB, ext4 the rest for future expend.
- data, rest, ntfs
After the "timed out", it throws me into an emergency mode, I can mount the data partition manually, and run "systemctl default", it will start the system properly. Or I can comment out the "data" part in the fstab file, and get into the system and mount it easily.
There is no problem before I switched to systemd. Now I've tried everything including write my own .service file to mount it, but it still can not mount the partition during boot. Any ideas?
The error above was from the journalctl, the error printed on screen during boot is:
[ TIME ] Timed out waiting for device dev-md126p5.device.
And followed by a lot of [ DEPEND ], then I am in emergency mode.
I am just curious what is the cause? Is it because it is on a raid, or because it is a ntfs partition?