I am trying to do an upgrade

English Install/Boot/Login
#21

That’s irrelevant.
External drives are not added automatically to the fstab by the installer, and especially not when doing an upgrade.

I looked in Yast and using Partition, Yast sees the device (sdf1), but it is not mounted. When I looked at doing the mount, I did not have an option to mount it where the other devices were mounted. “/run/media/hexdump”. My options were /usr/local or /srv.

You don’t have to choose anything from the list, you can enter anything you like.

But /run/media is used by the desktop to mount partitions. Click on the drive in dolphin or the device manager (if using KDE) and it should be mounted to /run/media. And you can set it to be mounted automatically in the device manager’s settings.
This is not a system thing you can configure with YaST. YaST allows to add entries to the fstab, to mount a drive systemwide during boot e.g.

Also, I would prefer a permanent solution, not a command line option that I would have to key in after every reboot.

Well, I already told you two options: add it to the fstab (via YaST e.g.), or set it to be mounted automatically in KDE’s settings.
But be careful: if you add it to the fstab, your system will not boot if it is not connected/turned on. You should better add the “nofail” mount option in that case.
But as your other drives are mounted to /run/media, you seem to use the desktop’s method there, so you should use that method with this drive as well I’d say.

#22

It seemed relevent to me in the other USB device is mounted ok and did not disappear during the upgrade and is not in fstab. So somehow opensuse remembered it but did not remember the WD500. That was what I was trying to figure out.

Dolphin shows the drive but I get this error when I click on it.

 An error occurred while accessing 'WD500', the system responded: The requested operation has failed: Error mounting /dev/sdf1 at /run/media/hexdump/WD500: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdf1" "/run/media/hexdump/WD500"' exited with non-zero exit status 32: mount: /dev/sdf1 is already mounted or /run/media/hexdump/WD500 busy

[/QUOTE]
Well, the fstab option seems to not be a good thing since it is a USB device and potentially will not be present at boot.
So this seems preferrable “or set it to be mounted automatically in KDE’s settings.”
Now would you kindly tell me how to do this.

Regards

#23

But it is irrelevant whether the drive was connected/powered on during the upgrade or not.

What are your KDE auto-mount settings anyway?
Do you have auto-mount turned on for all drives? Then it’s also irrelevant whether “opensuse remembered it” or not.

Dolphin shows the drive but I get this error when I click on it.

 An error occurred while accessing 'WD500', the system responded: The requested operation has failed: Error mounting /dev/sdf1 at /run/media/hexdump/WD500: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdf1" "/run/media/hexdump/WD500"' exited with non-zero exit status 32: mount: /dev/sdf1 is already mounted or /run/media/hexdump/WD500 busy

And that’s the reason why it cannot be mounted.

It either is mounted already, or the mount point /run/media/hexdump/WD500 is already in use by something else.
Can you post the output of “mount” again?
Does it work after a reboot?

Well, the fstab option seems to not be a good thing since it is a USB device and potentially will not be present at boot.
So this seems preferrable “or set it to be mounted automatically in KDE’s settings.”
Now would you kindly tell me how to do this.

Like you did for your other drives… :stuck_out_tongue:
Open KDE’s settings and choose “Removable Devices”, or right-click on the device notifier applet in the system tray and choose “Device Notifier Settings”.
You should be able to configure auto-mounting for your drive there.

But something else seems to go wrong.

#24

Output of the mount command and I am going to go look around for the other suggestions you have made. After I reboot.
I’ll be back later. :=)

hexdump@Corky-PC:~> mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=1891532k,nr_inodes=472883,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
/dev/sda2 on / type ext4 (rw,noatime,discard,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,noatime)
tmpfs on /var/log type tmpfs (rw,noatime)
/dev/sdb2 on /sdb/sdb2 type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /home type ext4 (rw,relatime,data=ordered)
/dev/sr0 on /run/media/hexdump/openSUSE-13.2-DVD-x86_640051 type iso9660 (ro,nosuid,nodev,relatime,uid=1000,gid=100,iocharset=utf8,mode=0400,dmode=0500,uhelper=udisks2)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
/dev/sda3 on /run/media/hexdump/a6b719f8-bf8e-427e-906b-3bc568112603 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/sdb5 on /run/media/hexdump/7ce5c1b1-42f1-4618-8a02-30f8df4410c6 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/sdg1 on /run/media/hexdump/STORE N GO type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
hexdump@Corky-PC:~>
#25

Rebooting did not solve anything.
I went into configure desktop/removable devices and this is what it looks like.
The Store-N-Go is another USB device and works properly.
The 465.8 GIB Removable Media and WD500 are the same USB device and do not work correctly.
As part of rebooting, with the WD500 device powered off, I booted up into Elementary linux, powered on the WD500 and the device worked correctly.
I tried the same thing only booting into openSuse 13.1 and I got the error again in Dolphin. Only the dev is now sdi rather than sdd or sdg as it was before.
Very strange.

http://i57.tinypic.com/2ynnqzd.png

#26

Yes, the device name changes depending on what devices are connected already and in which order they are detected. That’s the reason why it’s normally not a good idea to use the device name, but rather the UUID or label.

So your problem is that the device cannot be mounted at all. And therefore it also cannot be auto-mounted of course.

According to your settings, all drives should be auto-mounted, so no need to explicitely change/configure anything.

Please type this into a terminal window and post the output: (change sdf1 with the actual device name if it is different now)

udisksctl mount -b /dev/sdf1

Can you mount the drive normally?

sudo mount /dev/sdf1 /mnt

(you can unmount it afterwords either with dolphin or with “sudo umount /mnt”)

What filesystem is actually on the drive?

sudo lsblk -f
#27

Ok, here are the results

hexdump@Corky-PC:~> udisksctl mount -b /dev/sdi1
Error mounting /dev/sdi1: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdi1 at /run/media/hexdump/WD500: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdi1" "/run/media/hexdump/WD500"' exited with non-zero exit status 32: mount: /dev/sdi1 is already mounted or /run/media/hexdump/WD500 busy


hexdump@Corky-PC:~> 
hexdump@Corky-PC:~> sudo mount /dev/sdi1 /mnt


We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:


    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.


root's password:
mount: /dev/sdi1 is already mounted or /mnt busy

hexdump@Corky-PC:~> sudo lsblk -f

NAME   FSTYPE          LABEL      UUID                                 MOUNTPOINT
sda                                                                    
├─sda1 swap                       33f69041-2406-4037-9e14-1efcd4744453 [SWAP]
├─sda2 ext4                       751c8e22-0eb3-4e3d-b4fd-ea5f34310149 /
└─sda3 ext4                       a6b719f8-bf8e-427e-906b-3bc568112603 
sdb                                                                    
├─sdb1 ext4                       0f7d80e1-01bb-4331-bdf9-33bb5d7b3abb /home
├─sdb2 ext4                       7f73ea84-f1f2-491e-aebb-9f16734df7a6 /sdb/sdb2
├─sdb3                                                                 
├─sdb5 ext4                       7ce5c1b1-42f1-4618-8a02-30f8df4410c6 
└─sdb6 swap                       91f22007-4e54-46a8-82c1-6cc09d62084c 
sdf                                                                    
└─sdf1 vfat            STORE N GO B4A0-8F2C                            /run/media/hexdump/STORE N GO
sdi    isw_raid_member                                                 
└─sdi1 ext4            WD500      cb893780-7a01-491c-a73a-83af2ca3a478 
sr0                                                                    
hexdump@Corky-PC:~>
#28

That’s strange. Both say it is mounted already, but it doesn’t seem to be?

What happens when you run “sudo umount /dev/sdi1” to unmount it?

Might be that it is being mounted, but somehow the mount process hangs or something like that…

Can you disable Auto-mounting completely for a test, reboot, and try to mount it manually again? (i.e. “sudo mount /dev/sdi1”)
And please also post the output of “dmesg|tail” afterwards.

#29

Apparently, overnight or after the reboot, the device changed to sdd so here goes


What happens when you run "sudo umount /dev/sdi1" to unmount it?
hexdump@Corky-PC:~> sudo umount /dev/sdd1
umount: /dev/sdd1: not mounted



Can you disable Auto-mounting completely for a test, reboot, and try to mount it manually again? (i.e. "sudo mount /dev/sdi1")
hexdump@Corky-PC:~> sudo mount /dev/sdd1
mount: can't find /dev/sdd1 in /etc/fstab
hexdump@Corky-PC:~> 



And please also post the output of "dmesg|tail" afterwards
hexdump@Corky-PC:~> dmesg|tail
  490.444304] IT8718 SuperIO detected.
  490.450161] lp: driver loaded but no devices found
  492.708704] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
  492.708710] EDD information not available.
  494.838431] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
  494.838436] EDD information not available.
  603.233346] perf interrupt took too long (5012 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
  807.715209]  sdd: sdd1
  809.694208] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
  809.694212] EDD information not available.
hexdump@Corky-PC:~>

I verified that automount is off and I discovered the new sdd assigned, by running partitioner in Yast.

