ata1.00 seems to be the hard drive. It doesen't make any clunks and seem to work well.ata5.00 is the dvd reader/writer. it works very bad. barely can read anything and clunks a lot. i never use it and use an external usb dvd/rw

should i replace the hard drive?

may be related to this that sometimes, not very often, the system hangs for a while, may be a minute, may be three.... The GUI gets frozen for some time.

The way I've narrowed down things like this is disconnect all drives, install a known good (or new) drive with os on a new cable, and zero fill and use the suspect drive as storage for a while. Run smartctl daily and use diff on today and yesterday's report.

may be related to this that sometimes, not very often, the system hangs for a while, may be a minute, may be three.... The GUI gets frozen for some time.

Yeah, that sounds typical for a failing drive. You might be able to straighten it out, but drives are so cheap now, you could get a brand new 500 gig for an hours wages. It would probably take you at least an hour to backup, zero fill, and restore the thing. If it's going to die an a month anyway, or keep acting like this, why spend the time?

This one is beyond me, it's all over the place issues. Can say every time I've encountered this systemd start job pita, it's been due to problems in fstab. So triple check your fstab uuids against the output of "sudo blkid".

Da mighty Hoas(Head-on-a-etc) recently advised/informed me of systemd's ability to automount swap even w/o it having an entry in fstab. Yep works, removed swap from fstab, still mounts fine.

Why yours doesn't is odd. Also just recently ran up against an old headache that may be relevant. When you install a new distro, some of their installers will format the swap partition, thus changing its uuids.

This just happened to me and the result was systemd running a 90sec start job every boot. Am not a systemd guru by any means but learned enough now, that whenever this start job junk happens, checking fstab is 1st stop.

More fstab weirdness, the no new new line thing. Not sure if this ever caused a systemd start job but has caused boot probs. What's a new new line you may ask ? You go to the end of your last entry in fstab(with the cursor) and hit Return key to jump down to the next empty line in the file. You just made a new new line in fstab. Doubt this is your issue just being anal.

Might try deleting your present swap w gparted and create a new one in its place. Though yeah that means you'll have to correct fstab for it in all the on board os's.

Hope you get it sorted, an ailing gnu/nix install can cause someone much distress.

PS, another random thought, might upgrade systemd from backports presently v230-7etc. May not do a thing for your issue but for something as important as init I wanted newer. Working under the assumption that newer versions will have squashed bugs and added or polished features.

Deb-fan wrote:...Also just recently ran up against an old headache that may be relevant. When you install a new distro, some of their installers will format the swap partition, thus changing its uuids. ...

I had the same issue once. Easy fix once I worked out what the issue was. Edit fstab to reflect the new uuid as shown in blkid.journalctl was useful to detect the issue.

“ computer users can be divided into 2 categories:Those who have lost data...and those who have not lost data YET ”Remember toBACKUP!

Not me, but I can't speak for others,...I can say though, I have encountered the same/similar error, fortunately notvery often,...but in any event it has and can occur on non systemd systemsas well, Old Stable , Debian 7 wheezy,...I even have seen it on Debian 6

by sunrat » I had the same issue once. Easy fix once I worked out what the issue was. Edit fstab to reflect the new uuid as shown in blkid.journalctl was useful to detect the issue.

The same worked for me, but I did not have or use 'journalctl ' to detect it.

I did not ever see that particular error message until I was up to Jessie so, my WAG was a systemd behavior of some sort - obviously due to a startup configuration (likely hardware) the system was having a problem with...

EDIT: also, rather than editing /etc/fstab every time the swap partition is reformatted, the swap line can instead be removed for GPT drives and systemd will then automount the partition irrespective of the UUID.

"Men are born ignorant, not stupid. They are made stupid by education." — Bertrand Russell