RE: error enabling swap space device hda3. No such file ordirectory.

From: Evan Panagiotopoulos (epanagio_at_pcsd.k12.ny.us)
Date: 05/29/05

  • Next message: Evan Panagiotopoulos: "RE: error enabling swap space device hda3. No such fileordirectory." 
    To: redhat-list@redhat.com
Date: Sun, 29 May 2005 11:26:22 -0400

    Here is the output

    swapon -s
    Filename Type Size Used Priority
    /dev/hda3 partition 1020116 0 -1

    >
    >---- Original Message ----
    >From: vkarasik@nds.com
    >To: redhat-list@redhat.com
    >Subject: RE: error enabling swap space device hda3. No such file
    >ordirectory.
    >Date: Sun, 29 May 2005 18:06:23 +0300
    >
    >>Please check if RHEL 3 uses hda3 as swap:
    >>
    >>Swapon -s
    >>
    >>Rgds,
    >>Vitaly
    >>
    >>
    >>> -----Original Message-----
    >>> From: redhat-list-bounces@redhat.com
    >>> [mailto:redhat-list-bounces@redhat.com] On Behalf Of Evan
    >>> Panagiotopoulos
    >>> Sent: Saturday, May 28, 2005 5:39 PM
    >>> To: redhat-list@redhat.com
    >>> Subject: error enabling swap space device hda3. No such file
    >>> or directory.
    >>>
    >>> I am trying to upgrade from EL 3 to EL 4. I tested the 4 CDs
    >>> and they are OK. I select the Upgrade option and press OK and
    >>> I see the
    >>> following:
    >>>
    >>> error enabling swap space device hda3. No such file or directory.
    >>> This most likely means this swap partition has not been
    >initialized.
    >>> Press OK to reboot.
    >>>
    >>> Any ideas?
    >>>
    >>> --
    >>> redhat-list mailing list
    >>> unsubscribe
    >mailto:redhat-list-request@redhat.com?subject=unsubscribe
    >>> https://www.redhat.com/mailman/listinfo/redhat-list
    >>>
    >>********************************************************************
    >***************
    >>Information contained in this email message is intended only for use
    >of the individual or entity named above. If the reader of this
    >message is not the intended recipient, or the employee or agent
    >responsible to deliver it to the intended recipient, you are hereby
    >notified that any dissemination, distribution or copying of this
    >communication is strictly prohibited. If you have received this
    >communication in error, please immediately notify the
    >postmaster@nds.com and destroy the original message.
    >>********************************************************************
    >***************
    >>
    >>--
    >>redhat-list mailing list
    >>unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscrib
    >e
    >>https://www.redhat.com/mailman/listinfo/redhat-list 

    -- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
  • Next message: Evan Panagiotopoulos: "RE: error enabling swap space device hda3. No such fileordirectory."

    Relevant Pages

    • Re: change date of files in a directory
      ... value specified by the time parameter ... confidential information solely for the use of the intended recipient. ... the reader of this message is not the intended recipient, ... communication in error, please immediately notify CDS @ 248-478-7000. ...
      (AIX-L)
    • HELP
      ... If the reader of this message is not the intended ... message to the intended recipient, you are hereby notified that any ... communication or any of its attachments is strictly prohibited. ...
      (Fedora)
    • Re: OT Annoying Habits
      ... product doctrine and thus protected from disclosure. ... If the reader ... distribution or copying of this communication is strictly prohibited. ...
      (comp.lang.python)
    • Re: OT Annoying Habits (Was: when format strings attack)
      ... product doctrine and thus protected from disclosure. ... If the reader ... distribution or copying of this communication is strictly prohibited. ...
      (comp.lang.python)
    • Re: Worst Predictions of All Time
      ... not the intended recipient, you are hereby notified that any disclosure, ... The information contained in this communication (including any ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
      (bit.listserv.ibm-main)