SAPGUI problem on FEDORA linux

Hi friends,
we have worked on window OS.
recently we have changed the OS , we are working on FEDORA linux,
comming to problem.
production server and quality server are working fine.
but development server is not working.
when ever we have open this server it will not respond, it shows only blank screen.
the GUI is completly goes to wait stage. it shows a white screen.
what is the problem please post the solution immediatly.
Regards,
Sateesh.

Dear sateesh,
could you please explain in more detail what you are referring to when saying
In our organization sap is installed on fedora linux with 'jre1.6.0_14'
In this forum, we normally assume that you mean SAP on the server side. But the subject of this thread is called, SAPGUI problem, therefore I assume that you are only facing SAPGUI problems on the client side (and not the server side).
SAPGUI problem on the Client side:
For officially supported distributions for the JavaGUI [1] are mentioned in SAP note 959236 - Supported Java frontend platforms for 7.10 / 7.11 / 7.01. This note says that Fedora Linux is supported, so you are on the safe side here.
Also, the JavaGUI is fully compatible with Java 1.6. I', using the JavaGUI with jdk1.6.0_14 without any problems. I'm using a small script to start the JavaGUI on my machine. You should try it youself. Please note that you have to adept the paths accordingly. Sometimes it happens that some variables are not set correctly. Also, the Java path is very important!
#!/bin/sh
# SAP GUI Path
SGP=/home/hannes/data/progs/sapgui/SAPGUI7.10rev8
export SNC_LIB=/usr/lib/libsecude.so
export CREDDIR=/dev/shm/ssoclient-`id -u`
export JAVA_HOME=/home/hannes/data/progs/jdk1.5.0_16
export PLATIN_JAVA_VER=1.5.0_16
export PLATIN_JAVA=$JAVA_HOME/bin/java
export LD_LIBRARY_PATH=$SGP/bin
$SGP/bin/guilogon
Thanks,
  Hannes
[1]: ftp://ftp.sap.com/pub/sapgui/java/710r8/

