Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 34

Thread: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

  1. #21
    Join Date
    Dec 2012
    Beans
    18

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    Quote Originally Posted by darkod View Post
    Looks good. Did you try if it's working after rebooting?
    I tried to boot into Ubuntu. My monitors told me "there's no connection" and went black. I waited about a minute and nothing happened so I rebooted.

    There are two options for Windows 7 in GRUB. I tried one of them out and it worked great! I'm in Windows right now.

    I assume that Wubi problem was what was causing that black screen, so I'm trying to run a chkdsk on the drive that Ubuntu is installed on. Unfortunately, the drives aren't mapped or something because they don't have a path.

    Here's a picture of what I'm seeing (they just don't show up despite being recognized as partitions in Disk Management):
    http://i.imgur.com/oyIME.png

    So I'm not really sure how to run a chkdsk on a drive that I can't reference...

    I'm trying to google it now.

    Edit 1: I tried to run chkdsk on the drive letters despite them not appearing and it didn't work.

    Edit 2: Ugh. This is terrible... I downloaded Ext2Read because I saw a person was able to get windows to recognize ext drives and assign them letters. I ran the program and used it to permanently set drive letters to them, however, Windows still doesn't know how to read Ext4 format and so it detects the drives as RAW format. When I try to chkdsk it I get this message:
    "
    The type of the file system is RAW.
    CHKDSK is not available for RAW drives.
    "

    I have the sector range from the partition, why can't I just run a chkdsk on those sectors? :'(

    Edit 3: So I read that fsck.ext4 is the linux version of chkdsk for ext4 partitions. I ran it and now when I select Ubuntu from GRUB I get to the purple and white Ubuntu loading screen but it just stays there loading. I've waited about four minutes now, I'll wait a few more minutes before I do a manual reboot... Any ideas on what to do after that?

    Edit 4: Got back into the splash screen and tried to get into a tty via cntrl+alt+f1 so I could run sudo dpkg-reconfigure lightdm. Upon pressing cntrl+alt+f1 I went to a black screen with a tiny white underscore that blinked rapidly. Pressing keys did nothing.

    Edit 5: I ran the Recovery Mode after reading this (I have a 7000 series). Upon selecting any option a fsck.ext4 run appears beneath the menu with a blinking white underscore which I can type into. Typing commands does nothing, but upon pressing cntrl+c I'm brought to the following screen:
    "
    Begin: Loading essential drivers ... done.
    Begin: Running /scripts/init-premount ... done.
    Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
    Begin: Running /scripts/local-premount ... done.
    Begin: Running /scripts/local-bottom ... done.
    done.
    Begin: Running /scripts/init-bottom ... done.

    Warning: Fake initct1 called, doing nothing.
    The disk drive for / is not ready yet or not present.
    keys: Continue to wait, or Press S to skip mounting or M for manual recovery
    "
    No key press does anything except for esc, which switches to a white and purple loading screen that says the same warning message. Pressing esc again switches back to the white and black command prompt-looking screen.

    Edit 6: I just ran the system information option in the recovery mode and under the property "=== Software RAID state ===" it says:
    No software RAID detected (mdstat)
    Perhaps that's causing this?
    Last edited by sdsdsd2; December 3rd, 2012 at 06:48 PM.

  2. #22
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,558
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    chkdsk is for ntfs partitions. Forget about reading linux partitions from windows, it can only get you into problems. I wouldn't try it.

    If you want to run a check of the ubuntu partition, all you need to do from live session is:
    Code:
    sudo fsck /dev/mapper/isw_blahblah_thefuture7
    That will run the fsck on partition #7.

    The black screen or stucking at the purple screen might be a video issue. I didn't understand whether you did run the commands to install fglrx or not? They need to be run from ubuntu recovery mode, not from windows command prompt.
    In the grub boot menu, select the ubuntu recovery mode. In the menu that shows up, select Network to activate networking (internet).
    After that it will return you to the same menu, now select Drop to root shell.

    That will open command prompt as root. Start executing the commands in that link:
    Code:
    apt-get install fglrx
    aticonfig --initial
    reboot
    You don't need the sudo in front since in the root shell you are already as root.

    See if something like that can help. Usually the nvidia cards were the ones giving problems, not ATI but it seems lately there was a change in the drivers included in ubuntu so you have to do some additional steps for ATI cards too.

    You can also try downloading the driver from the AMD website and putting it onto a usb stick. Then you can try installing it in recovery mode. But try the above procedure first.

    PS. About your Edit6, the message about software raid. The message is correct, you don't have software raid. Linux software raid is different from the bios fakeraid, even though fakeraid is also software based in a way. But it's not linux software raid. So, the message saying you don't have one is correct and that's not a problem.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  3. #23
    Join Date
    Dec 2012
    Beans
    18

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    Quote Originally Posted by darkod View Post
    chkdsk is for ntfs partitions. Forget about reading linux partitions from windows, it can only get you into problems. I wouldn't try it.

    If you want to run a check of the ubuntu partition, all you need to do from live session is:
    Code:
    sudo fsck /dev/mapper/isw_blahblah_thefuture7
    That will run the fsck on partition #7.

    The black screen or stucking at the purple screen might be a video issue. I didn't understand whether you did run the commands to install fglrx or not? They need to be run from ubuntu recovery mode, not from windows command prompt.
    In the grub boot menu, select the ubuntu recovery mode. In the menu that shows up, select Network to activate networking (internet).
    After that it will return you to the same menu, now select Drop to root shell.

    That will open command prompt as root. Start executing the commands in that link:
    Code:
    apt-get install fglrx
    aticonfig --initial
    reboot
    You don't need the sudo in front since in the root shell you are already as root.

    See if something like that can help. Usually the nvidia cards were the ones giving problems, not ATI but it seems lately there was a change in the drivers included in ubuntu so you have to do some additional steps for ATI cards too.

    You can also try downloading the driver from the AMD website and putting it onto a usb stick. Then you can try installing it in recovery mode. But try the above procedure first.

    PS. About your Edit6, the message about software raid. The message is correct, you don't have software raid. Linux software raid is different from the bios fakeraid, even though fakeraid is also software based in a way. But it's not linux software raid. So, the message saying you don't have one is correct and that's not a problem.
    That's the thing though. I can't activate network in recovery mode because it does the problem I described in Edit 5. I can drop to root shell, though. The commands don't work without internet, though...

    Edit 1: I get stuck on the splash screen but the orbs below "ubuntu" still turn red/white. It's not frozen.

    Edit 2: HEY!!!! I just found something cool!

    So I did a google search to see if there was a way to set up a network connection via the root shell, and there's a command dhclient eth0 which can do it. It didn't work out in the recovery mode root shell, but I figured I'd try it out in that chroot shell we were having trouble with earlier, and it worked! So right now I'm installing GRUB with your installation guide.

    Edit 3: So I followed what you told me to do and there's a problem, a device which isn't supposed to be being used (at least I don't think it is) IS being used and I'm unable to unmount it. I'll post the full terminal so you can see exactly what happened, but the problem is at the end of it. Is it safe to reboot?

    Here it is:

    ubuntu@ubuntu:~$ sudo su
    root@ubuntu:/home/ubuntu# mount /dev/mapper/isw_djejjcdice_thefuture7 /mnt
    root@ubuntu:/home/ubuntu# mount --bind /proc /mnt/proc
    root@ubuntu:/home/ubuntu# mount --bind /dev /mnt/dev
    root@ubuntu:/home/ubuntu# mount --bind /sys /mnt/sys
    root@ubuntu:/home/ubuntu# chroot /mnt
    root@ubuntu:/# dhclient eth0
    root@ubuntu:/# apt-get remove --purge grub-pc grub-common
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be REMOVED:
    grub-common* grub-gfxpayload-lists* grub-pc* grub-pc-bin* grub2-common*
    0 upgraded, 0 newly installed, 5 to remove and 150 not upgraded.
    After this operation, 9,283 kB disk space will be freed.
    Do you want to continue [Y/n]? y
    Can not write log, openpty() failed (/dev/pts not mounted?)
    (Reading database ... 155942 files and directories currently installed.)
    Removing grub-gfxpayload-lists ...
    Removing grub-pc ...
    Purging configuration files for grub-pc ...
    Removing grub2-common ...
    Removing grub-pc-bin ...
    Removing grub-common ...
    invoke-rc.d: policy-rc.d denied execution of stop.
    Purging configuration files for grub-common ...
    Processing triggers for man-db ...
    Processing triggers for install-info ...
    Processing triggers for ureadahead ...
    root@ubuntu:/# apt-get install grub-pc
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following extra packages will be installed:
    grub-common grub-gfxpayload-lists grub-pc-bin grub2-common
    Suggested packages:
    multiboot-doc grub-emu xorriso desktop-base
    The following NEW packages will be installed:
    grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common
    0 upgraded, 5 newly installed, 0 to remove and 150 not upgraded.
    Need to get 0 B/2,368 kB of archives.
    After this operation, 9,283 kB of additional disk space will be used.
    Do you want to continue [Y/n]? y
    Preconfiguring packages ...
    Can not write log, openpty() failed (/dev/pts not mounted?)
    Selecting previously unselected package grub-common.
    (Reading database ... 155591 files and directories currently installed.)
    Unpacking grub-common (from .../grub-common_2.00-7ubuntu11_amd64.deb) ...
    Selecting previously unselected package grub2-common.
    Unpacking grub2-common (from .../grub2-common_2.00-7ubuntu11_amd64.deb) ...
    Selecting previously unselected package grub-pc-bin.
    Unpacking grub-pc-bin (from .../grub-pc-bin_2.00-7ubuntu11_amd64.deb) ...
    Selecting previously unselected package grub-pc.
    Unpacking grub-pc (from .../grub-pc_2.00-7ubuntu11_amd64.deb) ...
    Selecting previously unselected package grub-gfxpayload-lists.
    Unpacking grub-gfxpayload-lists (from .../grub-gfxpayload-lists_0.6_amd64.deb) ...
    Processing triggers for man-db ...
    Processing triggers for ureadahead ...
    Processing triggers for install-info ...
    Can not write log, openpty() failed (/dev/pts not mounted?)
    Setting up grub-common (2.00-7ubuntu11) ...
    invoke-rc.d: policy-rc.d denied execution of start.
    Processing triggers for ureadahead ...
    Setting up grub2-common (2.00-7ubuntu11) ...
    Setting up grub-pc-bin (2.00-7ubuntu11) ...
    Setting up grub-gfxpayload-lists (0.6) ...
    Setting up grub-pc (2.00-7ubuntu11) ...

    Creating config file /etc/default/grub with new version
    Installation finished. No error reported.
    Generating grub.cfg ...
    Found linux image: /boot/vmlinuz-3.5.0-17-generic
    Found initrd image: /boot/initrd.img-3.5.0-17-generic
    No volume groups found
    Found Windows 7 (loader) on /dev/mapper/isw_djejjcdice_thefuture1
    Found Windows 7 (loader) on /dev/mapper/isw_djejjcdice_thefuture2
    done
    root@ubuntu:/# grub-mkconfig
    Generating grub.cfg ...
    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #

    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"

    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi

    export menuentry_id_option

    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi

    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    }

    function recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
    }

    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    }

    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    else
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    fi
    font="/usr/share/grub/unicode.pf2"
    fi

    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_output gfxterm
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###

    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    if background_color 44,0,30; then
    clear
    fi
    ### END /etc/grub.d/05_debian_theme ###

    ### BEGIN /etc/grub.d/10_linux ###
    function gfxmode {
    set gfxpayload="${1}"
    if [ "${1}" = "keep" ]; then
    set vt_handoff=vt.handoff=7
    else
    set vt_handoff=
    fi
    }
    if [ "${recordfail}" != 1 ]; then
    if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
    if [ ${match} = 0 ]; then
    set linux_gfx_mode=keep
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=keep
    fi
    else
    set linux_gfx_mode=text
    fi
    export linux_gfx_mode
    if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
    Found linux image: /boot/vmlinuz-3.5.0-17-generic
    Found initrd image: /boot/initrd.img-3.5.0-17-generic
    menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-20a44ca8-89ba-40fc-a51e-33423e1784a7' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    else
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    fi
    linux /boot/vmlinuz-3.5.0-17-generic root=UUID=20a44ca8-89ba-40fc-a51e-33423e1784a7 ro quiet splash $vt_handoff
    initrd /boot/initrd.img-3.5.0-17-generic
    }
    submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-20a44ca8-89ba-40fc-a51e-33423e1784a7' {
    menuentry 'Ubuntu, with Linux 3.5.0-17-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-17-generic-advanced-20a44ca8-89ba-40fc-a51e-33423e1784a7' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    else
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    fi
    echo 'Loading Linux 3.5.0-17-generic ...'
    linux /boot/vmlinuz-3.5.0-17-generic root=UUID=20a44ca8-89ba-40fc-a51e-33423e1784a7 ro quiet splash $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-17-generic
    }
    menuentry 'Ubuntu, with Linux 3.5.0-17-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-17-generic-recovery-20a44ca8-89ba-40fc-a51e-33423e1784a7' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    else
    search --no-floppy --fs-uuid --set=root 20a44ca8-89ba-40fc-a51e-33423e1784a7
    fi
    echo 'Loading Linux 3.5.0-17-generic ...'
    linux /boot/vmlinuz-3.5.0-17-generic root=UUID=20a44ca8-89ba-40fc-a51e-33423e1784a7 ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-17-generic
    }
    }

    ### END /etc/grub.d/10_linux ###

    ### BEGIN /etc/grub.d/20_linux_xen ###

    ### END /etc/grub.d/20_linux_xen ###

    ### BEGIN /etc/grub.d/30_os-prober ###
    No volume groups found
    Found Windows 7 (loader) on /dev/mapper/isw_djejjcdice_thefuture1
    menuentry 'Windows 7 (loader) (on /dev/mapper/isw_djejjcdice_thefuture1)' --class windows --class os $menuentry_id_option 'osprober-chain-38CC659FCC6557E0' {
    insmod part_msdos
    insmod ntfs
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root 38CC659FCC6557E0
    else
    search --no-floppy --fs-uuid --set=root 38CC659FCC6557E0
    fi
    chainloader +1
    }
    Found Windows 7 (loader) on /dev/mapper/isw_djejjcdice_thefuture2
    menuentry 'Windows 7 (loader) (on /dev/mapper/isw_djejjcdice_thefuture2)' --class windows --class os $menuentry_id_option 'osprober-chain-3CA44133A440F0C6' {
    insmod part_msdos
    insmod ntfs
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root 3CA44133A440F0C6
    else
    search --no-floppy --fs-uuid --set=root 3CA44133A440F0C6
    fi
    chainloader +1
    }
    ### END /etc/grub.d/30_os-prober ###

    ### BEGIN /etc/grub.d/30_uefi-firmware ###
    ### END /etc/grub.d/30_uefi-firmware ###

    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###

    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    done
    root@ubuntu:/# update-grub
    Generating grub.cfg ...
    Found linux image: /boot/vmlinuz-3.5.0-17-generic
    Found initrd image: /boot/initrd.img-3.5.0-17-generic
    No volume groups found
    Found Windows 7 (loader) on /dev/mapper/isw_djejjcdice_thefuture1
    Found Windows 7 (loader) on /dev/mapper/isw_djejjcdice_thefuture2
    done
    root@ubuntu:/# grub-install /dev/mapper/isw_djejjcdice_thefuture
    Installation finished. No error reported.
    root@ubuntu:/# exit
    exit
    root@ubuntu:/home/ubuntu# sudo umount /mnt/sys
    root@ubuntu:/home/ubuntu# sudo umount /mnt/dev
    umount: /mnt/dev: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    root@ubuntu:/home/ubuntu# sudo umount /mnt/proc
    root@ubuntu:/home/ubuntu# sudo umount /mnt/dev
    umount: /mnt/dev: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    root@ubuntu:/home/ubuntu# sudo umount /mnt/dev
    umount: /mnt/dev: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))

    Edit 4: So I just found out about fuser. Here's the terminal log:

    root@ubuntu:/home/ubuntu# fuser -mu /mnt/dev
    /mnt/dev: 1(root) 3565(root) 3576(root) 3602(messagebus) 3685(root) 3932(avahi) 3937(avahi) 3945(root) 4264(root) 4304(root) 4388(root) 4401(root) 4407(root) 4418(root) 4419(root) 4421(root) 4440(root) 4447(daemon) 4451(root) 4519(root) 4714(root) 4844(ubuntu) 4845(ubuntu) 4846(ubuntu) 4847(ubuntu) 4848(ubuntu) 4852(whoopsie) 5182(root) 5332(root) 5497(ubuntu) 5716(root) 5922(root) 5923(root) 5938(ubuntu) 5940(rtkit) 5958(colord) 5977(ubuntu) 5984(nobody) 7832(root) 7845m(root) 7858(root) 7871(root) 7893(ubuntu) 7928(ubuntu) 7931(ubuntu) 7932(ubuntu) 7934(ubuntu) 7938(ubuntu) 7941(ubuntu) 7952(ubuntu) 7961(ubuntu) 7973(ubuntu) 7979(ubuntu) 7985(ubuntu) 7989(ubuntu) 7997(ubuntu) 8007(ubuntu) 8008(ubuntu) 8009(ubuntu) 8012(ubuntu) 8014(ubuntu) 8022(ubuntu) 8028(root) 8035(ubuntu) 8039(ubuntu) 8067(ubuntu) 8073(ubuntu) 8077(ubuntu) 8086(ubuntu) 8090(ubuntu) 8091(ubuntu) 8103(ubuntu) 8105(ubuntu) 8114(ubuntu) 8116(ubuntu) 8118(ubuntu) 8120(ubuntu) 8124(ubuntu) 8126(ubuntu) 8154(ubuntu) 8159(ubuntu) 8171(ubuntu) 8187(ubuntu) 8189(ubuntu) 8191(ubuntu) 8193(ubuntu) 8195(ubuntu) 8197(ubuntu) 8199(ubuntu) 8234(ubuntu) 8244(ubuntu) 8246(ubuntu) 8291(ubuntu) 8293(ubuntu) 8315(ubuntu) 8324(ubuntu) 8329(ubuntu) 8380(ubuntu) 8386(ubuntu) 8392(ubuntu) 8426(ubuntu) 8475(root) 9059(ubuntu) 9063(ubuntu) 9140(ubuntu) 13713(root) 13762(root) 14681(ubuntu) 14705(ubuntu)
    Last edited by sdsdsd2; December 3rd, 2012 at 07:24 PM.

  4. #24
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,558
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    That's cool, but the boot-repair process already reinstalled grub2 and now you can see the boot menu and boot win7. My procedure will do the same thing as boot-repair, you already did that.

    I assume you will still have the problem when loading ubuntu.

    I wonder if it's somehow connected to the fakeraid array, and whether it's not loading the array correctly. So subsequently it doesn't have the system root partition to mount.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  5. #25
    Join Date
    Dec 2012
    Beans
    18

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    Quote Originally Posted by darkod View Post
    That's cool, but the boot-repair process already reinstalled grub2 and now you can see the boot menu and boot win7. My procedure will do the same thing as boot-repair, you already did that.

    I assume you will still have the problem when loading ubuntu.

    I wonder if it's somehow connected to the fakeraid array, and whether it's not loading the array correctly. So subsequently it doesn't have the system root partition to mount.
    Now that we can get internet in chroots, though, can't we install those packages we wanted to before but couldn't because of the problem in edit 5? Also, is it safe to unmount that drive?

  6. #26
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,558
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    I'm not sure which packages are you referring to. It failed when you tried reinstalling grub2, but now that is done. There were not other packages that failed installing.

    I wonder if all of this is consequence of using the live cd, although in theory it should work.

    Are you willing to give alternate 12.04 a try? That should work start to finish, without needing to additionally add grub2. Just remember the array name in case it gets confused in the last install step and asks you to confirm the full array device name which is /dev/mapper/isw_...._thefuture.

    If you decide to reinstall with the alternate 12.04 cd you can use manual partitioning and reuse the existing partitions. Simply select them and set the correct mount points. Format the root partition so that it deletes all old files.

    In fact, if installing 12.04 LTS works fine, I wouldn't even try to upgrade it to 12.10. 12.04 is LTS and is supported 5 years, while 12.10 is standard release and is supported only 18 months.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  7. #27
    Join Date
    Dec 2012
    Beans
    18

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    Quote Originally Posted by darkod View Post
    I'm not sure which packages are you referring to. It failed when you tried reinstalling grub2, but now that is done. There were not other packages that failed installing.

    I wonder if all of this is consequence of using the live cd, although in theory it should work.

    Are you willing to give alternate 12.04 a try? That should work start to finish, without needing to additionally add grub2. Just remember the array name in case it gets confused in the last install step and asks you to confirm the full array device name which is /dev/mapper/isw_...._thefuture.

    If you decide to reinstall with the alternate 12.04 cd you can use manual partitioning and reuse the existing partitions. Simply select them and set the correct mount points. Format the root partition so that it deletes all old files.

    In fact, if installing 12.04 LTS works fine, I wouldn't even try to upgrade it to 12.10. 12.04 is LTS and is supported 5 years, while 12.10 is standard release and is supported only 18 months.

    The packages I'm referring to are the missing files from the ubuntu installation which might've been causing the hang on the splash screen. Maybe we could install the graphics drivers or whatever?

    I can try 12.04, sure. But first I need to know if it's safe to unmount /mnt/dev, even though it's in use by ~30 different files/programs, because I don't want to mess anything up.

  8. #28
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,558
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    Ah, OK. You mean installing the fglrx driver. Yes, you can try that.

    Unmounting /mnt/dev should be fine, we only mounted it to use the chroot procedure. Once you are done inside the chroot and exit it, unmounting /mnt/dev should be fine.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  9. #29
    Join Date
    Dec 2012
    Beans
    18

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    Quote Originally Posted by darkod View Post
    Ah, OK. You mean installing the fglrx driver. Yes, you can try that.

    Unmounting /mnt/dev should be fine, we only mounted it to use the chroot procedure. Once you are done inside the chroot and exit it, unmounting /mnt/dev should be fine.
    I couldn't get an internet connection established in the chroot.

    I installed 12.04.1 alternate amd 64 bit and it's failed on the "Select and install software" step. I didn't choose the option to install a GRUB. Upon rebooting I got to a screen which had this:

    error: unknown filesystem.
    grub rescue>_


    I relaunched the 12.04.1 installer and ran the rescue mode. When it got to the menu that said "Enter rescue mode" and wanted me to choose what would be the "device to use as root file system" I had 3 options:
    -/dev/sdd1
    -Assemble RAID array
    -Do not use a root file system

    I selected assemble raid array and it wanted me to select which "partitions to assemble" which had 2 options:
    -Automatic
    -/dev/sdd1
    with a "continue" button in the bottom right.
    I tried selecting automatic and hit continue but it brought me back to the "choose a root file system" menu. I went back in and tried /dev/sdd1 but the same thing happened. Selecting both at the same time had the same outcome. I then chose /dev/sdd1 to be the root file system and it said "Mount failed An error occurred while mounting the device you entered for your root file system (/dev/sdd1) on /target. Please check the syslog for more information." I then chose the only remaining option...

    The next menu showed three options:
    1. open a shell
    2. load another root file system
    3. quit

    I opened the shell but it's pretty much the same thing as when we had 12.10 installed...
    Last edited by sdsdsd2; December 3rd, 2012 at 10:25 PM.

  10. #30
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,558
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Trouble installing 12.10 64-bit on a RAID 0 configuration P8Z77-V PRO

    /dev/sdd1 is your usb stick I believe. You can't use it as root partition.

    If the 12.04 install failed, maybe the ISO is corrupted or the cd/usb.

    I'm running out of ideas, you can rarely find so many problems when installing. If you have a good ISO and a good cd/usb, installing the alternate 12.04 on your fakeraid should go just fine.
    Stopping at the install software step means something is bothering it. It's not the same like not being able to install grub at the end, it doesn't even continue to that step.

    I don't know what to recommend any more.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

Page 3 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •