Last week we got a problem with our system. Our SO was OpenSuse 13.1 in a RAID1 and the storage in RAD5 (14 disk, 2TB each). When we want to boot, we got a message:
“[FAILED] Failed to mount /SRV
see ‘systemctl status srv.mount’ for details
[DEPEND] Dependency failed for Local File Systems.
Welcome to emergency mode! After logging in, type “journalctl -xb” to view
system logs, “systemctl reboot” to reboot, “systemctl defaul” to try again
to boot into default mode.”
this message is in a infinite loop and cannot type anything, but the system recognize CONTROL + ALT + SUPR.
I really have NO idea why this is happening or what I have to do.
Do you have anyidea of what is happening or what can I do?
sorry is “srv” not SRV. We only installed “webmin” (a web control panel). When it boot, I only have 2 options (“openSUSE 13.1” and “Advanced options for openSUSE”). when the message “journalctl -xb” appears, I cannot type anything and the message is in an infinite loop. It only recognize the CONTROL + ALT + SUPR
Sorry, but I do not understand this. When the message about “login in emergency mode …” appears, you should see a login prompt then. Isn’t that the case?
Or o you mean that message is spontaniously repeated again and again without you doing anything?
And choosinf for boot in Advanced options should enable you to boot in tun level 1 and then login as root in the console to do that edit.
Also I asked if you hit Esc to see what happens!!!
You might not see a login prompt because of a loop of something preventing arrival at the login prompt.
A possible simple solution is to try to break the loop which isn’t likely critical anyway by hitting CTL-C.
Otherwise,
Have you tried booting to an emergency/recovery option in your GRUB menu?
Of course,
once you can get to either a login prompt or an emergency mode boot,
You should execute those recommended commands to gather information about your problem, if you need help understanding the output, you can post that here or to a pastebin, and if you need help how to do that you can ask here as well.
I’ve pressed CTL+C but nothing happend. in my GRUB menu I only have 2 options (boot normally and advance options). In advance I have 4 but all say the same (openSUSE 13.1 with Linux 3.11)
BTW, I (maybe implicitly) asked you about the file system on /srv.
It is clear that /srv is a separate file system. You seem not to know why. What is your relation to the system. Are you the system manager/administrator?. Did you install it and trim it to do it’s tasks? A separate /srv is not a default by any means, thus there must have been some idea behind it.
Also, the system manager must have some knowledge where the file systems are located. So for the file system to be used as /srv, what partition (or other container) is it on? As I suggested that container, or the underlying disk should be tested for failures.
The person who installed this server (OS and hardware) doesn’t work here anymore so I’m in charge now. I don’t have any problem to reinstall the openSUSe (which is my last resort). JIN I’m installing a new openSUSe in a new disk and I’ll try to boot (hope that the RAID5 won’t be affected).
UPDATED: I couldn’t recover the svr so I wanted to use a windows or other linux distro (i.e mint). But in Windows detected the RAID5 as a RAW format and I couldn’t access, is it normal? if I put another distro I will have the same problem?
Windows doesn’t understand anything about Linux filesystems - it may show them as RAW unformatted partitions. If you take any action on these drives on the Windows side, you risk catastrophic data loss.
My advice: get someone who is proficient with Linux to deal with this. Hire one if necessary if there is important data there.
Since we do not know which technique was used to RAID these drives (LVM? MDRAID? Hardware RAID?) without further examination of the drives it’s hard to throw any exact solutions for you.
However if you get another openSUSE installation up, we can give you commands that you can use to show us how they were built and how to mount them safely (if there hasn’t been any data loss or hardware issues that caused this problem in the first place)
I also want to stress that on my questions where the /srv file system is stored on, you gave no answer. Thus I assume that you do not know. Apparently you guess that it is on some RAID of unknown type (assumption based on the fact that you suddenly start talking about such a RAID without having it mentioned earlier). Again, you seem not to know much of what is there. That may not be your fault, but the task of managing this system is probably not really transferred to you in a proper way. You know best who to blame for that.
Like Miuku I doubt very much we, so far away from the system, can not be of very much help in this situation. So look for somebody with Linux knowledge that can come to your system for local hands on help.
And no, Windows is not an option here. Somebody choose for Linux for this system. And you have to live with that.
