Topic: SME Server 7.4 will not start

[ciqui]

The error given is:

md: md1 stopped.
md: bind<sda1>
raid1: raid set md1 active with 1 out of 2 mirrors
mdadm: /dev/md1 has been started with 1 drive (out of 2).
md: md2 stopped.
md: bind<sda2>
raid1: raid set md2 active with 1 out of 2 mirrors
mdadm: /dev/md2 has been started with 1 drive (out of 2).
Making device-mapper control node
Scanning logical volumes
    Reading all physical volumes. This may take a while...
    Found volume group "main" using metadata type lvm2
Activating logical volumes
    2 logical volumes(s) in volume group "main" now active
Creating root device
Mounting root filesystem
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Switching to new root
exec of init (/sbin/init) failed!!!: 20
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!

   
thank you very much.

[versa]

You might want to check your hardware compatibility
What spec hardware are you using ?

http://wiki.contribs.org/SME_Server:Documentation:FAQ#Hardware_Compatibility_List

[ciqui]

He was working 2 years, but due to numerous failures of energy does not start over.

Follow these steps: Recovering SME Server with lvm drives
http://wiki.contribs.org/Recovering_SME_Server_with_lvm_drives

but it does not work.

[MSmith]

"it does not work" will not get you much help without specific information on exactly what steps you took and the exact result.  If I understood your post correctly, repeated power cuts have resulted in a lot of filesystem corruption.  Sounds like you should check your hard drives with something such as the Ultimate Boot CD or the drive makers' utility CD, then reinstall a clean SME 7.4 and restore from your backup.

And buy a UPS if that's at all possible.

[CharlieBrady]

exec of init (/sbin/init) failed!!!: 20
umount /initrd/dev failed: 2

This indicates that you have file system corruption.

raid1: raid set md1 active with 1 out of 2 mirrors

This indicates that you have only one drive, or have two and one has failed. You should always have two drives, and should repair or replace immediately one if it fails.

[ciqui]

I have no armed raid.
It is a standard installation of SME Server in 1 HD SATA,
which creates 2 partitions (sda1 and sda2) but LVM,
/dev/sda1 FD type Linux raid autodetect
/dev/sda2 FD type Linux raid autodetect
The problem is that I can mount the sme rescue "main" in /mnt/sysimage
order to check or repair the files
but due to my poor knowledge in linux
I can not continue, which is performed as follows:

/dev/main/root  --->   /mnt/sysimage
/tmp/md1  --->   /mnt/sysimage/boot
/dev/root.old  ---->  /mnt/sysimage/dev
/dev/root.old  ---->  /

LV -> /dev/main/root
LV -> /dev/main/swap
VG -> "main"

e2fsck/dev/sda1 works
e2fsck/dev/sda2 "superblock" error or missing
   
That most do not.
Apparently executed
with the server running
e2fsck / (with all the mounted drives) and no more boot.

Best regars.
Ciqui