March 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] smartctl: is this HD really OK?
by Felix Miata 30 Mar '15

30 Mar '15

I have a multiboot system that has long delays at selecting Grub menu items. The Linux-bzImage messages appear, and should be shortly followed by the initrd message, but that's where the delay occurs. It can be as long as 3 minutes. It only happens with some installations and not others, all of which are normally being started from the same Grub on sda3, but can be chainloaded to, which doesn't eliminate the delays. Even after redoing Grub setup for 13.2, chainloading to its Grub triggers a reboot. This HD spent a bit over 3 years in a STB, after which I replaced it, which I did because the STB was stalling inexplicably. After the replacement, I used the WD utility to evaluate the device. It found bad sectors, and claimed it corrected them, that the device passed. I umounted all partitions except / while booted to TW, and ran e2fsck -f on each installations /. All passed, except the last tried (Kubuntu), which resulted in "error reading block 34307 (attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 10863. Ignore error<y>?" This repeated for blocks 34308, 34309, 590029, 590030, 688204 and several more, followed by directory corruption for inodes 68166, 98879 & yada. Most of these partitions are ext4. 11.4, 12.1 & 12.2 are ext3. Since it "passed" it has spent at least 20 hours in a PC, after I cloned from its original HD to the "passed" HD and switched them. NAICT, smartctl thinks this HD is OK, but is it really? I can't think of any other explanation for boot delays like this except for trouble reading sectors containing kernels or initrds - installing a new kernel/initrd can switch an installation from suffering the delays to one not, and vice versa. I asked about this on the linux-ide mailing list 2 weeks ago, but got no feedback there: http://marc.info/?l=linux-ide&m=142517892627960&w=2 The problem has me frustrated in that I cannot remember whether it started before or after the HD switch. If it started before, obviously trouble is not with the "passed" HD. This is a test system, so it doesn't really have anything "important" on it, other than the time invested to reconfigure on account of device IDs being different (e.g. /boot/grub/device.map). # smartctl -t long /dev/sda (more than 2 hours later) # smartctl -H /dev/sda smartctl 6.3 2015-02-08 r4039 [x86_64-linux-3.19.1-1-desktop] (SUSE RPM) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED # smartctl -l selftest /dev/sda smartctl 6.3 2015-02-08 r4039 [x86_64-linux-3.19.1-1-desktop] (SUSE RPM) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 27071 252915937 # 2 Extended offline Completed: read failure 90% 27070 252915955 # 3 Conveyance offline Completed without error 00% 27051 - # 4 Extended offline Completed: read failure 90% 27046 460886821 # 5 Short offline Completed without error 00% 3 - # smartctl -A /dev/sda smartctl 6.3 2015-02-08 r4039 [x86_64-linux-3.19.1-1-desktop] (SUSE RPM) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 3210 3 Spin_Up_Time 0x0027 156 153 021 Pre-fail Always - 3191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 869 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 063 063 000 Old_age Always - 27074 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 862 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 29 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 869 194 Temperature_Celsius 0x0022 112 073 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 195 173 000 Old_age Always - 306 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 smartctl -x data: http://fm.no-ip.com/Tmp/Hardware/Disk/smart-wdAVGP3200AVVS.txt -- "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(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 39

[opensuse] APEI Generic Hardware
by Roger Oberholtzer 30 Mar '15

30 Mar '15

I have a system, that when it boots, reports this in /var/log/messages: rst28 kernel: [ 61.244311] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 2 rst28 kernel: [ 61.244314] {1}[Hardware Error]: APEI generic hardware error status rst28 kernel: [ 61.244315] {1}[Hardware Error]: severity: 2, corrected rst28 kernel: [ 61.244317] {1}[Hardware Error]: section: 0, severity: 2, corrected rst28 kernel: [ 61.244318] {1}[Hardware Error]: flags: 0x01 rst28 kernel: [ 61.244319] {1}[Hardware Error]: primary rst28 kernel: [ 61.244320] {1}[Hardware Error]: fru_text: CorrectedErr rst28 kernel: [ 61.244322] {1}[Hardware Error]: section_type: PCIe error rst28 kernel: [ 61.244323] {1}[Hardware Error]: port_type: 0, PCIe end point rst28 kernel: [ 61.244324] {1}[Hardware Error]: version: 0.0 rst28 kernel: [ 61.244325] {1}[Hardware Error]: command: 0xffff, status: 0xffff rst28 kernel: [ 61.244326] {1}[Hardware Error]: device_id: 0000:00:02.3 rst28 kernel: [ 61.244327] {1}[Hardware Error]: slot: 0 rst28 kernel: [ 61.244328] {1}[Hardware Error]: secondary_bus: 0x00 rst28 kernel: [ 61.244330] {1}[Hardware Error]: vendor_id: 0xffff, device_id: 0xffff rst28 kernel: [ 61.244331] {1}[Hardware Error]: class_code: ffffff It reports it twice. Then no more. I am not sure what device is having the problem. I am not sure how to find out what 0000:00:02.3 is. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] tightvnc sluggish when typing
by Roger Oberholtzer 30 Mar '15

