May 2019 - openSUSE Users - openSUSE Mailing Lists

Mount Windows NT(NTFS) drive as drive Z: for all users
by Keith Jacobs 25 Sep '21

25 Sep '21

We have an winNT server and need to auto mount a shared folder as if it were a windose mapped drive Z: on SuSE8 Could someone please explain how to do this and how to make sure it is set-up for every user everytime the system is booted. Thanks Regards Keith Jacobs New to Linux

3 2

[opensuse] libc segfaults attaching an iPad
by Dave Howorth 26 Mar '21

26 Mar '21

I just tried to attach an iPad to my openSUSE 15.0 system, via USB. I think I've done it before, but this time it fails. Dmesg has: [9787970.148053] usb 3-9: new high-speed USB device number 96 using xhci_hcd [9787970.302089] usb 3-9: New USB device found, idVendor=05ac, idProduct=12a2 [9787970.302091] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [9787970.302092] usb 3-9: Product: iPad [9787970.302093] usb 3-9: Manufacturer: Apple Inc. [9787970.302094] usb 3-9: SerialNumber: c4088xxxxxserialxredacted [9787971.044264] ipheth 3-9:4.2: Apple iPhone USB Ethernet device attached [9787991.101146] pool[16789]: segfault at 0 ip 00007f6ada593ef1 sp 00007f6ad6203bd8 error 4 in libc-2.26.so[7f6ada43a000+1b1000] Anybody have any idea what the problem is? Thanks, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 7

[opensuse] Raid, Raid6, what file system for good fault tolerance?
by cagsm 21 Dec '20

21 Dec '20

Hi list, speaking about software raid, not hardware controller based. I am trying to go for some local OpenSuse machine and adding some storage to it. Was considering Raid6, and now reading about a bit and people left and right scaremongering about the larger the disks these days in the double digit terabyte capacities even, the more likely it is that during a reconstruction of a raid subsequent errors would occur. I would absolutely like to keep my data consistent, and I am not thinking about double digit terabytes either, would stick to 2TB or 4TB disks, with Raid6 thats at least 4 physical drives. Now I am wondering if it possible to use a good robust file system that can add some more parity or check blocks or redundancy on top of the hardware disks, to absolutely be able to always read my data. I can't add multiple machines or like those high availability stuff like clusters and what not I read about DRBD (Distributed Replicated Block Device), or maybe I am just too scared by those technical terms or consider myself to be just a simpleton and wanting to keep it rather simple. My use case here is also not constant availablity, when a disk needs to be replaced, so be it, but I don't want to lose my data that I can not ever read certain parts of it again or such stuff. The thing that came to my mind was, if there is some file systems that would add redundancy and robustness onto the mdraid system of the linux kernel? Anyone with some useful insights? Roughly speaking, I was considering some simple pcie esata interfaced controller card and an external case enclosure with esata port and portmulitplier stuff inside, that can present at least 4 physical disks as JBOD, just a bunch of disks, so that the Linux can seem them all separately. Speed and rebuild times are not my concern, but data persistence and data integrity. Not even number of physical disks, I could live with even one of those 8 bay device enclosures and cases that are out there on the market. Thanks for any help and hints. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 23

[opensuse] Issue with smartd
by Carlos E. R. 21 Oct '20

21 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have one disk that is giving me problems with the smartd daemon. I get this in the log: <3.6> 2018-10-21T13:45:23.829155+02:00 Isengard smartd 1173 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.483719+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], opened <3.6> 2018-10-21T13:45:24.484570+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB <3.6> 2018-10-21T13:45:24.503334+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not found in smartd database. <3.6> 2018-10-21T13:45:24.525071+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Attribute Autosave. <3.6> 2018-10-21T13:45:24.530486+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Automatic Offline Testing. <3.6> 2018-10-21T13:45:24.535003+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], is SMART capable. Adding to "monitor" list. <3.6> 2018-10-21T13:45:24.535627+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.880219+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T14:15:25.233525+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 147 to 144 <3.6> 2018-10-21T15:45:31.681938+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T15:45:33.632399+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T16:15:24.678100+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email <3.6> 2018-10-21T18:15:31.767150+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T18:15:33.717688+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T18:45:24.587304+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email It intermitently but periodically fail to read atributes, triggering hundreds of emails sent to me to warn of the problem: +++------------ Subject: SMART error (FailedReadSmartData) detected on host: Isengard This message was generated by the smartd daemon running on: host name: Isengard DNS domain: valinor The following warning/error was logged by the smartd daemon: Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data Device info: WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB For details see host's SYSLOG. You can also use the smartctl utility for further investigation. Another message will be sent in 24 hours if the problem persists. - ------------++- The disk is indeed smart capable and it works fine, as long as I call smartctl with "-d sat,16", which I do: Isengard:~ # smartctl --test=short -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Short self-test routine immediately in off-line mode". Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 2 minutes for test to complete. Test will complete after Sun Oct 21 13:50:18 2018 Use smartctl -X to abort test. Isengard:~ # Isengard:~ # smartctl --health -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Isengard:~ # It is crucial to use "-d sat,16" or it fails: Isengard:~ # smartctl --health /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0: Unknown USB bridge [0x1058:0x25ee (0x4004)] Please specify device type with the -d option. Use smartctl -h to get a usage summary Isengard:~ # Of course I use that option on the config: Isengard:~ # cat /etc/smartd.conf | egrep -v "^[[:space:]]*$|^#" /dev/sda -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000000000000001 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000c5009399305f -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 -d sat,16 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor Isengard:~ # What else am I missing? Is smartd not using "-d sat,16" somewhere else? Is it some other problem? Isengard:~ # rpm -q smartmontools smartmontools-6.6-135.1.x86_64 Isengard:~ # - -- Cheers Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlvM5UMACgkQtTMYHG2NR9WCwQCePjOt8PSMKsx6DwSe9bZJRhHf 2lQAn02eBTrtfAqmEg5ydZVagvMfW2r6 =eIzR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] oS 13.1 : "gnome keyring socket is not owned with the same credentials as the user"
by ellanios82 11 Aug '19

11 Aug '19

Hello List am using Xfce : - in /var/log/warn : i see warning " The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring-4i77r7/control 2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login keyring " ............... - any ideas how to fix ? thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Leap + Tumbleweed + boot partition
by Stephen Berman 06 Jul '19

06 Jul '19

I bought a computer with Leap 15.0 preinstalled on an SSD, and I also wanted to install Tumbleweed on the disk. For reasons detailed below, I did this without installing a bootloader for Tumbleweed, but since Tumbleweed is frequently updated, including grub2, I think it would be better to install the bootloader in Tumbleweed. Due to my lack of knowledge, I would be grateful for advice on how to do that safely. Some specifics follow about the disk and what I did to install Tumbleweed. The SSD had three partitions: /boot, / (root) and swap. I shrank the root partition (formatted as ext4) and added a btrfs partition for Tumbleweed. I first left /boot and swap as is, but the Tumbleweed installer said there was no bootable partition (I don't remember the exact wording, something like no BIOS boot table). I then tried deleting the /boot partition and adding it again, selecting "BIOS Boot" as the partition ID, but the installer still said there was no bootable partition. I also tried different file systems to format /boot -- originally it was FAT and I also tried XFS and ext3 -- but that made no difference. So finally, I left the /boot partition unchanged but unmounted it and proceeded with the installation. At the summary I then changed the boot setup to prevent any boot loader being installed and any changes made to the MBR. The installer said I might end up with an unbootable system, but I went ahead anyway. The installation completed and on rebooting the boot screen showed only Leap 15.0 as before, but after running grub2-mkconfig in Leap, Tumbleweed was found and I could boot it and it seems to be fine. The disk has GPT with protective MBR. As noted the /boot partition is formatted as FAT and also contains a directory efi, which is populated in the running Leap, which mounts /boot/efi, but in the running Tumbleweed, where /boot is not a separate partition, after mounting the partition Leap sees as /boot/efi, the efi directory is empty (in the running Tumbleweed). I do not plan to install any MS-Windows system, but I do plan to install other Linux-based systems besides Tumbleweed, and possibly a *BSD system. How can I install the bootloader in Tumbleweed -- either from the currently installed Tumbleweed or by reinstalling it -- without risking making both Tumbleweed and Leap unbootable? If that requires deleting the existing /boot partition and add it anew, is it necessary, given the systems I plan to install, to have the efi directory, and if so, do I just have to make /boot/efi a mountpoint, and if not, what else to I need to do to make sure it exists and gets populated as required (if it's required)? And if the efi directory is not needed, what would be the recommended file system for the boot partition? I also have a question concerning having a separate /boot partition shared by Leap, Tumbleweed and any other systems I install: in each system the directory /boot contains versioned files of the kernel, config, etc., but there are also symlinks vmlinuz and initrd pointing to the latest version installed in the system; if Leap and Tumbleweed (and other Linux-based systems) populate the same /boot directory, the last one installed would override existing symlinks, so I don't see how this can work. Is it possible for different systems to use the same /boot directory, installed on a separate partition, and if not, where do the files used for booting different systems need to go, when a separate /boot partition is used? Thanks, Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 62

[opensuse] How to exclude sites from Zypper?
by Anton Aylward 04 Jun '19

04 Jun '19

I mean site not repository. I know, because in the past, I can download at speed in excess of 6megabytes/sec from some sites 9and, lets face it, from YouTube and other streaming sites), and still can if I sftp/wget/cURL from specific ones, but the supposed smarts or mirrorbrain are selecting sites that, while they may be electrically closer, are delivering less than 1% of that, often even less, sometimes single digit byes/sec. Other than firewalling out specific sites, and somehow getting zypper to deal with that error (but I'm not sure how), how can I tell the mirrorbrain selection that I don't want "the closest and mostest"? Who knows, perhaps Estonia is faster than Waterloo? Currently downloading a new kernel at between 88 and 32 kiloBITS/sec -- 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(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 20

[opensuse] leap 15.1 / openvpn - stricter requirements on the server
by Per Jessen 04 Jun '19

04 Jun '19

Just a heads-up, maybe we have some openvpn users here? In leap 15.1 we ship openvpn 2.4.5 - this version has a stricter set of checks on the server setup. I don't think there is a way around rebuilding the pki infrastructure - generate a new CA with sha256 signature, then re-issue all client certificates. -- Per Jessen, Zürich (6.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] What happened to Aramok?
by James Knott 02 Jun '19

02 Jun '19

In 15.0 and earlier, I used Aramok for my music player. However, I can't seem to find it. Where is it? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 91

[opensuse] Annoying features in Amarok
by James Knott 02 Jun '19

02 Jun '19

Since installing the latest Amarok on 15.1, I've noticed a couple of annoying "features". First, I now get a pop up message with the song title. Since I'm not deaf, I really don't need a pop up telling me what song is starting. The other, more serious "feature" is it stops playing after several songs. I have been using Amarok for a few years and not experienced these before. Any ideas? I have gone into the settings and turned off anything I could find about notifications, but they still happen. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 10