Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-5463

FIWARE.Request.Lab.Lannion.FI-LAB VM won't start due to disk mounting issues!

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Critical
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-LAB-HELP
        • Labels:
          None

          Description

          Hi,

          I'm experiencing the following issue after rebooting my virtual machine,
          i.e. "ChargeAdvisorVM", hosted on FI-LAB.

          I didn't made any changes to the VM, I've simply rebooted it and it
          stops here :

          */EXT4-fs (dm-0): Couldn't remount RDWR because of unprocessed orphan
          inode list. Please umount/remount instead./**/
          /*/An error occurred while mounting /./*/
          /*
          Please, could you help me to fix this issue?
          Thanks in advance.

          Regards,
          Letterio

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-incense-coaching@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-incense-coaching mailing list
          Fiware-incense-coaching@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-incense-coaching
          [Created via e-mail received from: Letterio Zuccaro <letterio.zuccaro@ares2t.com>]

            Issue Links

            relates to

            extRequest - Request from external stakeholder received in the help desk HELC-1167 FIWARE.Request.Coach.INCENSe.FI-LAB VM won't start due to disk mounting issues!

            • Critical - Crashes, loss of data, severe memory leak.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              6 older comments
              Hide
              Permalink
              fw.ext.user FW External User added a comment -

              Dear Letterio,

              It seems that the problem was concerning the boot disk.
              I did a fsck over your instance.

              Can you try if your instance working well?
              Please send us a feedback to close this ticket.

              BR,
              Cristian

              Show
              fw.ext.user FW External User added a comment - Dear Letterio, It seems that the problem was concerning the boot disk. I did a fsck over your instance. Can you try if your instance working well? Please send us a feedback to close this ticket. BR, Cristian
              Hide
              Permalink
              fw.ext.user FW External User added a comment -

              Dear Cristian,

              I've just checked, it works well.
              Thanks for your support.

              BR,
              Letterio

              Show
              fw.ext.user FW External User added a comment - Dear Cristian, I've just checked, it works well. Thanks for your support. BR, Letterio
              Hide
              Permalink
              lannionsupport Lannion Node Helpdesk added a comment -

              VM works well.
              Ticket closed.
              BR,
              Cristian

              Show
              lannionsupport Lannion Node Helpdesk added a comment - VM works well. Ticket closed. BR, Cristian
              Hide
              Permalink
              fw.ext.user FW External User added a comment -

              Dear Christian,

              I'm experiencing the disk issue again (see the attachment).
              Could you please check that the VM is booting well?

              Thanks in advance.

              Best,
              Letterio

              Show
              fw.ext.user FW External User added a comment - Dear Christian, I'm experiencing the disk issue again (see the attachment). Could you please check that the VM is booting well? Thanks in advance. Best, Letterio
              Hide
              Permalink
              fw.ext.user FW External User added a comment - - edited

              Dear Letterio,

              It seems that it was a disk issue... after a fsck the problem was solved.
              Please check now your VM;

              BR,
              Cristian

              ----Message d'origine----
              De : Letterio Zuccaro letterio.zuccaro@ares2t.com
              Envoyé : lundi 8 février 2016 17:36
              À : Cristian CMECIU
              Cc : FW External User (JIRA); support-lannion@imaginlab.fr
              Objet : Re: [FI-WARE-JIRA] (HELP-5463) [Fiware-incense-coaching] [URGENT] FI-LAB VM won't start due to disk mounting issues!

              Dear Christian,

              I'm experiencing the disk issue again (see the attachment).
              Could you please check that the VM is booting well?

              Thanks in advance.

              Best,
              Letterio

              Show
              fw.ext.user FW External User added a comment - - edited Dear Letterio, It seems that it was a disk issue... after a fsck the problem was solved. Please check now your VM; BR, Cristian ---- Message d'origine ---- De : Letterio Zuccaro letterio.zuccaro@ares2t.com Envoyé : lundi 8 février 2016 17:36 À : Cristian CMECIU Cc : FW External User (JIRA); support-lannion@imaginlab.fr Objet : Re: [FI-WARE-JIRA] ( HELP-5463 ) [Fiware-incense-coaching] [URGENT] FI-LAB VM won't start due to disk mounting issues! Dear Christian, I'm experiencing the disk issue again (see the attachment). Could you please check that the VM is booting well? Thanks in advance. Best, Letterio

                People

                • Assignee:
                  lannionsupport Lannion Node Helpdesk
                  Reporter:
                  fw.ext.user FW External User
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: