a start job is running for dev-disk-by\x2uuid...

If none of the more specific forums is the right place to ask

a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-06 03:16

Hello.
I'm getting this messages every time i start the pc:

a start job is running for dev-disk-by\x2uuid-xxxx

a start job is running for Load/Save RF Kill Switch status of rfkill0

And some other like those. (Don't know how to load the photos i took of the screen.)

I don't know what kind of information should i give you to help you help me. But i read it could be something about fstab. So, in case it helps...

The output of blkid
Code: Select all
root@debtest:/home/canelon3# blkid
/dev/sda1: UUID="99f355a2-d84f-4b95-9497-9650e3aeb7b1" TYPE="ext4" PARTUUID="2c81e484-01"
/dev/sda2: UUID="2c67147b-69bd-40b9-8a1f-1a3765a4f856" TYPE="swap" PARTUUID="2c81e484-02"
/dev/sda5: UUID="7ce7f2ae-d2ea-4226-97ae-721475f6f95f" TYPE="ext4" PARTUUID="2c81e484-05"
/dev/sda6: LABEL="tester" UUID="32991fd0-f76d-458f-b7be-5e6a2ddc8610" TYPE="ext4" PARTUUID="2c81e484-06"
/dev/sda7: UUID="4274728a-bdb1-42f2-b8b8-5e8f0ea9589b" TYPE="ext4" PARTUUID="2c81e484-07"
/dev/sdb1: LABEL="TOSHIBA EXT" UUID="0416A85816A84D0C" TYPE="ntfs" PARTUUID="1f47d99e-01"


And this is my fstab
Code: Select all
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda6 during installation
UUID=32991fd0-f76d-458f-b7be-5e6a2ddc8610 /               ext4    errors=remoun$
# /home was on /dev/sda7 during installation
UUID=4274728a-bdb1-42f2-b8b8-5e8f0ea9589b /home           ext4    defaults     $
# swap was on /dev/sda2 during installation
UUID=2c67147b-69bd-40b9-8a1f-1a3765a4f856 none            swap    sw           $
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0


Thank you.
Laurentius

Debian Jessie.
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby debiman » 2017-03-06 06:31

are you booting into a usable system?

we really need full error messages.

journalctl output would help better than screenshots, but maybe it is not enabled by default.
anyhow, try:
Code: Select all
journalctl -b
User avatar
debiman
 
Posts: 820
Joined: 2013-03-12 07:18

Re: a start job is running for dev-disk-by\x2uuid...

Postby kedaha » 2017-03-06 08:03

Hi,
I used to get this in both stable and testing —but not in unstable— so I commented out the swap entry in fstab as posted by Head_on_a_Stick here
So you might try commenting out yours, i.e., by placing a # before the swap line for /dev/sda2 in fstab.
User avatar
kedaha
 
Posts: 2589
Joined: 2008-05-24 12:26

Re: a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-06 17:55

Hi.
Well, i have some problems, but the system is usable. May be i will reinstall when stretch is published.

Here is the output
Code: Select all
canelon3@debtest:~$ journalctl -b
No journal files were found.
canelon3@debtest:~$
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby bw123 » 2017-03-06 18:07

a start job is running for dev-disk-by\x2uuid-xxxx


Does the uuid in the error message match one of the devices listed in the blkid output? Looks like you have 1,2,5,6,7 what happened to partitions 3 and 4? What app created those partuuids anyway?

I think you need to be root to look at the journalctl files. I have no idea why... this is somewhat obscured in a oneliner in about the 5th paragraph of the man page.
jessie/KDE4.14.2 plasma netbook, 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
User avatar
bw123
 
Posts: 2378
Joined: 2011-05-09 06:02
Location: TN_USA

Re: a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-06 19:57

Yes, the uuid in the error messages matches the home partition (sda7) as is listed in blkid.
Here i show three lines: 1) is the blkid line that represents /home 2) is the fstab line for /home and 3) is the error message as i can see it in the photograph i took. That message appears 3 or 4 times before the boot secuence continues with "ok's"

1)Blkid
# /home was on /dev/sda7 during installation
UUID=4274728a-bdb1-42f2-b8b8-5e8f0ea9589b /home ext4 defaults $

2)fstab
/dev/sda7: UUID="4274728a-bdb1-42f2-b8b8-5e8f0ea9589b" TYPE="ext4" PARTUUID="2c81e484-07"

3)error message
x2duuid-4274728a\x2dbdb1\x2d42f2x2db8b8\x2d5e8f0ea9589b.device

Partition #3 is an Extended partition where logical partitions 5, 6, 7 are located. Don't know why there is no #4 partition.
I usually use gparted to partition disks before installing a linux distro.

if i run journalctl -b as root, the output is endless.

Thanks.

PS: Here is my parition history:
When i first prepared the disk for installing debian (using gparted from a live os), following the advice of debian wiki i left partition #1 for /boot, #2 for swap, #5 for debian, #6 for distro hopping and #7 for /home.
And i installed debian as expected and it worked fine. But then i installed manjaro on #6 and could not boot into debian anymore (kernel panic or smthg). After trying some things (installing debian again without being able to boot in manjaro...etc) i thought the problem was that i didn't know how to work with a separate /boot partition. So i installed debian again on #6 without using sda1 as a separate /boot and just use /, /home and swap. Then i have installed xubuntu on #5 without using a separate /boot. And now i can boot both systems.
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby Head_on_a_Stick » 2017-03-06 21:08

Laurentius wrote:Here is the output
Code: Select all
canelon3@debtest:~$ journalctl -b
No journal files were found.
canelon3@debtest:~$

To access the systemd journal, add your user to the requisite group:
Code: Select all
# gpasswd -a canelon3 systemd-journal

Then log out & back in again and post the output of:
Code: Select all
journalctl -u x2duuid-4274728a\x2dbdb1\x2d42f2x2db8b8\x2d5e8f0ea9589b.device

If that doesn't work then the entire `journalctl -b` will have to do.
“Such is modern computing: everything simple is made too complicated because it’s easy to fiddle with; everything complicated stays complicated because it’s hard to fix." — Rob Pike

Please read before posting How to report a problem
User avatar
Head_on_a_Stick
 
Posts: 6413
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-06 23:43

The output after # gpasswd -a canelon3 systemd-journal:

Code: Select all
canelon3@debtest:~$ journalctl -u x2duuid-4274728a\x2dbdb1\x2d42f2x2db8b8\x2d5e8f0ea9589b.device
-- Logs begin at lun 2017-03-06 20:28:06 ART, end at lun 2017-03-06 21:25:24 ART. --
canelon3@debtest:~$


Now, the output of journalctl -b as $user is as endless as #root
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby Head_on_a_Stick » 2017-03-07 07:10

“Such is modern computing: everything simple is made too complicated because it’s easy to fiddle with; everything complicated stays complicated because it’s hard to fix." — Rob Pike

Please read before posting How to report a problem
User avatar
Head_on_a_Stick
 
Posts: 6413
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-07 12:56

guess that link is to paste the output.
the output of
Code: Select all
journalctl -b >> journal-output.txt
is a text file with 1596 lines.
the server does't allow me to paste that ammount of data, even if i select "wrap to 78 caracters"
it doesn't allow me to attach the .txt file neither

so, i could paste the firt 23 lines (first page) of the journalctl -b output directly from the terminal:
https://paste.debian.net/918584
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby debiman » 2017-03-10 05:41

entry was deleted since.
if
Code: Select all
journalctl -u x2duuid-4274728a\x2dbdb1\x2d42f2x2db8b8\x2d5e8f0ea9589b.device
did not produce the desired result (as i'm sure you realised), you can always try something like this:
Code: Select all
journalctl -b | grep device
journalctl -b | grep uuid
journalctl -b | grep 5e8f0ea9589b
and make an informed choice what entries might be relevant to your problem, then share them with us.

please don't make this harder than it has to be.
we ARE trying to help, don't you realise that?
User avatar
debiman
 
Posts: 820
Joined: 2013-03-12 07:18

Re: a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-12 19:31

i really don't know yet what kind of results should i expect. But i'm looking for information about it.

would de journalctl command output be useful if the problem doesn't appear, i mean on a "sane" boot?
In the last boot it did not.Sometimes it does (mostly), sometimes not.
So, i think i will expect till it appear to analyze the outputs.
One thing i've done was to comment (#) the swap line on the /etc/fstab as i realized that it's uuid was appearing in the "start job is running..." error message too.
Since then, i've only seen the uuid that matches for /home in the error message but also, i have no more swap avaiable. So, i think i will uncomment the fstab line.


i'm having another issues. i point them just in case they are related (but i don't think so)
1) One is the kworker prcocess hogging my pc (i'm triyng to find out why in other thread)
Sometimes it starts at system startup. Sometimes some hours after startup.
Once it appears i have no way to solve it. Only restarting.

2) Another one is an odd behaviour with the usb Genius optical mouse. Sometimes it stop working on some usb ports (while there's no problem with the usb ports for any other devices, e.g. usb-sticks, hard drive, phone, etc.) The workaround i found is to unplug it, then plug it in/out on onother usb (where it does not work neither) and then plug it again on the usb port where it mostly works. Weird eh?
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby bw123 » 2017-03-12 19:56

i have no more swap avaiable. So, i think i will uncomment the fstab line.


use mkswap on it first, you can keep the uuid the same if you want, see man mkswap.

systemd should still be mounting it if it is valid?

man systemd.swap
jessie/KDE4.14.2 plasma netbook, 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
User avatar
bw123
 
Posts: 2378
Joined: 2011-05-09 06:02
Location: TN_USA

Re: a start job is running for dev-disk-by\x2uuid...

Postby Laurentius » 2017-03-12 22:26

Ok, thanks bw123. I'll try mkswap then. Meanwhile I mount it manually with $sudo swapon /dev/sda2.

But now, as i had to restart to stop kworker before it fried my processor, and the "start job is running..." error appeared again for the /home uuid at boot, i went over with the journalctl command.
Here is what i found could be relevant from the output of $journalctl -b | grep device:

Code: Select all
mar 12 18:05:57 debtest kernel: input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input6
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest kernel: ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:05:57 debtest systemd[1]: Expecting device dev-disk-by\x2duuid-4274728a\x2dbdb1\x2d42f2\x2db8b8\x2d5e8f0ea9589b.device...
mar 12 18:05:57 debtest systemd[1]: Starting Create list of required static device nodes for the current kernel...
mar 12 18:05:57 debtest systemd[1]: Started Create list of required static device nodes for the current kernel.
mar 12 18:05:57 debtest kernel: lp: driver loaded but no devices found

(...)

mar 12 18:05:58 debtest kernel: input: MCE IR Keyboard/Mouse (ene_ir) as /devices/virtual/input/input10
mar 12 18:05:59 debtest kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mar 12 18:05:59 debtest kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mar 12 18:05:59 debtest kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mar 12 18:05:59 debtest kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
mar 12 18:05:59 debtest kernel: input: PC Speaker as /devices/platform/pcspkr/input/input11

(...)

mar 12 18:06:30 debtest systemd-udevd[234]: timeout 'lmt-udev force modules=runtime-pm devices=8-5'
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
mar 12 18:06:31 debtest kernel: ata1.00: device reported invalid CHS sector 0
mar 12 18:06:31 debtest kernel: ata1.00: device reported invalid CHS sector 0
mar 12 18:06:31 debtest kernel: ata1.00: device reported invalid CHS sector 0
mar 12 18:06:31 debtest kernel: ata1.00: device reported invalid CHS sector 0
mar 12 18:06:31 debtest kernel: ata1.00: device reported invalid CHS sector 0
mar 12 18:06:31 debtest kernel: ata1.00: device reported invalid CHS sector 0
mar 12 18:06:31 debtest systemd-udevd[238]: timeout 'lmt-udev force modules=runtime-pm devices=1-1'


There seems to be some trouble with ata1.00 and ata5.00
May be i should look for a driver for ACPI.

Then, this is what may be relevant in the output of dmesg, where we find again the same ata1.00 problems (or what it seem to be)

Code: Select all
[   47.803001] WARNING! power/level is deprecated; use power/control instead
[   47.844057] ata1.00: exception Emask 0x0 SAct 0x3f0 SErr 0x0 action 0x6 frozen
[   47.844127] ata1.00: failed command: READ FPDMA QUEUED
[   47.844178] ata1.00: cmd 60/68:20:70:e4:47/00:00:03:00:00/40 tag 4 ncq 53248 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   47.844296] ata1.00: status: { DRDY }
[   47.844328] ata1.00: failed command: READ FPDMA QUEUED
[   47.844375] ata1.00: cmd 60/18:28:90:a9:5b/00:00:03:00:00/40 tag 5 ncq 12288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   47.844494] ata1.00: status: { DRDY }
[   47.844525] ata1.00: failed command: READ FPDMA QUEUED
[   47.844572] ata1.00: cmd 60/08:30:58:1c:6b/00:00:03:00:00/40 tag 6 ncq 4096 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   47.844694] ata1.00: status: { DRDY }
[   47.844726] ata1.00: failed command: READ FPDMA QUEUED
[   47.844777] ata1.00: cmd 60/e0:38:08:0f:a4/00:00:03:00:00/40 tag 7 ncq 114688 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   47.844897] ata1.00: status: { DRDY }
[   47.844928] ata1.00: failed command: READ FPDMA QUEUED
[   47.844975] ata1.00: cmd 60/08:40:d8:bf:c7/00:00:03:00:00/40 tag 8 ncq 4096 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   47.845094] ata1.00: status: { DRDY }
[   47.845125] ata1.00: failed command: READ FPDMA QUEUED
[   47.845173] ata1.00: cmd 60/00:48:78:37:58/01:00:02:00:00/40 tag 9 ncq 131072 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   47.845294] ata1.00: status: { DRDY }
[   47.845327] ata1: hard resetting link
[   48.336047] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   48.339107] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[   48.339317] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[   48.339415] ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded
[   48.339421] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   48.339628] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[   48.339837] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[   48.349271] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[   48.349500] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[   48.349503] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   48.349723] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[   48.349928] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[   48.353624] ata1.00: configured for UDMA/133
[   48.353629] ata1.00: device reported invalid CHS sector 0
[   48.353632] ata1.00: device reported invalid CHS sector 0
[   48.353634] ata1.00: device reported invalid CHS sector 0
[   48.353637] ata1.00: device reported invalid CHS sector 0
[   48.353639] ata1.00: device reported invalid CHS sector 0
[   48.353642] ata1.00: device reported invalid CHS sector 0
[   48.353665] ata1: EH complete


