[opensuse] Strange 42.2 to 42.3 update problem
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine. I have 2 42.3 systems where I plug it in and it says: openSUSE-13.2-DVD-x86_640051 with 3 options. I don't understand why it says the above. On a Leap 42.2 it says SANDISK. I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/08/17 09:02 AM, Mark Hounschell wrote:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
I would start the investigation by using FDISK or similar to see what that tells me about a few things line the partitioning. Partition IDs for different types of file systems have different codes. There may be a clue there. If its really a ISO image then that's a different matter, but that it CAN be recognised as a file system on your 42.2 system says that there's file system info there. FDISK (or similar) will tell you. You might also use BLKID to see what that tells you about the raw drive and what you think might be a file system on it. I might then use DD and OD to look at the first raw sector of the drive to see it it looks like a partitioned device or a loadable device. How I would proceed then depends on what the above tells me. Do check MAN pages and relevant how-to pages on the 'Net for usage. WORST CASE ========== if nothing else matters I might scrub the drive entirely using DD with an INDEV of /dev/zero then use fdisk to set it whatever I want <sidebar> when I download the RAW images from my camera to the computer I pull the card and plug it into the computer than move from the card to a 'incoming' directory on the computer for further processing and categorization. Then rather than returning the card with files 'deleted' to the camera, I wipe it clean and once back in the camera I have the camera reformat it to the way the camera wants it to be. I've had other photographers questions this process all the way from popping the card into a reader for the computer rather than using a tether and 'uploading' to the wipe-and-reformat. Well, the copy is fast. The reformat ensures there are no problems. It's a belt&braces but it woks and it's reliable. I've never had any problems or 'artefacts' crop up such as the one Mark describes. </sidebar> -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/02/2017 09:27 AM, Anton Aylward wrote:
On 02/08/17 09:02 AM, Mark Hounschell wrote:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
I would start the investigation by using FDISK or similar to see what that tells me about a few things line the partitioning. Partition IDs for different types of file systems have different codes. There may be a clue there.
Disk /dev/sdf: 28.7 GiB, 30752000000 bytes, 60062500 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x10ce3e4f Device Boot Start End Sectors Size Id Type /dev/sdf1 2048 60061695 60059648 28.7G c W95 FAT32 (LBA)
If its really a ISO image then that's a different matter, but that it CAN be recognised as a file system on your 42.2 system says that there's file system info there. FDISK (or similar) will tell you.
It is not an ISO image today. At one point in time it might have been? Maybe when it had an installable 13.2 system on it?
You might also use BLKID to see what that tells you about the raw drive and what you think might be a file system on it.
# blkid -L SANDISK /dev/sdf1 # blkid /dev/sdf1 /dev/sdf1: LABEL="SANDISK" UUID="5AAE-A725" TYPE="vfat" PARTUUID="10ce3e4f-01" # blkid -L openSUSE-13.2-DVD-x86_640051 /dev/sdf # blkid /dev/sdf /dev/sdf: UUID="2014-10-27-14-56-02-00" LABEL="openSUSE-13.2-DVD-x86_640051" TYPE="iso9660" PTUUID="10ce3e4f" PTTYPE="dos" So it looks to me like 42.2 is looking at the /dev/sdf1 info and 42.3 is looking at the /dev/sdf info? Is this proper, or something unexpected?
I might then use DD and OD to look at the first raw sector of the drive to see it it looks like a partitioned device or a loadable device.
Do you still think the DD and OD info will be useful?
How I would proceed then depends on what the above tells me.
Do check MAN pages and relevant how-to pages on the 'Net for usage.
WORST CASE ==========
if nothing else matters I might scrub the drive entirely using DD with an INDEV of /dev/zero then use fdisk to set it whatever I want
I thought when I formatted this thing on WIN-7, I did the "long" format. Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/08/17 10:34 AM, Mark Hounschell wrote:
# blkid /dev/sdf1 /dev/sdf1: LABEL="SANDISK" UUID="5AAE-A725" TYPE="vfat" PARTUUID="10ce3e4f-01"
[...]f
# blkid /dev/sdf /dev/sdf: UUID="2014-10-27-14-56-02-00" LABEL="openSUSE-13.2-DVD-x86_640051" TYPE="iso9660" PTUUID="10ce3e4f" PTTYPE="dos"
So it looks to me like 42.2 is looking at the /dev/sdf1 info and 42.3 is looking at the /dev/sdf info? Is this proper, or something unexpected?
/dev/sdf and /dev/sfd1 are NOT the same thing. if you look at you main disk you might see something like # ls /dev/sda /dev/sda # ls /dev/sda* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda is the DRIVE /dev/sda, /dev/sda2, /dev/sda3 are the PARTITIONS on it. # ls -l /dev/sda* brw-rw---- 1 root disk 8, 0 Aug 2 07:56 /dev/sda brw-rw---- 1 root disk 8, 1 Aug 2 07:56 /dev/sda1 brw-rw---- 1 root disk 8, 2 Aug 2 07:56 /dev/sda2 brw-rw---- 1 root disk 8, 3 Aug 2 07:56 /dev/sda3 # ls -l /dev/disk/by-label/BOOT lrwxrwxrwx 1 root root 10 Aug 2 07:56 /dev/disk/by-label/BOOT -> ../../sda1 # ls -l /dev/disk/by-label/SWAP lrwxrwxrwx 1 root root 10 Aug 2 07:56 /dev/disk/by-label/SWAP -> ../../sda2 sda3 is my LVM device but lets not go into that, it will just confuse the matter and the point I'm trying to male # blkid /dev/sda /dev/sda: PTUUID="95145b7b-5bf2-400a-a1c1-d75b6f197126" PTTYPE="gpt" # blkid /dev/sda1 /dev/sda1: LABEL="BOOT" UUID="fe7be533-fb41-421d-9216-29c9701ec01c" TYPE="ext2" PTTYPE="dos" PARTLABEL="primary" PARTUUID="cebb3ec5-8cfe-4272-954e-04552ca5305c" ^^^^^^^^^ ^^^^^^^^ Note: it's now referring to a PARTitiion That''s on the same machine. I think that your two machines are configured slightly differently in the way the udisk rules are set up for recognising when a USB drive is plugged in. It is unlikely that you made such alternations. I think we have to blame the developers for this installation-level config change. its an annoyance but we can't report it as a bug. well, that's my opinion. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Hounschell <markh@compro.net> [08-02-17 09:03]:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
you apparently "quick" formatted it and that only erases the file table and I believe replaces the label. read: https://en.opensuse.org/SDB:Live_USB_stick#How_to_recover_the_USB_stick_for_... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/02/2017 09:31 AM, Patrick Shanahan wrote:
* Mark Hounschell <markh@compro.net> [08-02-17 09:03]:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
you apparently "quick" formatted it and that only erases the file table and I believe replaces the label. read: https://en.opensuse.org/SDB:Live_USB_stick#How_to_recover_the_USB_stick_for_...
I formatted it on a WIN-7 laptop. And I thought I did the "long" format. Maybe not though. Regards Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
02.08.2017 16:02, Mark Hounschell пишет:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
Sounds like https://bugzilla.opensuse.org/show_bug.cgi?id=1046268 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/02/2017 12:52 PM, Andrei Borzenkov wrote:
02.08.2017 16:02, Mark Hounschell пишет:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
Sounds like https://bugzilla.opensuse.org/show_bug.cgi?id=1046268
Yep. Commenting out that line in /usr/lib/udev/rules.d/61-persistent-storage-compat.rules does fix it for me. #ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*" I notice that you imply in the BUG that there probably shouldn't even be a /usr/lib/udev/rules.d/61-persistent-storage-compat.rules? Can I assume there will be an update/fix for this? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
02.08.2017 20:13, Mark Hounschell пишет:
On 08/02/2017 12:52 PM, Andrei Borzenkov wrote:
02.08.2017 16:02, Mark Hounschell пишет:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
Sounds like https://bugzilla.opensuse.org/show_bug.cgi?id=1046268
Yep. Commenting out that line in /usr/lib/udev/rules.d/61-persistent-storage-compat.rules does fix it for me.
#ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*"
I notice that you imply in the BUG that there probably shouldn't even be a /usr/lib/udev/rules.d/61-persistent-storage-compat.rules?
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/02/2017 01:16 PM, Andrei Borzenkov wrote:
02.08.2017 20:13, Mark Hounschell пишет:
On 08/02/2017 12:52 PM, Andrei Borzenkov wrote:
02.08.2017 16:02, Mark Hounschell пишет:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
Sounds like https://bugzilla.opensuse.org/show_bug.cgi?id=1046268
Yep. Commenting out that line in /usr/lib/udev/rules.d/61-persistent-storage-compat.rules does fix it for me.
#ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*"
I notice that you imply in the BUG that there probably shouldn't even be a /usr/lib/udev/rules.d/61-persistent-storage-compat.rules?
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at https://bugzilla.opensuse.org/show_bug.cgi?id=1051940 Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/08/17 01:25 PM, Mark Hounschell wrote:
Both have just been done. The bug against Leap 42.3 is at
Sorry, I don't think its a BUG. The difference may be an nooyance, it may be an artifact of the developers, but I don't think it's a bug, per se. You ran this with a device that had just one partition ... As I pointed out in an earlier email to this list, my main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that which partition should the KDE popup select? Whichever one, it might not be the one I want and hence it is "misidentified by the device notifier". In this case, recognizing the device makes sense. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/02/2017 08:29 PM, Anton Aylward wrote:
On 02/08/17 01:25 PM, Mark Hounschell wrote:
Both have just been done. The bug against Leap 42.3 is at
Sorry, I don't think its a BUG. The difference may be an nooyance, it may be an artifact of the developers, but I don't think it's a bug, per se.
You ran this with a device that had just one partition ...
As I pointed out in an earlier email to this list, my main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that which partition should the KDE popup select?
It should show ALL of them. And does here on 42.3 with the workaround to the BUG. On Leap 42.2 it does show ALL of them also. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-03 02:29, Anton Aylward wrote:
On 02/08/17 01:25 PM, Mark Hounschell wrote:
Both have just been done. The bug against Leap 42.3 is at
Sorry, I don't think its a BUG. The difference may be an nooyance, it may be an artifact of the developers, but I don't think it's a bug, per se.
Yes, it is, but IMHO, it is a bug of the device creation software.
You ran this with a device that had just one partition ...
As I pointed out in an earlier email to this list, my main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that which partition should the KDE popup select?
All of them. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 08/03/2017 09:23 AM, Carlos E. R. wrote:
On 2017-08-03 02:29, Anton Aylward wrote:
On 02/08/17 01:25 PM, Mark Hounschell wrote:
Both have just been done. The bug against Leap 42.3 is at
Sorry, I don't think its a BUG. The difference may be an nooyance, it may be an artifact of the developers, but I don't think it's a bug, per se.
Yes, it is, but IMHO, it is a bug of the device creation software.
Strangely it only seems to affect USB. Hot plugging a Sata disk works properly. All partitions show up. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-03 15:37, Mark Hounschell wrote:
On 08/03/2017 09:23 AM, Carlos E. R. wrote:
On 2017-08-03 02:29, Anton Aylward wrote:
On 02/08/17 01:25 PM, Mark Hounschell wrote:
Both have just been done. The bug against Leap 42.3 is at
Sorry, I don't think its a BUG. The difference may be an nooyance, it may be an artifact of the developers, but I don't think it's a bug, per se.
Yes, it is, but IMHO, it is a bug of the device creation software.
Strangely it only seems to affect USB. Hot plugging a Sata disk works properly. All partitions show up.
Burn an ISO DVD on a Sata disk, then format it for normal use, and try how it is identified ;-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Mark Hounschell composed on 2017-08-03 09:37 (UTC-0400):
Strangely it only seems to affect USB. Hot plugging a Sata disk works properly. All partitions show up.
Whether due to kernel, usbutils, storage drivers, pmount, udev and/or something else I don't know, but I do know that USB HDs are not treated the same as other USB storage. Other are treated as removable devices, while USB HDs are not distinguished from internal HDs on the SATA buses. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-03 20:50, Felix Miata wrote:
Mark Hounschell composed on 2017-08-03 09:37 (UTC-0400):
Strangely it only seems to affect USB. Hot plugging a Sata disk works properly. All partitions show up.
Whether due to kernel, usbutils, storage drivers, pmount, udev and/or something else I don't know, but I do know that USB HDs are not treated the same as other USB storage. Other are treated as removable devices, while USB HDs are not distinguished from internal HDs on the SATA buses.
Yes. If you use "lsblk" to get information of the disks, and include "RM" in the output format, it prints if the disk is recognized as "removable". I use it this way (trimmed): Isengard:~ # lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT NAME KNAME RA RM RO SIZE TYPE FSTYPE LABEL PARTLABEL MOUNTPOINT UUID PARTUUID WWN MODEL ALIGNMENT sda sda 512 0 0 111,8G disk KINGSTON SMS200S 0 ├─sda1 sda1 512 0 0 156M part vfat primary /boot/efi BD39-068A cada5ef3-03a1-4d0b-a984-49c1c16c75bb 0 sdc sdc 512 0 0 3,7T disk 2115 0 ├─sdc1 sdc1 512 0 0 250M part ext2 Initial_4T Initial_4T 216dbdde-6676-4102-a686-541a4874fe04 007da3de-1328-4988-9f36-2eedd41587aa 0 sdd sdd 512 1 0 3,7G disk USB DISK 2.0 0 └─sdd1 sdd1 512 1 0 3,7G part ext4 Ext4Flash f07734c8-b021-4dc0-9729-abcb07fb66cd ad7b68da-01 0 sda is internal "SSD". sdc is rotating disk via usb3 cable. sdd is a normal usb stick - and this one has the "RM" field set to "1". How it knows, I don't know. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at
https://bugzilla.opensuse.org/show_bug.cgi?id=1051940
Thanks Mark
I have two boxes both running 42.2. The older one was unaffected in that until I just ran "zypper up" my Verbatim usb stick was recognised as such by KDE Plasma and after running "xypper up" it is reported as "openSuse Leap dvd" So I assume there will be another update that fixes the problem ? Is there a list that announces such things ? M -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 3 Aug 2017 12:25:30 +0100 michael norman <michaeltnorman@gmail.com> wrote:
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at
https://bugzilla.opensuse.org/show_bug.cgi?id=1051940
Thanks Mark
I have two boxes both running 42.2. The older one was unaffected in that until I just ran "zypper up" my Verbatim usb stick was recognised as such by KDE Plasma and after running "xypper up" it is reported as "openSuse Leap dvd"
So I assume there will be another update that fixes the problem ? Is there a list that announces such things ?
M
opensuse-updates@opensuse.org -- Bob Williams System: Linux 4.4.76-1-default Distro: openSUSE 42.3 (x86_64) Desktop: KDE Frameworks: 5.32.0, Qt: 5.6.2 and Plasma: 5.8.7
On 08/03/2017 07:25 AM, michael norman wrote:
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at
https://bugzilla.opensuse.org/show_bug.cgi?id=1051940
Thanks Mark
I have two boxes both running 42.2. The older one was unaffected in that until I just ran "zypper up" my Verbatim usb stick was recognised as such by KDE Plasma and after running "xypper up" it is reported as "openSuse Leap dvd"
So I assume there will be another update that fixes the problem ? Is there a list that announces such things ?
Ah, good to know. And update to 42.2 breaks it also. Regards Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/03/2017 07:25 AM, michael norman wrote:
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at
https://bugzilla.opensuse.org/show_bug.cgi?id=1051940
Thanks Mark
I have two boxes both running 42.2. The older one was unaffected in that until I just ran "zypper up" my Verbatim usb stick was recognised as such by KDE Plasma and after running "xypper up" it is reported as "openSuse Leap dvd"
So I assume there will be another update that fixes the problem ? Is there a list that announces such things ?
M
You could add a comment about the Leap 42.2 update breakage to the original BUG against TW and it should get addressed. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/08/17 13:09, Mark Hounschell wrote:
On 08/03/2017 07:25 AM, michael norman wrote:
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at
https://bugzilla.opensuse.org/show_bug.cgi?id=1051940
Thanks Mark
I have two boxes both running 42.2. The older one was unaffected in that until I just ran "zypper up" my Verbatim usb stick was recognised as such by KDE Plasma and after running "xypper up" it is reported as "openSuse Leap dvd"
So I assume there will be another update that fixes the problem ? Is there a list that announces such things ?
M
You could add a comment about the Leap 42.2 update breakage to the original BUG against TW and it should get addressed.
Mark
Maybe I "could" add a comment to the bugreport, if I was in the least competent in that area, and I had any idea of which one of the updates broke the thing. Sorry I don't know how to do that. I just wonder how many lists I "should" subscribe to to see thing sort of thing coming, and more seriously how do updates get applied which break things without anybody noticing before users have to file bug reports, lets remind ourselves what this looks like to newer users, we are talking here about KDE automatically mounting inserted usb drives. Something every other reliable system just does. But now until its fixed openSUSE doesn't. M -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/03/2017 08:27 AM, michael norman wrote:
On 03/08/17 13:09, Mark Hounschell wrote:
On 08/03/2017 07:25 AM, michael norman wrote:
Can I assume there will be an update/fix for this?
Someone will need to file bug report for 42.3 or at least mention that 42.3 is also affected. This bug is filed for tumbleweed.
Both have just been done. The bug against Leap 42.3 is at
https://bugzilla.opensuse.org/show_bug.cgi?id=1051940
Thanks Mark
I have two boxes both running 42.2. The older one was unaffected in that until I just ran "zypper up" my Verbatim usb stick was recognised as such by KDE Plasma and after running "xypper up" it is reported as "openSuse Leap dvd"
So I assume there will be another update that fixes the problem ? Is there a list that announces such things ?
M
You could add a comment about the Leap 42.2 update breakage to the original BUG against TW and it should get addressed.
Mark
Maybe I "could" add a comment to the bugreport, if I was in the least competent in that area, and I had any idea of which one of the updates broke the thing. Sorry I don't know how to do that.
I just wonder how many lists I "should" subscribe to to see thing sort of thing coming, and more seriously how do updates get applied which break things without anybody noticing before users have to file bug reports, lets remind ourselves what this looks like to newer users, we are talking here about KDE automatically mounting inserted usb drives. Something every other reliable system just does. But now until its fixed openSUSE doesn't.
M
I've just confirmed you are correct with a 42.2 system in house here. It got broken. I'll report it. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-02 15:02, Mark Hounschell wrote:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
This is an old issue. When you formatted it as fat32 the formatter did not erase some areas that identify it as an ISO image that was written previously. As Patrick wrote, there is a procedure to correctly re-use the stick again after holding an ISO image: # umount /dev/sdX # dd if=/dev/zero of=/dev/sdX count=100 -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 08/03/2017 09:29 AM, Carlos E. R. wrote:
On 2017-08-02 15:02, Mark Hounschell wrote:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
This is an old issue. When you formatted it as fat32 the formatter did not erase some areas that identify it as an ISO image that was written previously.
As Patrick wrote, there is a procedure to correctly re-use the stick again after holding an ISO image:
# umount /dev/sdX # dd if=/dev/zero of=/dev/sdX count=100
It is still a bug. This should not be required. It should not care/look what is /dev/sdx is. Only what /dev/sdx# is. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-03 15:42, Mark Hounschell wrote:
On 08/03/2017 09:29 AM, Carlos E. R. wrote:
As Patrick wrote, there is a procedure to correctly re-use the stick again after holding an ISO image:
# umount /dev/sdX # dd if=/dev/zero of=/dev/sdX count=100
It is still a bug. This should not be required. It should not care/look what is /dev/sdx is. Only what /dev/sdx# is.
It has to identify partitions first, list them. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/08/17 14:42, Mark Hounschell wrote:
On 08/03/2017 09:29 AM, Carlos E. R. wrote:
On 2017-08-02 15:02, Mark Hounschell wrote:
I have a SANDISK usb stick that was formatted as FAT32 on a WIN-7 laptop. It previously has had other formats including at one point was a opensuse-13.2 install stick. In Leap 42.2 it mounts just fine. I plug it in and it is labeled SCANDISK I click on open with file manager and all is fine.
I have 2 42.3 systems where I plug it in and it says:
openSUSE-13.2-DVD-x86_640051 with 3 options.
I don't understand why it says the above. On a Leap 42.2 it says SANDISK.
I click open with file manager but it can't open. I'm sure that it is just something to do with the stick as I have other USB sticks that work just fine on 42.3. The stick is FAT32 with a volume label of SANDISK. I don't understand why this is happening and I really need this thing to work properly. Can anyone shed some light what might be changed on the stick for Leap 42.3 to treat it correctly?
This is an old issue. When you formatted it as fat32 the formatter did not erase some areas that identify it as an ISO image that was written previously.
As Patrick wrote, there is a procedure to correctly re-use the stick again after holding an ISO image:
# umount /dev/sdX # dd if=/dev/zero of=/dev/sdX count=100
It is still a bug. This should not be required. It should not care/look what is /dev/sdx is. Only what /dev/sdx# is.
Mark
Of course its a bug caused by an update. I don't expect to have to reformat or whatever a usb stick which may or may note have been used as something else in the past It was seen properly in 42,2 before the update to the system. Linux Mint sees it as it "is" now, openSUSE needs to be fixed to do the same thing. Is anybody listening to this who can fix it ? M -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-03 15:51, michael norman wrote:
On 03/08/17 14:42, Mark Hounschell wrote:
On 08/03/2017 09:29 AM, Carlos E. R. wrote:
On 2017-08-02 15:02, Mark Hounschell wrote:
Of course its a bug caused by an update. I don't expect to have to reformat or whatever a usb stick which may or may note have been used as something else in the past It was seen properly in 42,2 before the update to the system. Linux Mint sees it as it "is" now, openSUSE needs to be fixed to do the same thing. Is anybody listening to this who can fix it ?
That's another bug. Yes, I think there is work on it. Or you can apply the modification yourself. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* michael norman <michaeltnorman@gmail.com> [08-03-17 09:53]:
On 03/08/17 14:42, Mark Hounschell wrote:
On 08/03/2017 09:29 AM, Carlos E. R. wrote:
On 2017-08-02 15:02, Mark Hounschell wrote: [...] As Patrick wrote, there is a procedure to correctly re-use the stick again after holding an ISO image:
# umount /dev/sdX # dd if=/dev/zero of=/dev/sdX count=100
It is still a bug. This should not be required. It should not care/look what is /dev/sdx is. Only what /dev/sdx# is.
Mark
Of course its a bug caused by an update. I don't expect to have to reformat or whatever a usb stick which may or may note have been used as something else in the past It was seen properly in 42,2 before the update to the system. Linux Mint sees it as it "is" now, openSUSE needs to be fixed to do the same thing. Is anybody listening to this who can fix it ?
no, of course it is not a bug and not caused by an update. it is an inherent problem with micro$oft formatting. they do not set the standard and seldom attempt to adhere to *any* standard which does not suit their purpose. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/08/17 18:18, Patrick Shanahan wrote:
* michael norman <michaeltnorman@gmail.com> [08-03-17 09:53]:
On 03/08/17 14:42, Mark Hounschell wrote:
On 08/03/2017 09:29 AM, Carlos E. R. wrote:
On 2017-08-02 15:02, Mark Hounschell wrote: [...] As Patrick wrote, there is a procedure to correctly re-use the stick again after holding an ISO image:
# umount /dev/sdX # dd if=/dev/zero of=/dev/sdX count=100
It is still a bug. This should not be required. It should not care/look what is /dev/sdx is. Only what /dev/sdx# is.
Mark
Of course its a bug caused by an update. I don't expect to have to reformat or whatever a usb stick which may or may note have been used as something else in the past It was seen properly in 42,2 before the update to the system. Linux Mint sees it as it "is" now, openSUSE needs to be fixed to do the same thing. Is anybody listening to this who can fix it ?
no, of course it is not a bug and not caused by an update. it is an inherent problem with micro$oft formatting. they do not set the standard and seldom attempt to adhere to *any* standard which does not suit their purpose.
Please explain to me why in many years of using various operating systems that what I and others have reported is not a fault in the latest versions of openSUSE. I repeat, it worked as expected and then after an update it doesn't, and why that is now the fault of Microsoft formatting all of a sudden. M -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-03 19:18, Patrick Shanahan wrote:
no, of course it is not a bug and not caused by an update. it is an inherent problem with micro$oft formatting. they do not set the standard and seldom attempt to adhere to *any* standard which does not suit their purpose.
You get the same failure formatting with Linux gparted, for instance. In fact, we learnt of this problem from people that only used Linux. It is a "bug" of most formatters trying to end fast, thus not erasing the areas the new filesystem they are creating doesn't use, because it takes time. Then there is a secondary bug - the one people see: Bug 1046268 - USB Keys are mis-identified by device notifier But: «This bug got reassigned to udisks because it was shown that udsisk already has wrong filesystem type. Both KDE and XFCE (should) use udisks as backend to discover and mount devices so should have the same issue.» (Andrei Borzenkov) There is a modification you can do to file "/usr/lib/udev/rules.d/61-persistent-storage-compat.rules" to bypass the problem - comment out this line: ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*" -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/08/17 09:42 AM, Mark Hounschell wrote:
It is still a bug. This should not be required. It should not care/look what is /dev/sdx is. Only what /dev/sdx# is.
See my comment about multiple partitions. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Anton Aylward -
Bob Williams -
Carlos E. R. -
Felix Miata -
Mark Hounschell -
michael norman -
Patrick Shanahan