You are not logged in.

Pages: 1

#1 2011-09-30 20:21:44

mbareko
Member
Registered: 2011-09-30
Posts: 4

[SOLVED] sdb devpath changing randomly causes thunar issues

I have 3 hdd's in my system. I had a problem with thunar, sometimes I boot my computer and thunar shows all my partitions and the usb drive in the left panel, and sometimes it shows nothing and wont show any usb drive either.

I noticed that this behavior was related to the devpath assigned to my drives at boot.

Everything works fine when sdb has devpath '/devices/pci0000:00/0000:00:11.0/host3/target3:0:0/3:0:0:0/block/sdb' and messages.log shows:

Sep 30 15:19:42 localhost kernel: [    1.120171] ata7: SATA link down (SStatus 0 SControl 300)
Sep 30 15:19:42 localhost kernel: [    1.120202] ata8: SATA link down (SStatus 0 SControl 300)
Sep 30 15:19:42 localhost kernel: [    1.283457] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 30 15:19:42 localhost kernel: [    1.284798] ata4.00: ATA-8: ST31000524AS, JC45, max UDMA/133
Sep 30 15:19:42 localhost kernel: [    1.284800] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
Sep 30 15:19:42 localhost kernel: [    1.286376] ata4.00: configured for UDMA/133
Sep 30 15:19:42 localhost kernel: [    1.286787] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 30 15:19:42 localhost kernel: [    1.286805] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 30 15:19:42 localhost kernel: [    1.288600] ata6.00: ATAPI: ASUS    DRW-24B1LT, 1.01, max UDMA/100
Sep 30 15:19:42 localhost kernel: [    1.289418] ata6.00: configured for UDMA/100
Sep 30 15:19:42 localhost kernel: [    1.290119] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 30 15:19:42 localhost kernel: [    1.291311] ata3.00: ATA-8: ST3500418AS, CC37, max UDMA/133
Sep 30 15:19:42 localhost kernel: [    1.291313] ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
Sep 30 15:19:42 localhost kernel: [    1.292710] ata3.00: configured for UDMA/133
Sep 30 15:19:42 localhost kernel: [    1.292857] scsi 2:0:0:0: Direct-Access     ATA      ST3500418AS      CC37 PQ: 0 ANSI: 5
Sep 30 15:19:42 localhost kernel: [    1.293044] scsi 3:0:0:0: Direct-Access     ATA      ST31000524AS     JC45 PQ: 0 ANSI: 5
Sep 30 15:19:42 localhost kernel: [    1.327670] ata5.00: ATA-7: ST3300822AS, 3.AAE, max UDMA/133
Sep 30 15:19:42 localhost kernel: [    1.327671] ata5.00: 586072368 sectors, multi 16: LBA48 NCQ (depth 31/32)
Sep 30 15:19:42 localhost kernel: [    1.385971] ata5.00: configured for UDMA/133
Sep 30 15:19:42 localhost kernel: [    1.386048] scsi 4:0:0:0: Direct-Access     ATA      ST3300822AS      3.AA PQ: 0 ANSI: 5
Sep 30 15:19:42 localhost kernel: [    1.388956] scsi 5:0:0:0: CD-ROM            ASUS     DRW-24B1LT       1.01 PQ: 0 ANSI: 5
Sep 30 15:19:42 localhost kernel: [    1.394041] sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Sep 30 15:19:42 localhost kernel: [    1.394072] sd 2:0:0:0: [sda] Write Protect is off
Sep 30 15:19:42 localhost kernel: [    1.394075] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Sep 30 15:19:42 localhost kernel: [    1.394092] sd 4:0:0:0: [sdc] 586072368 512-byte logical blocks: (300 GB/279 GiB)
Sep 30 15:19:42 localhost kernel: [    1.394095] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 30 15:19:42 localhost kernel: [    1.394107] sd 3:0:0:0: [sdb] Write Protect is off
Sep 30 15:19:42 localhost kernel: [    1.394123] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 30 15:19:42 localhost kernel: [    1.394127] sd 4:0:0:0: [sdc] Write Protect is off
Sep 30 15:19:42 localhost kernel: [    1.394140] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 30 15:19:42 localhost kernel: [    1.425615]  sdc: unknown partition table
Sep 30 15:19:42 localhost kernel: [    1.425790] sd 4:0:0:0: [sdc] Attached SCSI disk
Sep 30 15:19:42 localhost kernel: [    1.445901]  sda: sda1 sda2 sda3 sda4 < sda5 >
Sep 30 15:19:42 localhost kernel: [    1.446157] sd 2:0:0:0: [sda] Attached SCSI disk
Sep 30 15:19:42 localhost kernel: [    1.498062]  sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 >
Sep 30 15:19:42 localhost kernel: [    1.498321] sd 3:0:0:0: [sdb] Attached SCSI disk
Sep 30 15:19:42 localhost kernel: [    1.503320] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray

And have the thunar issue when sdb has devpath '/devices/pci0000:00/0000:00:11.0/host1/target1:0:0/1:0:0:0/block/sdb' and messages.log shows:

Sep 30 15:12:33 localhost kernel: [    1.113459] ata5: SATA link down (SStatus 0 SControl 300)
Sep 30 15:12:33 localhost kernel: [    1.113491] ata6: SATA link down (SStatus 0 SControl 300)
Sep 30 15:12:33 localhost kernel: [    1.153234] hub 7-0:1.0: USB hub found
Sep 30 15:12:33 localhost kernel: [    1.153239] hub 7-0:1.0: 2 ports detected
Sep 30 15:12:33 localhost kernel: [    1.153376] pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Sep 30 15:12:33 localhost kernel: [    1.153603] scsi6 : pata_atiixp
Sep 30 15:12:33 localhost kernel: [    1.153654] scsi7 : pata_atiixp
Sep 30 15:12:33 localhost kernel: [    1.154010] ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
Sep 30 15:12:33 localhost kernel: [    1.154011] ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
Sep 30 15:12:33 localhost kernel: [    1.276788] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 30 15:12:33 localhost kernel: [    1.277995] ata1.00: ATA-8: ST3500418AS, CC37, max UDMA/133
Sep 30 15:12:33 localhost kernel: [    1.277997] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
Sep 30 15:12:33 localhost kernel: [    1.279385] ata1.00: configured for UDMA/133
Sep 30 15:12:33 localhost kernel: [    1.279530] scsi 0:0:0:0: Direct-Access     ATA      ST3500418AS      CC37 PQ: 0 ANSI: 5
Sep 30 15:12:33 localhost kernel: [    1.280128] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 30 15:12:33 localhost kernel: [    1.281470] ata2.00: ATA-8: ST31000524AS, JC45, max UDMA/133
Sep 30 15:12:33 localhost kernel: [    1.281472] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
Sep 30 15:12:33 localhost kernel: [    1.283056] ata2.00: configured for UDMA/133
Sep 30 15:12:33 localhost kernel: [    1.283149] scsi 1:0:0:0: Direct-Access     ATA      ST31000524AS     JC45 PQ: 0 ANSI: 5
Sep 30 15:12:33 localhost kernel: [    1.283473] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 30 15:12:33 localhost kernel: [    1.286786] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 30 15:12:33 localhost kernel: [    1.288576] ata4.00: ATAPI: ASUS    DRW-24B1LT, 1.01, max UDMA/100
Sep 30 15:12:33 localhost kernel: [    1.289385] ata4.00: configured for UDMA/100
Sep 30 15:12:33 localhost kernel: [    1.326052] ata3.00: ATA-7: ST3300822AS, 3.AAE, max UDMA/133
Sep 30 15:12:33 localhost kernel: [    1.326053] ata3.00: 586072368 sectors, multi 16: LBA48 NCQ (depth 31/32)
Sep 30 15:12:33 localhost kernel: [    1.384352] ata3.00: configured for UDMA/133
Sep 30 15:12:33 localhost kernel: [    1.384463] scsi 2:0:0:0: Direct-Access     ATA      ST3300822AS      3.AA PQ: 0 ANSI: 5
Sep 30 15:12:33 localhost kernel: [    1.389766] scsi 3:0:0:0: CD-ROM            ASUS     DRW-24B1LT       1.01 PQ: 0 ANSI: 5
Sep 30 15:12:33 localhost kernel: [    1.394253] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Sep 30 15:12:33 localhost kernel: [    1.394262] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Sep 30 15:12:33 localhost kernel: [    1.394281] sd 0:0:0:0: [sda] Write Protect is off
Sep 30 15:12:33 localhost kernel: [    1.394286] sd 2:0:0:0: [sdc] 586072368 512-byte logical blocks: (300 GB/279 GiB)
Sep 30 15:12:33 localhost kernel: [    1.394294] sd 1:0:0:0: [sdb] Write Protect is off
Sep 30 15:12:33 localhost kernel: [    1.394298] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 30 15:12:33 localhost kernel: [    1.394313] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 30 15:12:33 localhost kernel: [    1.394318] sd 2:0:0:0: [sdc] Write Protect is off
Sep 30 15:12:33 localhost kernel: [    1.394331] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 30 15:12:33 localhost kernel: [    1.424025]  sdc: unknown partition table
Sep 30 15:12:33 localhost kernel: [    1.424195] sd 2:0:0:0: [sdc] Attached SCSI disk
Sep 30 15:12:33 localhost kernel: [    1.436166]  sda: sda1 sda2 sda3 sda4 < sda5 >
Sep 30 15:12:33 localhost kernel: [    1.436376] sd 0:0:0:0: [sda] Attached SCSI disk
Sep 30 15:12:33 localhost kernel: [    1.501182]  sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 >
Sep 30 15:12:33 localhost kernel: [    1.501445] sd 1:0:0:0: [sdb] Attached SCSI disk
Sep 30 15:12:33 localhost kernel: [    1.506599] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray

These are the only two configurations the system switches between, every boot randomly. I don't know when this started.

I know that because of udev, that uses parallelism at boot, devices letters may change every boot. This is not exactly the same case, but i thing is the same cause.

Is there a way to fix devpaths? Is this a thunar issue?

Thanks.

Last edited by mbareko (2011-10-07 15:56:45)

Offline

#2 2011-09-30 20:38:12

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: [SOLVED] sdb devpath changing randomly causes thunar issues

Do you have two devices on the PATA bus?  That would explain why the you're seeing two configurations: sometimes the PATA bus 'gets in first' and takes 0:0:0:0 and 1:0:0:0, so the SATA bus starts at 2:0:0:0 (that's Host:Channel:ID:LUN if you're curious).  Other times the SATA bus is first and takes 0:0:0:0 through 2:0:0:0.  The same thing happens on an Ubuntu Server box I have.  The console command cat /proc/scsi/scsi might make things a bit clearer.

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#3 2011-09-30 21:05:52

mbareko
Member
Registered: 2011-09-30
Posts: 4

Re: [SOLVED] sdb devpath changing randomly causes thunar issues

Thanks for your reply, but i dont have any devices on the PATA bus. I just disabled the PATA bus from he BIOS settings but i still have the problem. I ckecked /proc/scsi/scsi and got:

When there is no problem:

Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3500418AS      Rev: CC37
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST31000524AS     Rev: JC45
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3300822AS      Rev: 3.AA
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
  Vendor: ASUS     Model: DRW-24B1LT       Rev: 1.01
  Type:   CD-ROM                           ANSI  SCSI revision: 05

And with the issue:

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3500418AS      Rev: CC37
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST31000524AS     Rev: JC45
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3300822AS      Rev: 3.AA
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: ASUS     Model: DRW-24B1LT       Rev: 1.01
  Type:   CD-ROM                           ANSI  SCSI revision: 05

When there is no issue, host 0 is not shown in /proc/scsi/scsi. May be it was taken by another device. How can I see that?

Last edited by mbareko (2011-09-30 21:06:09)

Offline

#4 2011-09-30 21:47:02

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: [SOLVED] sdb devpath changing randomly causes thunar issues

Sorry, I forgot that even 'empty' ports (PATA and SATA) still take up a host number.  I would have thought disabling PATA would have solved it though.  OTOH, I have a crappy mobo at home that still presents a PATA bus even if it is disabled in the BIOS.

In any case, running dmesg | grep "scsi[0-9]" should show you what all the hosts are.  For example on my system:

$ dmesg | grep "scsi[0-9]"
[    1.191851] scsi0 : ahci
[    1.191990] scsi1 : ahci
[    1.192072] scsi2 : ahci
[    1.192145] scsi3 : ahci
[    3.895969] scsi4 : pata_amd
[    3.896043] scsi5 : pata_amd

Of course, this is all academic, as it probably won't help you solve your problem hmm

Last edited by alphaniner (2011-09-30 21:47:59)

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#5 2011-09-30 23:35:27

mbareko
Member
Registered: 2011-09-30
Posts: 4

Re: [SOLVED] sdb devpath changing randomly causes thunar issues

Maybe you were right alphaniner, look at this:

The configuration that works

$ dmesg | grep "scsi[0-9]"
[    0.790590] scsi0 : pata_atiixp
[    0.790661] scsi1 : pata_atiixp
[    0.791978] scsi2 : ahci
[    0.792031] scsi3 : ahci
[    0.792079] scsi4 : ahci
[    0.792127] scsi5 : ahci
[    0.792175] scsi6 : ahci
[    0.792222] scsi7 : ahci
[    1.386649] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    3.776090] scsi8 : usb-storage 1-1:1.0

reboot...
The config that doesn't:

$ dmesg | grep "scsi[0-9]"
[    0.794439] scsi0 : ahci
[    0.794515] scsi1 : ahci
[    0.794561] scsi2 : ahci
[    0.794639] scsi3 : ahci
[    0.794700] scsi4 : ahci
[    0.794759] scsi5 : ahci
[    0.795081] scsi6 : pata_atiixp
[    0.795146] scsi7 : pata_atiixp
[    1.403221] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    3.983007] scsi8 : usb-storage 1-1:1.0

Even disabling PATA bus, I have the same problem.

Running thunar from console trows this when I plug my USB memory stick, (when everything is working ok):

$ dbus-launch thunar
libudev: udev_device_new_from_syspath: device 0xb511c0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1'
libudev: udev_device_read_db: device 0xb511c0 filled with db file data
thunar-volman: Unsupported USB device type.
libudev: udev_device_new_from_syspath: device 0x1c7c1c0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0'
libudev: udev_device_read_db: no db file to read /run/udev/data/+usb:1-1:1.0: No such file or directory
thunar-volman: Unsupported USB device type.
libudev: udev_device_new_from_syspath: device 0xa7c1a0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host11/target11:0:0/11:0:0:0/block/sdd'
libudev: udev_device_read_db: device 0xa7c1a0 filled with db file data
thunar-volman: Unknown block device type.
libudev: udev_device_new_from_syspath: device 0xae41a0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host11/target11:0:0/11:0:0:0/block/sdd/sdd1'
libudev: udev_device_read_db: device 0xae41a0 filled with db file data
thunar-volman: /dev/sdd1 is mounted.

With the issue:

$ dbus-launch thunar
(thunar-volman:1402): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
libudev: udev_device_read_db: device 0xebc1c0 filled with db file data
thunar-volman: Unsupported USB device type.
libudev: udev_device_new_from_syspath: device 0xa451c0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0'

(thunar-volman:1414): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
libudev: udev_device_read_db: no db file to read /run/udev/data/+usb:1-1:1.0: No such file or directory
thunar-volman: Unsupported USB device type.
libudev: udev_device_new_from_syspath: device 0x24a71a0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host10/target10:0:0/10:0:0:0/block/sdd'

(thunar-volman:1423): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
libudev: udev_device_read_db: device 0x24a71a0 filled with db file data
thunar-volman: Unknown block device type.
libudev: udev_device_new_from_syspath: device 0x6fb1a0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host10/target10:0:0/10:0:0:0/block/sdd/sdd1'

(thunar-volman:1432): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
libudev: udev_device_read_db: device 0x6fb1a0 filled with db file data
thunar-volman: Could not detect the volume corresponding to the device.

I don't know if this is an issue with gvfs, thunar's volman or udev, may be PolicyKit too.

I have 'exec ck-launch-session dbus-launch startxfce4' in my .xinitrc. I don't know...

Offline

#6 2011-10-03 13:30:20

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: [SOLVED] sdb devpath changing randomly causes thunar issues

Edit (Oct 6):

Check out this thread, I think his solution will work for you.

---

Archwiki to the rescue (maybe): Presistent block device naming

If that doesn't work, I think you could just blacklist the module for your IDE bus.  That'd probably be the quickest solution, if not for the fact that your 'working config' has IDE in first.  So you'd still have to figure out how to solve the thunar issue.  The xfce forums would probably be the best place for that.

Last edited by alphaniner (2011-10-06 19:57:10)

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#7 2011-10-07 15:56:22

mbareko
Member
Registered: 2011-09-30
Posts: 4

Re: [SOLVED] sdb devpath changing randomly causes thunar issues

Ok, I think I solved it. After 3 days and several booting, the problem has gone.

I blacklisted the module for the IDE bus, but it didn't work, because my system works fine when the PATA module is loaded first. So blacklisting it make the issue permanent.
Persistent device naming didn't work either. I didn't have the problems identified in the article. But reading it made me understand a little better how mkinitcpio works.

So the solution for me was:

1.- Add to the "MODULES" array in /etc/mkinitcpio.conf the two modules in conflict, in the order I wanted them to load. (pata_atiixp, then ahci). So the system always sets up first the PATA bus and then SATA buses.
2.- Runing mkinitcpio to generate a new initial ramdisk, with the configurations needed.

Thank you alphaniner!

Offline

Pages: 1

Board footer

Powered by FluxBB