And again when I started Dolphin, at first there was no entry for WD500, then when I came back to it about 15 minutes later, it is listed and also gives this error message.

An error occurred while accessing 'WD500', the system responded: The requested operation has failed: Error mounting /dev/sdd1 at /run/media/hexdump/WD500: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdd1" "/run/media/hexdump/WD500"' exited with non-zero exit status 32: mount: /dev/sdd1 is already mounted or /run/media/hexdump/WD500 busy
#30

As I said, the device name will change “randomly”.

What happens when you run “sudo umount /dev/sdi1” to unmount it?
hexdump@Corky-PC:~> sudo umount /dev/sdd1
umount: /dev/sdd1: not mounted

Ok, so it is not mounted at this point.


Can you disable Auto-mounting completely for a test, reboot, and try to mount it manually again? (i.e. "sudo mount /dev/sdi1")
hexdump@Corky-PC:~> sudo mount /dev/sdd1
mount: can't find /dev/sdd1 in /etc/fstab
hexdump@Corky-PC:~>

In this case you’d need “sudo umount /dev/sdd1 /mnt”. Sorry for not being clear enough.

So please try that again, and post “dmesg|tail” afterwards.

And please, also post the output of “dmesg|tail” directly after connecting the drive.

And again when I started Dolphin, at first there was no entry for WD500, then when I came back to it about 15 minutes later, it is listed and also gives this error message.

Hm?
The entry in dolphin should be there regardless whether it’s mounted or not.

This would rather sound like the device is appearing/disappearing/reappearing all the time or similar.

Can you try to connect it to a different USB port maybe?
Can you verify that it still works with a different computer/operating system?
This would sound like a hardware issue IMHO… (could be a driver/kernel issue as well of course)

#31

In this case you’d need “sudo umount /dev/sdd1 /mnt”. Sorry for not being clear enough.

So please try that again, and post “dmesg|tail” afterwards.

hexdump@Corky-PC:~> sudo umount /dev/sdd1 /mnt
root's password:
umount: /dev/sdd1: not mounted
umount: /mnt: not mounted
hexdump@Corky-PC:~> sudo umount /dev/sdd1 /mnt

Also, I started up dolphin, WD500 was there, and as I turned off the drive, WD500 disappeared from Dolphin, as I expected.

I dismounted and removed my other USB stick and put it into the suspicious USB port and it worked properly.
I put the WDC500 drive into the known good USB port and in Dolphin it does not show up as I power it on. It will probably show up after a few minutes and probably give me an error.

The device is now sdh1 as shown in partioner.

I rebooted into Elementary linux and the device works correctly.

I did not do the “dmesg|tail” as it appears that the command “sudo umount /dev/sdd1 /mnt” has a syntax error.

WDC500 shows up in Dolphin about 8 minutes after I turn it on.

During my poking around, I noticed that it seems like Linux keeps a record of devices in at least 4 ways:

  1. by label
  2. by uuid
  3. by id
  4. by path.

Can those get out of sync and what happens if they do ?
Is there a way to remove all references to this device and start it fresh ?

thanks again

#32

It is “sudo mount /dev/sdd1 /mnt” for mounting it. “sudo umount /dev/sdd1” (without “/mnt”) will unmount it.
Sorry, I made a typo there, but actually I think it should have been clear by now…

WDC500 shows up in Dolphin about 8 minutes after I turn it on.

Again, please post the output of “dmesg|tail” immediately after you plug it in/turn it on.

During my poking around, I noticed that it seems like Linux keeps a record of devices in at least 4 ways:

  1. by label
  2. by uuid
  3. by id
  4. by path.

Yes, because the device name can change as you experienced, so mounting a device by uuid, id, or label is preferred.
I’m not sure what you mean with “by path” though. If you mean e.g. /mnt or /run/media/user/xxx, then that’s the mount point, i.e. the directory where it is mounted to. That’s where you will see the files that are on it after you mounted it.

Can those get out of sync and what happens if they do ?

No.

#33

Here they are

  1. Right after I turned it off and it disappeared from Dolphin
hexdump@Corky-PC:~> dmesg|tail                
 9784.998664] sd 10:0:0:0: [sdh] Attached SCSI disk
 9785.059652] md: bind<sdh>
 9993.539821]  sdd: sdd1
 9993.570280]  sdd: sdd1
 9993.666191]  sdh: sdh1
 9995.815571] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
 9995.815574] EDD information not available.
[14346.372737] usb 1-8: USB disconnect, device number 7
[14346.398187] md: unbind<sdh>
[14346.406173] md: export_rdev(sdh)
  1. Right after turning it on