30 Mar '15

When I connect with TightVNC (tightvnc-1.3.10-10.8.1.i586 on openSUSE 12.3) to a Linux client, keyboard activity is sluggish. There can be delays of seconds when typing. And the Enter key sometimes needs to be pressed more than once. The remote systems are various openSUSE releases. The display is otherwise rather quick. It is only typing that seems to be effected. It seems that apps like konsole and xterm are most effected. LibreOffice seems to get the key presses as I type. The font size (and thus the amount of screen changed) is the same for all apps. I even made the konsole font bigger to see if that helped. Nope. So I am guessing it is more a keyboard forwarding issue than a screen update issue. A search revealed that this has been seen on the Windows client in the past. But I did not see a resolution or mention of this on Linux. Maybe I should use a better client? Local command: vncviewer -passwd /home/roger/.vncpasswd rst28:0 Remote command (via xinetd): /usr/bin/x11vnc -inetd -rfbauth /etc/vncpasswd -o /var/log/x11vnc.log -find -env FD_XDM=1 -shared -forever -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Grr - Need Help - Unstick FF36 New Bookmark Entry Dialog
by David C. Rankin 29 Mar '15

29 Mar '15

All, Just seeing if anyone has a solution. In FF36, when you go to bookmark a page (ctrl+d), the bookmark entry dialog is now STUCK over the page you are bookmarking and cannot be moved (no longer modeless). How in the heck do you move it so you can read/copy/paste from the page into the dialog so you can have sane bookmark names instead of whatever 256+ char default page title is? This is frustrating as heck. I try and keep my bookmarks logically named. I just tried to create a new bookmark to the UEFI link Anton posted, and I couldn't move the damn dialog so I could see the page to create a custom title for the bookmark. Has anyone found a way to get rid of this behavior and restore the previous dialog? I never had this problem in the past... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] What happened to openSUSE-SU-2014:1254-1
by Lew Wolfgang 29 Mar '15

29 Mar '15

Hi Folks, I'm having to maintain a 13.2 box with a requirement to run Nessus scans on it. Nessus is complaining about bash related CVE-2014-6271 and related issues. The fix is mentioned here: http://lists.opensuse.org/opensuse-security-announce/2014-09/msg00044.html but "zypper in -t patch openSUSE-2014-567" says "patch non-existent or not needed". Nessus identifies the installed bash as bash-4.2-75.3.1, but says it should be bash-4.2-75.4.1. This doesn't work either: zypper patch --cve=CVE-2014-6217 Is there something wrong with the repositories, or is Nessus barking up the wrong tree? This is on a fresh 13.2 x86-64 system. Thanks in advance, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] Mounting iomega_px4-300d NAS
by don fisher 28 Mar '15

28 Mar '15

I have an iomega_px4-300d system as part of my home network. I would like to be able to mount it on opensuse 13.2. In the past (fedora14) I had do configure a rather ugly line for /etc/fstab which follows: dfnas:/mnt/pools/A/A0/Documents/ /mnt/nas nfs rw,nosuid,relatime, vers=3,rsize=2048,wsize=2048,namlen=255,soft,proto=tcp,timeo=10, retrans=10,sec=sys,mountaddr=192.168.7.90,mountvers=3,mountport=609, mountproto=udp,local_lock=none,addr=192.168.7.90 0 0 Pardon the wrap arounds, but I do not think fstab allows for continuation lines, hence this is all one line in my /etc/fstab. This line mounted the NAS /mnt/pools/A/A0/Documents directory on that system. When I mount the NAS under fedora it works, under openSuse the mount command hangs. I do not know how to debug network problems. I have the following entries from dmesg: [281093.136399] FS-Cache: Loaded [281093.138735] RPC: Registered named UNIX socket transport module. [281093.138737] RPC: Registered udp transport module. [281093.138737] RPC: Registered tcp transport module. [281093.138738] RPC: Registered tcp NFSv4.1 backchannel transport module. [281093.141275] FS-Cache: Netfs 'nfs' registered for caching [281093.142162] Key type dns_resolver registered [281093.143874] NFS: Registering the id_resolver key type [281093.143879] Key type id_resolver registered [281093.143880] Key type id_legacy registered Under pstree I see: sudo---mount---mount.nfs Also, where does one start the rpc-statd.service? If I mount an nfs share under root the service starts. After that, once it is started, I can mount nfs shares as user. I do not know how to tell systemd to start this. Does anybody have experience with this NAS device, or other suggestions on how to proceed. I admit to not having memory of how the entry shown in fstab was generated, probably via some google link. Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] How do I switch from NetworkManager to wicked ?
by Per Jessen 28 Mar '15