Similar Messages

  • Installation problem on fedora linux

    Hi
    I am trying to install oracle 10g to Fedora Linux.
    When I type ./runInstaller :
    Exception java.lang.UnsatisfiedLinkError: /tmp/OraInstall2007-08-21_12-40-12AM/jre/1.4.2/lib/i386/libawt.so:...........................
    Exception in thread main java.lang.NoClassDefFoundError
    Please help me to solve this problem

    Ricardinho,
    try post full error message (or stack trace) because in this case we can only guess...
    Also when you post name of Linux distribution then don't forget post the version.
    Anyway according to partial error message I think there is missing libXp.so.6 library on your OS.
    So execute "yum install libXp" to install required package. Od locate the package on installtion media and install it via "rpm -ivh" command.
    Note: In FC5 and later libXp.so.6 is included in libXp package. In FC4 and older releases you need to install xorg-deprecated-libs package.

  • Error in installation Oracle 8.1.6 on Fedora linux

    I am getting the following error message while installing Oracle 8i release 2 (8.1.6) for linux intel on Fedora Linux.
    "Symbol errorno, version GLIBC-2.0 not defined in libc.so.6 with link time reference (libzip.so)"
    Earlier I have sucessfully installed on Redhat linux 8.0 without any problems.
    Kindly help

    All the rpms mentioned in above link are already installed. the same error comes with Oracle 9i/AS also.
    I quote here the exact error message:-
    [oracle@sczopngs cdrom]$ ./runInstaller
    [oracle@sczopngs cdrom]$ Initializing Java Virtual Machine from /tmp/OraInstall/ jre/bin/jre. Please wait...
    /tmp/OraInstall/jre/lib/linux/native_threads/libzip.so: symbol errno, version GL IBC_2.0 not defined in file libc.so.6 with link time reference (libzip.so)
    Unable to initialize threads: cannot find class java/lang/Thread
    I don't have newer version of Oracle for linux , but dont think a newer version will solve the above problem as the same message is coming with Oracle 9i/AS also when I tried just to test..
    This may problem with new relase of Linux Fedora with kernel 2.6.2.

  • Can't get windows 8.1 with dual boot for fedora (linux) . system is UEFI .

    Can't get  windows 8.1 with  dual boot for fedora (linux) . system is UEFI .

    Hi,
    Any update here?
    We may seek help at Fedora forum as Milos suggested, if convenient we could share the related thread link here for reference.
    In addition, please also check the information in the similar thread:
    Dual Boot Windows 8 and Linux?
    Best regards
    Michael Shao
    TechNet Community Support

  • I am using jboss 4.2, java5.0 and Fedora Linux Enterprise Version 4.0 with

    Hi,
    I am using jboss 4.2, java5.0 and Fedora Linux Enterprise Version 4.0 with kernel 2.6 and NPTL 2.3.4
    I am using open source network chart generation API provided by geosoft ( http://geosoft.no/graphics/). This API generates chart into swing window.
    I wrote the code to change this swing window into web browser compatible jpeg image. I used thread to generate the image. It is working fine, for one user and no other processes running on the application.
    ISSUE:- When more than 5 users hit the application at the same time, some images get generated, some donot, there is no fixed trend to this image generation process.
    I analyzed CPU timing, it is using 100% CPU and after the images are generated / not generated, the CU usage goes down to zero.
    When I used the same code with Linux 9.0 (kernel 2.4, NPTL � 0.6), rest remain the same, it is working perfectly fine with more than 10 users, with all images being generated within 30 secs
    Can somebody help me out to figure out whether it is a kernel issue / NPTL issue? Does it have something to do with thread processing?
    Code for network chart generation :-
    NetworkGenerator ntw=new NetworkGenerator();
    BufferedImage img;
    ntw.setVectRootNodes(vectRootNodes);
    ntw.setHashChildNodeNames(hashNodeData);
    ntw.setHashNodeRelation(hashNodeRelation);
    ntw.setHashNodesCreated(hashNodesCreated);
    ntw.setSupplyChainBean(supplyChainBean);
    Thread t=new Thread(ntw);
    t.setPriority(Thread.MAX_PRIORITY);
    t.start();
    try{
    t.join();
    catch(Exception e)
    DebugManager.doDebug(className.toString(),e);
    if(t!=null)
    System.out.println(t.getState().name());
    System.out.println(t.isAlive());
    public class NetworkGenerator extends JFrame implements Runnable{
    public void run()
    //call the garbage collector
    System.gc();
    // Create the graphic canvas
    window = new no.geosoft.cc.graphics.GWindow();
    window.getCanvas().setSize(screenWidth,screenHt );
    // Create the GUI
    JPanel topLevel = new JPanel();
    topLevel.setBackground(new Color(255,255,255)) ;
    topLevel.setLayout (new BorderLayout());
    getContentPane().add (topLevel);
    topLevel.add (window.getCanvas(), BorderLayout.CENTER);
    topLevel.setVisible(true);
    // Create scene with default viewport
    scene = new no.geosoft.cc.graphics.GScene(window, "My Scene"+ (new Date().getTime()));
    no.geosoft.cc.graphics.GStyle style = new no.geosoft.cc.graphics.GStyle();
    style.setForegroundColor (new Color (0, 0, 0));
    style.setBackgroundColor (new Color (255, 255, 255));
    style.setFont (new Font ("Arial", Font.BOLD, 10));
    scene.setStyle (style);
    int xPos=minY ;
    int yPos=0;
    int noofChild=vectRootNodes.size();
    int dev=(screenHt -minY )/(noofChild+1);
    int newDev=Math.round(dev-(dev/5));
    //log.debug("---------noofChild-----------------------------------"+noofChild);
    if(!hashNodesCreated.isEmpty())
    for(int i=0;i<noofChild;i++)
    yPos=minY +(dev*(i+1));
    String nodeName = vectRootNodes.get(i).toString();
    log.debug("root nodename===="+nodeName+" with ypos :"+yPos);
    //log.debug("nodeName=="+nodeName);
    //create root nodes
    Node rootNode = createChildNode( nodeName,minY,screenHt,xPos, yPos ,newDev,1);
    scene.add(rootNode);
    log.debug("screenWidth ===="+screenWidth );
    // if(screenWidth>minExtXval)
    // minExtXval = screenWidth;
    // w2 o
    // * |
    // * |
    // * |
    // * w0 o-------o w1
    double w0[] = {0.0,screenHt ,0.0};
    double w1[] = {screenWidth,screenHt,0.0};
    double w2[] = {0.0,0.0,0.0};
    scene.setWorldExtent (w0, w1, w2);
    this.pack();
    Thanks in advance.

    How do I do that as I checked for it in utilities and is not there? Thanks in advance

  • Red Hat Linux project merges with Fedora Linux project

    Will this mean that the Fedora Linux project will become the officially supported Linux platform for Java releases in the near future? Please reference http://fedora.redhat.com/
    What will be the supported Linux platform for v1.5?

    A sidenote: I have been happily using a plethora of JDK and J2SE versions on different versiond of SUSE Linux although SUSE was never "the" officially supported Linux distribution.

  • Install 9I in Fedora Linux

    Que necesito hacer para poder instalar Oracle 9I en Fedora Linux core 1.

    En realidad yo nunco he escuchado de esa versi�n de
    Linux. Si tienes una cuenta metalink puedes revisar en:
    Certify & Availability . En la matrix de certificaciones
    podras saber si Oracle es certificado para dicha versi�n.
    De ante mano me temo que no esta certificada.
    http://metalink.oracle.com
    Siempre que preguntes aqui hazlo en Ingl�s o ser�
    muy dificil que alguien te conteste.
    Yo respondo preguntas todos los d�as y te podr�
    responder pero los demas no porque el idioma que se
    maneja aca es el ingl�s.
    Buena Suerte
    Joel P�rez

  • Nokia CS-10 Fedora Linux, doesn't make detection

    Hi!
    I'm looking for a documentation to install the CS-10 Nokia modem.My OS is Fedora Linux 12.
    I use the scripts of:
    http://www.islascruz.org/html/index.php/blog/show/Nokia-Internet-Stick-CS-10-on-Linux.html
    But, in the first, I don't see the CD drive (the modem, that say the page). I found a probably solution in:
    http://europe.nokia.com/support/product-support/cs-10/software
    I downloaded the rmp package of the page, but I don't see a change.  Firstly, like after, I don't see a CD/DVD drive to unmount or/and eject.
    thnx a lot

    I answer to me
    Firstly, I have the USB modem without a CDROM behavior ( Like is saw in Ubuntu and Debian ). But my Fedora 12 doesn´t.
    I used the advice:
    http://www.islascruz.org/html/index.php/blog/show/Nokia-Internet-Stick-CS-10-on-Linux.html
    But weren't give me a result. I was install
    Before I saw the device with the command "lsusb" like:
    Bus 001 Device 005: ID 0421:060c Nokia Mobile Phones
    Like the reference (in the end of this comment), I write the next code in the /etc/udev/rules.d/
    SUBSYSTEMS=="usb", SYSFS{idVendor}=="0421", SYSFS{idProduct}=="060c", ACTION=="add", RUN+="/usr/bin/eject -s %k", OPTIONS+="last_rule"
    Next I was reboot the machine. Then, I see the device shining the red light, and next the green ( brefore I was config a 3G Telcel connection).
    Reference:
    http://blog.nielshorn.net/2010/02/using-a-nokia-cs-10-gsm-modem-on-slackware/
    Anyway thnx

  • Oracle 10g for Fedora Linux 3 with Kernel 2.6.9

    Can any body suggest a link, from where I can download the Oracle database 10g for Fedora Core 3 Linux with Kernel version 2.6.9-1*.
    I went through the oracle site site but i was not able to find a one for Fedora 3 instead i found for Fedora 4.
    Thanks.......
    Suneel

    You will not find one exactly as you require.
    As I suggested in the duplicate link
    Oracle 10g for Fedora Linux 3 with Kernel 2.6.9 you need to take a version of Oracle that seems to close to your Linux and then carefully tinker to make it work.,

  • Javascript Adobe Reader problem in some linux distributions

    Adobe Reader doesn't execute initial javascript code of 3D scene in pdf document. With friends we've tested several linux distributions, namely CentOS, Ubuntu, Arch Linux, Mandriva, OpenSUSE. Also several Adobe Reader versions like 9.4.6 or 9.1. No luck. For some reason though, it works fine in Fedora (with exactly the same Adobe Reader). Here is an example pdf for test: http://www.2shared.com/document/LIbyWm_ … _dice.html . Just open the mysterious_dice.pdf and you should see a rotating dice. If you dont, javascript wasn't executed properly (it should be easy to check in Windows 7/XP or Fedora).
    We thought that something is wrong in Reader settings (like disabled javascript), but javascript was always allowed. Then that maybe it is linux Adobe Reader bug, but again, why does it work in Fedora? So maybe some package(s) or something.
    Another example is the Asymptote application, which uses javascript at the beginning for some scene settings (lights, camera position, etc) and especially with orthographic projection this problem shows up. More about this here: http://sourceforge.net/projects/asympto … ic/4021157.
    Any idea what might be wrong with this? I will just add that javascript later on works, only the initial code is ignored. Thanks for any suggestion.

    Interesting, just to be sure, was your dice spinning around? If it was, then it really works. My friend with Arch i686 just tried it with Adobe Reader 9.4.2, same settings and the dice was static. He provided also screenshot to show how it looks on his system together with some info:
    Last edited by Sil (2011-11-17 17:05:55)

  • System freezes due to hard disk problems only on Linux (not windows)

    Intro/context:
    Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
    I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
    tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
    What i've done so far:
    The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
    I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
    Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
    I found no firmware update for this hard drive.
    So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
    Info:
    Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
    Some logs i've recollected all this time:
    journalctl -xfa --system
    abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
    abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
    abr 21 13:51:24 echoes kernel: ata1: hard resetting link
    abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 13:51:24 echoes kernel: ata1: EH complete
    abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
    res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
    dmesg
    [55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
    [55661.023034] ata1.00: failed command: READ FPDMA QUEUED
    [55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [55661.023042] ata1.00: status: { DRDY }
    [55661.023046] ata1: hard resetting link
    [55666.358537] ata1: link is slow to respond, please be patient (ready=0)
    [55671.053813] ata1: COMRESET failed (errno=-16)
    [55671.053819] ata1: hard resetting link
    [55676.389438] ata1: link is slow to respond, please be patient (ready=0)
    [55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [55681.320305] ata1.00: configured for UDMA/100
    [55681.320319] ata1.00: device reported invalid CHS sector 0
    [55681.320349] ata1: EH complete
    [55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
    [55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
    dmesg
    [102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
    [102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
    [102884.890333] systemd[1]: systemd-journald.service failed.
    [102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
    [102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    [104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
    [104179.117369] ata1.00: failed command: READ FPDMA QUEUED
    [104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [104179.117377] ata1.00: status: { DRDY }
    [104179.117381] ata1: hard resetting link
    [104184.453382] ata1: link is slow to respond, please be patient (ready=0)
    [104189.149114] ata1: COMRESET failed (errno=-16)
    [104189.149121] ata1: hard resetting link
    [104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [104189.952982] ata1.00: configured for UDMA/100
    [104189.952989] ata1.00: device reported invalid CHS sector 0
    [104189.953004] ata1: EH complete
    [104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    [104508.223798] ata1.00: failed command: SMART
    [104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [104508.223806] ata1.00: status: { DRDY }
    [104508.223810] ata1: hard resetting link
    [104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [104510.698126] ata1.00: configured for UDMA/100
    [104510.698157] ata1: EH complete
    One of the latest and worse
    journalctl -xfa --system
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
    res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
    abr 22 12:57:11 echoes kernel: ata1: EH complete
    abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
    abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
    abr 22 12:57:11 echoes kernel: ata1: EH complete
    Current smart status:
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: Toshiba 2.5" HDD MQ01ABD...
    Device Model: TOSHIBA MQ01ABD100
    Serial Number: Y44MT611T
    LU WWN Device Id: 5 000039 5e1a80e85
    Firmware Version: AX1P5E
    User Capacity: 1,000,204,886,016 bytes [1.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5400 rpm
    Form Factor: 2.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS (minor revision not indicated)
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Sun May 3 16:42:06 2015 ART
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 120) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 234) minutes.
    SCT capabilities: (0x003d) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    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 0x000b 100 100 050 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
    7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
    10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
    193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
    194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
    197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
    220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
    222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
    223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
    226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
    240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
    SMART Error Log Version: 1
    No Errors Logged
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Vendor (0x50) Completed without error 00% 611 -
    # 2 Short offline Completed without error 00% 611 -
    # 3 Short offline Completed without error 00% 597 -
    # 4 Vendor (0x50) Completed without error 00% 583 -
    # 5 Short offline Completed without error 00% 583 -
    # 6 Vendor (0x50) Completed without error 00% 575 -
    # 7 Short offline Completed without error 00% 575 -
    # 8 Short offline Completed without error 00% 547 -
    # 9 Extended offline Completed without error 00% 529 -
    #10 Short offline Completed without error 00% 355 -
    #11 Short offline Completed without error 00% 355 -
    #12 Extended offline Aborted by host 70% 355 -
    #13 Short offline Completed without error 00% 319 -
    #14 Vendor (0x50) Completed without error 00% 13 -
    #15 Short offline Completed without error 00% 13 -
    #16 Short offline Completed without error 00% 12 -
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
    Last edited by jesu (2015-05-03 19:42:53)

    Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
    Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
    $ lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 931,5G 0 disk
    ├─sda1 8:1 0 1000M 0 part
    ├─sda2 8:2 0 260M 0 part /boot
    ├─sda3 8:3 0 207,7G 0 part
    ├─sda4 8:4 0 25G 0 part
    ├─sda5 8:5 0 14,8G 0 part
    ├─sda6 8:6 0 80,5G 0 part /
    ├─sda8 8:8 0 599G 0 part /home
    └─sda9 8:9 0 2G 0 part [SWAP]
    So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
    Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
    Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
    dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
    [ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
    [ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
    [ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 653.821735] ata1.00: status: { DRDY }
    [ 653.821739] ata1: hard resetting link
    [ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
    [ 663.851604] ata1: COMRESET failed (errno=-16)
    [ 663.851610] ata1: hard resetting link
    [ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
    [ 673.881456] ata1: COMRESET failed (errno=-16)
    [ 673.881462] ata1: hard resetting link
    [ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
    [ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 703.012578] ata1.00: configured for UDMA/100
    [ 703.012584] ata1.00: device reported invalid CHS sector 0
    [ 703.012599] ata1: EH complete
    [ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
    [ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
    [ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
    [ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
    [ 742.443506] Buffer I/O error on device sda8, logical block 9323208
    [ 742.443508] Buffer I/O error on device sda8, logical block 9323209
    [ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
    [ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
    [ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
    [ 742.443524] Buffer I/O error on device sda8, logical block 9323216
    [ 742.443526] Buffer I/O error on device sda8, logical block 9323217
    [ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
    [ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
    [ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
    [ 742.443540] Buffer I/O error on device sda8, logical block 9323226
    [ 742.443542] Buffer I/O error on device sda8, logical block 9323227
    [ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
    [ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
    [ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
    [ 742.443555] Buffer I/O error on device sda8, logical block 9323234
    [ 742.443557] Buffer I/O error on device sda8, logical block 9323235
    [ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
    [ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
    [ 756.188116] systemd[1]: systemd-journald.service failed.
    [ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
    [ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
    [ 756.189143] systemd[1]: Listening on Journal Audit Socket.
    [ 756.189801] systemd[1]: Starting Journal Service...
    [ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
    [ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 758.503041] systemd[1]: Started Journal Service.
    [ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
    [ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867747] ata1.00: status: { DRDY }
    [ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867763] ata1.00: status: { DRDY }
    [ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867778] ata1.00: status: { DRDY }
    [ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867793] ata1.00: status: { DRDY }
    [ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867807] ata1.00: status: { DRDY }
    [ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867821] ata1.00: status: { DRDY }
    [ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867835] ata1.00: status: { DRDY }
    [ 974.867841] ata1: hard resetting link
    [ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
    [ 984.900902] ata1: COMRESET failed (errno=-16)
    [ 984.900908] ata1: hard resetting link
    [ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
    [ 994.930829] ata1: COMRESET failed (errno=-16)
    [ 994.930836] ata1: hard resetting link
    [ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 997.014012] ata1.00: configured for UDMA/100
    [ 997.014020] ata1.00: device reported invalid CHS sector 0
    [ 997.014023] ata1.00: device reported invalid CHS sector 0
    [ 997.014025] ata1.00: device reported invalid CHS sector 0
    [ 997.014026] ata1.00: device reported invalid CHS sector 0
    [ 997.014028] ata1.00: device reported invalid CHS sector 0
    [ 997.014030] ata1.00: device reported invalid CHS sector 0
    [ 997.014031] ata1.00: device reported invalid CHS sector 0
    [ 997.014065] ata1: EH complete
    There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
    root and home partitions are both ext4.

  • Oracle 10g Installation Problem on SUSE Linux 10

    Hello Friends,
    I want to install SAP Solution Manager 7.0 with Oracle 10g on SUSE Linux 10.0.
    But, while starting the Installation i am getting following Errors.
    Starting Oracle Universal Installer...
    Checking installer requirements...
    Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1,
    asianux-2 or SuSE-10
                                          Passed
    All installer requirements met.
    Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-22_03-59-38PM. Please wait ...
    Error in writing to directory /tmp/OraInstall2009-04-22_03-59-38PM. Please ensure that this directory is
    writable and has atleast 60 MB of disk space. Installation cannot continue.
    : Success
    I have checked the Permissions and the Size of /tmp Directory, which is as followed:
    drwxr-xr-x  11 root root    0 2009-04-22 21:19 sys
    drwxrwxrwt  52 root root 1824 2009-04-22 16:00 tmp
    drwxr-xr-x  15 root root  408 2009-04-19 14:43 usr
    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/sda10             2104376     73112   2031264   4% /tmp
    I am starting the Oracle 10g Installation within orasm7 User which is a member of dba, users, disk groups.
    The directories which are created upon starting the Oracle Installation in /tmp directory are having the situations as followed:
    drwxr-xr-x 3 orasm7   dba          128 2009-04-21 18:41 OraInstall2009-04-21_06-41-14PM
    drwxr-xr-x 3 orasm7   dba          128 2009-04-21 18:41 OraInstall2009-04-21_06-41-25PM
    drwxr-xr-x 3 orasm7   dba          128 2009-04-22 15:59 OraInstall2009-04-22_03-59-38PM
    The Oracle Installation log is as follwoed:
    Using paramFile: /home/MyData/51031676/database/install/oraparam.ini
    Checking installer requirements...
    Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1, asianux-2 or SuSE-10
                                          Passed
    All installer requirements met.
    The commandline for unzip:
    /home/MyData/51031676/database/install/unzip -qqq ../stage/Components/oracle.swd.jre/1.4.2.0.8
    /1/DataFiles/\*.jar -d /tmp/OraInstall2009-04-22_03-59-38PM
    I have set DISPLAY variable in this way before starting Installation:
    DISPLAY=$HOSTNAME:0.0
    export DISPLAY
    I tried to search the solution over the internet for this kind of problem, but i am not able to find its solution. Even i tried to start the Orale installation using this parameter: ./runInstaller ignoreSysPrereqs, but still it is giving the same unexpected error.
    I have a doubt on File/Directory permissions which are created for Installation in /tmp. The umask setiing of the system is 0022.
    Please, help me for this issue.
    Thanks & Regards,
    Bhavik G. Shroff

    Hi Markus,
    How are you ?
    Thank you very much for your reply.
    I was executing wrong runInstaller file. RUNINSTALLER is right file for starting the execution. But still i am facing the same error, which is as followed.
    Preparing response files. Please wait:
    ======================================
    Working on /home/MyData/51031676/database/SAP/SVRCUSTOM.RSP
    /home/MyData/51031676/database/SAP/SVRCUSTOM.RSP --> /tmp/.orainst_rsp.27450: Done
    Starting Oracle Universal Installer...
    Checking installer requirements...
    Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1, asianux-2 or SuSE-10
                                          Passed
    All installer requirements met.
    Preparing to launch Oracle Universal Installer from /home/orasm7/tmpora/OraInstall2009-04-22_05-25-26PM. Please wait ...
    Error in writing to directory /home/orasm7/tmpora/OraInstall2009-04-22_05-25-26PM. Please ensure that
    this directory is writable and has atleast 60 MB of disk space. Installation cannot continue.
    : Success
    SHROFF:~ # cd /home/orasm7/tmpora/
    SHROFF:/home/orasm7/tmpora # ll
    total 0
    drwxr-xr-x 3 orasm7 dba 128 Apr 22 17:25 OraInstall2009-04-22_05-25-26PM
    SHROFF:/home/orasm7/tmpora # cd OraInstall2009-04-22_05-25-26PM/
    SHROFF:/home/orasm7/tmpora/OraInstall2009-04-22_05-25-26PM # ll
    total 4
    drwxr-xr-x 2 orasm7 dba 304 Apr 22 17:25 images
    -rwxr-xr-x 1 orasm7 dba 504 Apr 22 17:25 installActions2009-04-22_05-25-26PM.log
    SHROFF:/home/orasm7/tmpora/OraInstall2009-04-22_05-25-26PM #
    I have a doubt on tmp_netca_file & tmp_dbca_file variable.
    Please give your suggestion for the same.
    Regards,
    Bhavik G. Shroff
    Edited by: Bhavik G. Shroff on Apr 22, 2009 2:10 PM

  • J2esdk installation problem on fedora 2

    Hello All
    I am tring to install the j2eesdk-1_4_01-linux.bin on my newly intalled redhat fedora system
    while running on command prompt as
    $./j2eesdk-1_4_01-linux.bin
    it gives error message like
    ./j2eesdk-1_4_01-linux.bin: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
    please help me
    Thank you

    This hang is a known issue on some Linux distributions and seems to triggered by particular environment settings. To work around it, you can run:
    /j2eesdk-1_4_01-linux.bin -javahome <java_directory>
    where java_directory is location where you have preexisting JDK or JRE 1.4.1 or higher,
    If you don't have preexisting JRE or JDK installation, you can also take a look at workaround (unzip and invoking Java installation wizard directly) described in this thread:
    http://forum.java.sun.com/thread.jsp?forum=136&thread=507826

  • Oracle 10g XE installation problem on Ubuntu Linux, Oracle will not start

    Hi,
    After installing the pakages the error is when I call sqlplus and login as SYS :-
    oracleXE: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
    ERROR:
    ORA-12547: TNS:lost contact
    What I have done:-
    My system is 64 bit AMD.
    I installed .deb package on Ubuntu 9.04 server. I installed the following packages.
    1.     ibc6-i386
    2.     libaio_0.3.104-1_i386.deb
    3.     bc
    4.     oracle-xe-universal_10.2.0.1-1.1_i386.deb.
    The Oracle processes do not start after running /etc/init.d/oracle-xe start.
    I can tnsping from the local machine.
    dpkg -l |grep libaio gives the following:
    ii libaio1 0.3.107-3ubuntu1 Linux kernel AIO access library - shared lib

    I have been running XE on 9.04 (32bit on my laptop - 64bit on my workstation) and both works fine. I had no problem installing. I followed the directions in documents I found on Ubuntu forums and also google. The document I used to install on 64bit was from http://littlebrain.org
    I remember using
    dpkg -i --force-architecture libaio1_0.3.107-1ubuntu1_i386.deb
    dpkg -i --force-architecture libaio-dev_0.3.107-1ubuntu1_i386.deb
    dpkg -i --force-architecture libaio1-dbg_0.3.107-1ubuntu1_i386.deb
    dpkg -i --force-architecture oracle-xe_10.2.0.1-1.0_i386.deb
    and then I used the ./oracle-xe configure as root, the installation was ok - and I have even updated the APEX version to 3.2.1 on the XE installation running on my 64bit Ubuntu 9.04
    hope this proves useful
    R/ Zafer

  • Oracle9i R2 (9.2.0.2.0), installation problem on RH Linux 3.0 on IA64.

    Hi,
    While installing Oracle9i release 2 (9.2.0.2.0),on Redhat Linux 3.0 on IA64 itanium processor, Oracle Universal Installer starts and copies some of the files and stops installation at 0% without giving any error.
    After selecting NO to Create Database,OUI install starts, and it has stopped at
    "Installing Java Runtime Environment 1.4.1.0.0" ,
    "Link pending" , "Copying LICENSE".
    Please help me in solving this problem.
    Thanks in adv..
    Venkatakrishna

    Ur kernel Parameter is not tuned to 2.4.1

Maybe you are looking for