hexdump@Corky-PC:~> dmesg|tail
 9784.998664] sd 10:0:0:0: [sdh] Attached SCSI disk
 9785.059652] md: bind<sdh>
 9993.539821]  sdd: sdd1
 9993.570280]  sdd: sdd1
 9993.666191]  sdh: sdh1
 9995.815571] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
 9995.815574] EDD information not available.
[14346.372737] usb 1-8: USB disconnect, device number 7
[14346.398187] md: unbind<sdh>
[14346.406173] md: export_rdev(sdh)
  1. a few seconds later

hexdump@Corky-PC:~> dmesg|tail
 9784.998664] sd 10:0:0:0: [sdh] Attached SCSI disk
 9785.059652] md: bind<sdh>
 9993.539821]  sdd: sdd1
 9993.570280]  sdd: sdd1
 9993.666191]  sdh: sdh1
 9995.815571] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
 9995.815574] EDD information not available.
[14346.372737] usb 1-8: USB disconnect, device number 7
[14346.398187] md: unbind<sdh>
[14346.406173] md: export_rdev(sdh)
  1. and still a bit later after I heard the disk spinning

hexdump@Corky-PC:~> dmesg|tail
[14434.627687] scsi 11:0:0:0: Direct-Access     WDC      WD5000AAKS-00TMA 3.00 PQ: 0 ANSI: 4
[14434.630210] sd 11:0:0:0: Attached scsi generic sg8 type 0
[14434.631790] sd 11:0:0:0: [sdh] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[14434.633195] sd 11:0:0:0: [sdh] Write Protect is off
[14434.633207] sd 11:0:0:0: [sdh] Mode Sense: 23 00 00 00
[14434.634637] sd 11:0:0:0: [sdh] No Caching mode page found
[14434.634641] sd 11:0:0:0: [sdh] Assuming drive cache: write through
[14434.647497]  sdh: sdh1
[14434.651521] sd 11:0:0:0: [sdh] Attached SCSI disk
[14434.730578] md: bind<sdh>
hexdump@Corky-PC:~>

And as long as it took me to post this, it still does not appear in olphin.
Quite a puzzle, huh.

#34

Well, it seems to be “captured” by md. That should not happen.

I’m not sure at the moment how to prevent that or why that would happen, but try to uninstall the package “mdadm” (“sudo zypper rm mdadm” or YaST) and reboot.
You are not using a RAID, are you? (might be a bad idea to uninstall that if you do…)

#35

PS: STOP!
Do not use “zypper rm”, this will also remove parts of YaST.

Better use “sudo rpm -e --nodeps mdadm” for testing this. Then reboot.

#36

You should NEVER just turn off the drive without umount it first. It can leave the drive in undetermined state and lose information. If Linux file system you will need to run fsck. For USB devices that are auto-mounted they should be in the Device Notifies on your system tray, there you can tell to safly remove. This commits all data and umounts the devices.

.

#37

More info and thanks again.
Here is a picture of Device notifier and Partitioner from Yast and I dont know why the same device should show up as both attached and dis-connected. Makes no sense to me.
I have not done anything since yesterday so “Enable automatic mounting” is maybe off. I had checked it in anticipation of turning it back on.
However the apply button seems to do nothing. Usually I would have expected it to grey out but it wont do that now.

Ok, I guess I am supposed to run fsck and I will do it after I read up on it a bit.

http://i57.tinypic.com/9k8304.png

#38

And here is fsck though it acts as if sdd is mounted.

hexdump@Corky-PC:~> sudo parted /dev/sdd
GNU Parted 3.1
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                            
Model: WDC WD5000AAKS-00TMA (scsi)
Disk /dev/sdd: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 


Number  Start   End    Size   Type     File system  Flags
 1      1049kB  500GB  500GB  primary  ext4         type=83


(parted) quit                                                             
hexdump@Corky-PC:~> sudo fsck /dev/sdd1
fsck from util-linux 2.25.1
e2fsck 1.42.12 (29-Aug-2014)
/dev/sdd1 is in use.
e2fsck: Cannot continue, aborting.




hexdump@Corky-PC:~>
#39

As I wrote already yesterday, sdd is grabbed by md, that’s why it is “in use”.

Have you tried to uninstall mdadm as I suggested?

#40

I just did it and that solved it !
I didn’t see it as I was paying attention to your STOP comment.
Also, the Auto mounting is still turned off. I guess that that’s ok cause things seem to be working fine.

I owe you a beer wolfi.