28 Mar '15

I'm trying to $SUBJ using "yast lan", but when I have switched to wicked and exited yast, then go back in, it's still saying NetworkManager. What's the magic incantation? -- Per Jessen, Zürich (11.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Plymouth splash failure on 13.2-x64 Intel
by Marco Calistri 28 Mar '15

28 Mar '15

Hello, Wonder if others using a Sandy-bridge Intel video card (i915) is having same Plymouth boot splash dark screen with the three ??? question marks dots. I tried all the possible solutions found by Googling but the issue continues. The problem has raised recently, I suspect caused by some package updates. Regards, -- There is no such thing as a problem without a gift for you in its hands. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] mariadb command line - pageup/down not working ?
by Per Jessen 28 Mar '15

28 Mar '15

With the mysql command line shell, one is able to use pageup/down to search through command history and find a previous command matching the input, just like in the unix shell. With mariadb this no longer sems to work - when I type in the beginning of a query and hit PageUp, all I get is a tilde ? -- Per Jessen, Zürich (7.5°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6

[opensuse] Can't reduce text size at GRUB2+UEFI boot-time console
by lyndat3＠your-mail.com 28 Mar '15

28 Mar '15

I've installed opensuse 13.2 in a minimal server config. It boots with GRUB2+UEFI. I've set up text only boot. Currently the console display appears to be 1024x768. That's large for my taste. I want to reduce the text size to take advantage of my 1920x1080 monitor. The video card's an Nvidia GT610 hwinfo --gfxcard | egrep "Hardware|Vendor|Device" Hardware Class: graphics card Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x104a "GF119 [GeForce GT 610]" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd." SubDevice: pci 0x809f hwinfo --framebuffer 02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.+d_bXS84kpB Hardware Class: framebuffer Model: "NVIDIA GF119 Board - 13100000" Vendor: "NVIDIA Corporation" Device: "GF119 Board - 13100000" SubVendor: "NVIDIA" SubDevice: Revision: "Chip Rev" Memory Size: 14 MB Memory Range: 0xd1000000-0xd1dfffff (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0303: 800x600 (+800), 8 bits Mode 0x0305: 1024x768 (+1024), 8 bits Mode 0x0307: 1280x1024 (+1280), 8 bits Mode 0x030e: 320x200 (+640), 16 bits Mode 0x030f: 320x200 (+1280), 24 bits Mode 0x0311: 640x480 (+1280), 16 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Mode 0x0317: 1024x768 (+2048), 16 bits Mode 0x0318: 1024x768 (+4096), 24 bits Mode 0x031a: 1280x1024 (+2560), 16 bits Mode 0x031b: 1280x1024 (+5120), 24 bits Mode 0x0330: 320x200 (+320), 8 bits Mode 0x0331: 320x400 (+320), 8 bits Mode 0x0332: 320x400 (+640), 16 bits Mode 0x0333: 320x400 (+1280), 24 bits Mode 0x0334: 320x240 (+320), 8 bits Mode 0x0335: 320x240 (+640), 16 bits Mode 0x0336: 320x240 (+1280), 24 bits Mode 0x033d: 640x400 (+1280), 16 bits Mode 0x033e: 640x400 (+2560), 24 bits Mode 0x034b: 1920x1080 (+1920), 8 bits Mode 0x034c: 1920x1080 (+3840), 16 bits Mode 0x034d: 1920x1080 (+7680), 24 bits Mode 0x0360: 1280x800 (+1280), 8 bits Mode 0x0361: 1280x800 (+5120), 24 bits Config Status: cfg=no, avail=yes, need=no, active=unknown The nouveaux driver's in use lsmod | grep nouveau nouveau 1479611 0 mxm_wmi 13021 1 nouveau wmi 19193 2 mxm_wmi,nouveau ttm 105728 1 nouveau drm_kms_helper 125995 1 nouveau drm 363977 3 ttm,drm_kms_helper,nouveau video 28709 1 nouveau button 14015 1 nouveau i2c_algo_bit 13413 2 igb,nouveau I edited the grub2 config to include /etc/default/grub GRUB_USE_LINUXEFI=true GRUB_GFXMODE=1920x1080 GRUB_TERMINAL_INPUT="console serial" GRUB_TERMINAL_OUTPUT="gfxterm serial" GRUB_GFXPAYLOAD_LINUX=keep GRUB_CMDLINE_LINUX=" ... vga=0x034c" ... After grub2-mkconfig -o /boot/grub2/grub.cfg reboot The console still displays same as before, only at ~ 1024x768. I just want small text, no graphics. What settings do I need to add or change? LT -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 14