I don't see much on the output of $journalctl -b | grep uuid

Code: Select all
canelon3@debtest:~$ journalctl -b | grep uuid
mar 12 18:05:57 debtest systemd[1]: Expecting device dev-disk-by\x2duuid-4274728a\x2dbdb1\x2d42f2\x2db8b8\x2d5e8f0ea9589b.device...
mar 12 18:06:33 debtest systemd[1]: Starting File System Check on /dev/disk/by-uuid/4274728a-bdb1-42f2-b8b8-5e8f0ea9589b...
mar 12 18:06:35 debtest systemd[1]: Started File System Check on /dev/disk/by-uuid/4274728a-bdb1-42f2-b8b8-5e8f0ea9589b.
mar 12 18:10:53 debtest gnome-session[2384]: (tracker-extract:2651): Tracker-WARNING **: Task 0, error: Unable to insert multiple values for subject `urn:uuid:0af576ab-4496-6625-5e14-b5a0c16608a7' and single valued property `dc:identifier' (old_value: 'urn:uuid:7a2d48bd-8125-d1e2-f270-732b3f1c8b53', new value: '978-84-670-3478-3')
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:0af576ab-4496-6625-5e14-b5a0c16608a7> nie:dataSource <http://www.tracker-project.org/ontologies/tracker#extractor-data-source> .
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:0af576ab-4496-6625-5e14-b5a0c16608a7> a nfo:EBook ;
mar 12 18:10:53 debtest gnome-session[2384]: nie:identifier "urn:uuid:7a2d48bd-8125-d1e2-f270-732b3f1c8b53" ;
mar 12 18:10:53 debtest gnome-session[2384]: (tracker-extract:2651): Tracker-WARNING **: Task 1, error: Unable to insert multiple values for subject `urn:uuid:66431af7-c465-1340-4946-6297652cee52' and single valued property `dc:identifier' (old_value: 'awp2011-09-02T18:19:25Z', new value: '84-473-3902-5')
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:66431af7-c465-1340-4946-6297652cee52> nie:dataSource <http://www.tracker-project.org/ontologies/tracker#extractor-data-source> .
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:66431af7-c465-1340-4946-6297652cee52> a nfo:EBook ;
mar 12 18:10:53 debtest gnome-session[2384]: (tracker-extract:2651): Tracker-WARNING **: Task 2, error: Unable to insert multiple values for subject `urn:uuid:9d3b054d-e0f6-feb3-3fae-6035c718f7ac' and single valued property `dc:identifier' (old_value: 'urn:uuid:a681a441-471a-404c-a363-0572dfcd6e01', new value: '9788434501782')
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:9d3b054d-e0f6-feb3-3fae-6035c718f7ac> nie:dataSource <http://www.tracker-project.org/ontologies/tracker#extractor-data-source> .
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:9d3b054d-e0f6-feb3-3fae-6035c718f7ac> a nfo:EBook ;
mar 12 18:10:53 debtest gnome-session[2384]: nie:identifier "urn:uuid:a681a441-471a-404c-a363-0572dfcd6e01" ;
mar 12 18:10:53 debtest gnome-session[2384]: (tracker-extract:2651): Tracker-WARNING **: Task 3, error: Unable to insert multiple values for subject `urn:uuid:89814c73-7f1a-d8a1-be68-914dc9e4763b' and single valued property `dc:identifier' (old_value: 'urn:uuid:2267d5fd-30cd-48ac-a7a2-466bd64e1a44', new value: '978-84-670-3505-6')
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: GRAPH <urn:uuid:472ed0cc-40ff-4e37-9c0c-062d78656540> {
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:89814c73-7f1a-d8a1-be68-914dc9e4763b> nie:dataSource <http://www.tracker-project.org/ontologies/tracker#extractor-data-source> .
mar 12 18:10:53 debtest gnome-session[2384]: <urn:uuid:89814c73-7f1a-d8a1-be68-914dc9e4763b> a nfo:EBook ;
mar 12 18:10:53 debtest gnome-session[2384]: nie:identifier "urn:uuid:2267d5fd-30cd-48ac-a7a2-466bd64e1a44" ;
canelon3@debtest:~$


Hope this could tell you something meaningfull.

Thank you.
Laurentius
 
Posts: 21
Joined: 2017-01-14 00:52

Re: a start job is running for dev-disk-by\x2uuid...

Postby bw123 » 2017-03-12 22:30

status: { DRDY }
[ 47.844328] ata1.00: failed command: READ FPDMA QUEUED


Sure looks like a failing drive to me. I had one start that stuff and I zeroed it out but that only got a couple of weeks out of it.

If you have smartmontools you can get some more info, like hours in use, and other errors

just for curiosity, what drive is it? If it's ide, you might hear it clicking as it spins up occasionally? or maybe a <clunk> at boot time, or now and then?

this kind of command might tell more.

Code: Select all
$ dmesg | grep -A8 ', max U'
jessie/KDE4.14.2 plasma netbook, 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
User avatar
bw123
 
Posts: 2378
Joined: 2011-05-09 06:02
Location: TN_USA

Next

Return to General Questions

Who is online

Users browsing this forum: No registered users and 8 guests

fashionable