[SOLVED] maintenance mode

whitethorn · 2010-09-10 09:18:27

Hi,

Everytime I boot arch, I get the maintenance mode question, control D to continue or root password for console. This started happening after I deleted my /var/cache/pacman pretty much my whole local package database. I got the database back and everything is running properly again, but I keep getting the maintenance mode prompt. How do I get rid of this, I've done some extensive googling but so far I haven't been able to find anything which gets rid of the problem.

Last edited by whitethorn (2010-11-10 16:40:09)

karol · 2010-09-10 12:12:05

Does the system tell you why are you're being dropped into the maintenance mode?

kgas · 2010-09-10 12:22:40

may be related to your file system problem / clock settings.

whitethorn · 2010-09-10 23:41:06

karol wrote:

Does the system tell you why are you're being dropped into the maintenance mode?

Nope, the maintenance mode prompt comes right after it loads the keymap profile from /etc/rc.conf

may be related to your file system problem / clock settings.

Well I got everything back and installed. My clock I get sychronized with every restart using ntpdate.

Last edited by whitethorn (2010-09-10 23:48:10)

whitethorn · 2010-09-14 20:51:43

bump

Cape · 2010-09-15 12:04:04

You should tell us more about your system. For example, what kind of hard disk are you using?

whitethorn · 2010-10-03 10:59:58

I have 2 Harddrives, both are 1 Tb samsung F1 spinpoints. I have one for data and the other one is for my OSs. Is there some file or some sort of log which will tell me what the problem is?

whitethorn · 2010-10-26 20:38:47

bump

I gonna need this to work soon. I want to use WOL and I don't really want to install some other linux just to start my pc :S

Hmm System information

Processor : Q9860
Motherboard : Asus P5Q Pro
HDs : 2 X 1 TB Samsung F1 spinpoints
Graphic Card : GTX 275

WM : Openbox

As said above, this problem started after having tried using a Ramdisk. I believe everything in /var got toasted and I had to reinstall all my programs with pacman -Sf which then kinda screwed everything up. Afterwards I looked through /etc/ and started .pacorig with the newer versions and editing the differences ... Since then I've always had the maintenance mode prompt.

ChoK · 2010-10-26 23:46:05

Does it say something about the root partition being corrupted? or a partition that can't be mounted?
Can you post our /etc/fstab and also fsck your partitions (via a live cd for the root partition)

whitethorn · 2010-10-27 01:54:44

Here's my fstab

$ cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda6 /home ext4 defaults 0 1
/dev/sda7 / ext3 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda4 /media/Stuff ext4 defaults,users 0 2
tmpfs /tmp tmpfs defaults 0 0

I'll fsck /root in the morning, but I don't get any messages about a corrupt partition and fsck have run through normally (after a certain amount of mounts ..)

Thor@Flanders · 2010-10-29 10:50:24

Hi,

Possible problem : the disks are "messy" and require cleaning...

If so, here's a possible thing to do:

There should be a mentioning if fsck failing, note the drive, eg "/dev/sda3"
enter the root password
enter init 1
detatch the affected partition

umount /dev/sda3 - for example

enter

fsck -TYPE

where TYPE is ext3 - check what dile system you have
should be something like

fsck -ext3

confirm repairs
at the end enter "reboot" to restart the system

notes:
- I gave an example with "/dev/sda3" - figure out what it says on your box
- If possible, try to save your data first...

Wellness

Thor

ChoK · 2010-10-29 13:17:37

i'm also pretty sure it should be
none /tmp tmpfs defaults 0 0
instead of
tmpfs /tmp tmpfs defaults 0 0

edit and:
/dev/sda2 none swap sw 0 0
instead of
/dev/sda2 swap swap defaults 0 0

Last edited by ChoK (2010-10-29 13:23:08)

whitethorn · 2010-11-09 15:50:52

Hi, sorry it's taken me this long to write back. I've been really busy at work and uni. I fschecked the harddrives no problems there.

As for the /dev/sda2 as swap I was just following the arch wiki fstab

https://wiki.archlinux.org/index.php/Fstab

In the one example it's written the way I have it set in my fstab. Now I'm not sure which one is right. Usually I tend to follow the wiki.

Is there a place where the bootup order is listed I'm slowly running out of time (gotta get this working before december. I'll be on vacation for a month and WoL won't work properly if I can't get it to bootup completely.) I'd rather just go through the bootup order and work my way through might be I'll find the problem.

ChoK · 2010-11-10 00:35:10

the /etc/inittab file control the bootorder, if the system drops you to a recovery shell the file you want is /etc/rc.sysinit (the first runlevel)

Maybe the swap configuration in the wiki is also correct, but can you try with my suggestions (switch swap and tmpfs for none and don't forget the sw instead of swap). If it works we have to correct the wiki.

whitethorn · 2010-11-10 12:56:13

ChoK wrote:

the /etc/inittab file control the bootorder, if the system drops you to a recovery shell the file you want is /etc/rc.sysinit (the first runlevel)
Maybe the swap configuration in the wiki is also correct, but can you try with my suggestions (switch swap and tmpfs for none and don't forget the sw instead of swap). If it works we have to correct the wiki.

Alright changed it around, rebooted. Everything looks fine. Swap gets mounted and /tmp looks the same. Alright gonna have a look at /etc/inittab and /etc/rc.sysinit.

whitethorn · 2010-11-10 16:39:50

Alright I finally got it figured out. I was playing around with my /boot/grub/menu.lst and I just noticed that on the kernel line there was the option "single" in there. I then remembered reading about that yesterday as being the ideal way of booting into maintenance mode. Removed it rebooted and voila no maintenance mode.

thisisabdus · 2018-05-08 17:15:30

Ahhh. This problem was a real pain for me. I'm a newbie to arch and had no idea how to tackle this problem.
After some googling, I found a way to fix it.
Resin for the problem was, a corrupted file system.

STEPS I FOLLOWED:

1. identity in which file system the problem is occurring (For me, it was /dev/sda1)

2. Run fsck <your file system> (fsck /dev/sda1)

3. Fix all those problems rendering in your display (you have to press oonl Y)

And your are good to go for a peaceful sleep.

Slithery · 2018-05-08 17:21:09

Welcome to the forums thisisabdus

Please take the time to familiarise yourself with our forums Code of Conduct, especially the section regarding necro-bumping. Also your problem seems to be unrelated to the OP in any way. I'm going to close this old thread now.

Closing - For deletion.

Arch Linux

#1 2010-09-10 09:18:27

[SOLVED] maintenance mode

#2 2010-09-10 12:12:05

Re: [SOLVED] maintenance mode

#3 2010-09-10 12:22:40

Re: [SOLVED] maintenance mode

#4 2010-09-10 23:41:06

Re: [SOLVED] maintenance mode

#5 2010-09-14 20:51:43

Re: [SOLVED] maintenance mode

#6 2010-09-15 12:04:04

Re: [SOLVED] maintenance mode

#7 2010-10-03 10:59:58

Re: [SOLVED] maintenance mode

#8 2010-10-26 20:38:47

Re: [SOLVED] maintenance mode

#9 2010-10-26 23:46:05

Re: [SOLVED] maintenance mode

#10 2010-10-27 01:54:44

Re: [SOLVED] maintenance mode

#11 2010-10-29 10:50:24

Re: [SOLVED] maintenance mode

#12 2010-10-29 13:17:37

Re: [SOLVED] maintenance mode

#13 2010-11-09 15:50:52

Re: [SOLVED] maintenance mode

#14 2010-11-10 00:35:10

Re: [SOLVED] maintenance mode

#15 2010-11-10 12:56:13

Re: [SOLVED] maintenance mode

#16 2010-11-10 16:39:50

Re: [SOLVED] maintenance mode

#17 2018-05-08 17:15:30

Re: [SOLVED] maintenance mode

#18 2018-05-08 17:21:09

Re: [SOLVED] maintenance mode

Board footer