Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I had a hardware issue which caused my Ubuntu Server to fail. After the problem has been resolved I still cannot boot into my Ubuntu installation, but fall into initramfs instead. To me it seems that there is something wrong with the boot manager. This is why I wanted to reinstall Grub, but from the LiveCD I cannot mount my system partitions.

First I tried with BootRepair, but it couldn't fix it. I guess it is not able to fix Raid partitions. Anyway here is its output:


And some further info:

# blkid
/dev/loop0: TYPE="squashfs"
/dev/sda: TYPE="jmicron_raid_member"
/dev/sdb: TYPE="jmicron_raid_member"
/dev/mapper/jmicron_JRAID1p1: UUID="f243e212-5167-4761-87b2-829106812fbc" TYPE="ext2"
/dev/sdc: LABEL="MYLINUXLIVE" UUID="F06C-C565" TYPE="vfat"

dmraid -r
/dev/sdb: jmicron, "jmicron_JRAID1", mirror, ok, 390660096 sectors, data@ 0
/dev/sda: jmicron, "jmicron_JRAID1", mirror, ok, 390660096 sectors, data@ 0

# fdisk -l /dev/mapper/jmicron_JRAID1
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0xffe2 of partition table 5 will be corrected by w(rite)

Disk /dev/mapper/jmicron_JRAID1: 200.0 GB, 200017969152 bytes
255 heads, 63 sectors/track, 24317 cylinders, total 390660096 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008fa0e

                      Device Boot      Start         End      Blocks   Id  System
/dev/mapper/jmicron_JRAID1p1   *        2048   382341119   191169536   83  Linux
/dev/mapper/jmicron_JRAID1p2       382343166   390660095     4158465    5  Extended
/dev/mapper/jmicron_JRAID1p5   ?  4256503776  8130664385  1937080305   e2  Unknown

I can mount only the first partition /dev/mapper/jmicron_JRAID1p1 but it has some rather spare contents:

root@ubuntu:/# ls -la
total 25719
drwxr-xr-x 4 root root     1024 Aug  3 20:04 .
drwxr-xr-x 1 root root      240 Aug  3 17:58 ..
-rw-r--r-- 1 root root   919604 Aug 14  2013 abi-3.8.0-29-generic
-rw-r--r-- 1 root root   154969 Aug 14  2013 config-3.8.0-29-generic
drwxr-xr-x 3 root root     5120 Nov  1  2013 grub
-rw-r--r-- 1 root root 16516696 Nov  1  2013 initrd.img-3.8.0-29-generic
drwxr-xr-x 2 root root    12288 Nov  1  2013 lost+found
-rw------- 1 root root  3187899 Aug 14  2013 System.map-3.8.0-29-generic
-rw------- 1 root root  5426416 Aug 14  2013 vmlinuz-3.8.0-29-generic

There is only grub there and the images, so I cannot follow to otherwise great advices from this askubuntu answer because I am missing the /dev, /proc, /sys and the /bin/bash in order to chroot to it.

Can anybody give me a hand in fixing this?

What would be the safest way (for the data) of fixing this? I could maybe turn off the Raid and use only the first HDD to fix this mess. Then wipe the second one and recreate the Raid array.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.