Mint 12 RAID 0 DMI Pool verification "system halt"

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read this

Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Thu Jan 05, 2012 4:23 pm

I'm having some difficulty installing Mint 12 Lisa x86 to my new configuration.

AMD Gigabyte motherboard (FakeRAID)
3x Seagate 500gb matched (RAID0)
1x Hitachi 80 GB (40gb /Boot & 40gb Swap Area)

I have an additional Hitachi 80GB drive for /Boot sector as i read that Grub doesn't like RAID configurations. At the beginning of the install i noticed that the partition size for my RAID array was only showing as 975GB however it shot be somewhere near 1.5TB. I still continued with the install and everything installed fine however as soon as i reboot the system halts at:

Verifying DMI Pool Data......

and does not go any further until I boot the live USB key that use

Has anyone got any ideas what the problems are. I'm a bit of a noob when it comes to Linux, but I'm sick of windows so I'll persevere :)

Please see below picture of my partition setup
Image
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Linux Mint is funded by ads and donations.
 

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Thu Jan 05, 2012 6:10 pm

Off course you know that RAID-0 means that if one disk dies you are loosing all of your data from that RAID ??
GRUB2 from Mint12 likes RAID, but only RAID-1 for boot partition.

Drop that FakeRAID and go to RAID with MDADM.
If your present motherboard dies, to recover your data you will have to find/buy/steal the same motherboard.
Once again RAID-0 is evil, and worth only for temp data without any value.

With 3 disk of 500GB you could do something wild like:
Create 3 partitions only for BOOT partition about 200MB and make from this RAID-1
Create additional 3 partitions for RAID-5 for your root partition /.
Create additional 3 partitions for RAID-1 for your SWAP partition.

You will then be safe if one disk fails.
RAIDs-1 wil have working mirrors and RAID-5 will go from checksums.
But you have to have some experience to do and maintain this later if disk fails.
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Thu Jan 05, 2012 6:48 pm

Thanks for your response jack

I like your idea of setting up multiple RAID partitions using MDADM, I have read vague snippets on this software RAID tool, however as a bit of a linux novice I thought I'd try and take the easy route first, which I think has already failed at the first hurdle.

Can you possibly give me some brief or basic instructions on how to set up these RAID partitions or point me in the right direction with simple easy to understand instructions on using MDADM?

I can partition the disks manually using GParted prior to booting the live USB. Its more the whole software RAID set up that concerns me and my lack of skills in that area.
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Fri Jan 06, 2012 7:55 pm

I don't know your detail CPU and motherboard spec and etc. so I assume that you have 4GB of RAM.

1. Run LiveCD LinuxMint12

2. Install mdadm through apt-get, aptitude, Software Manager, Synaptic etc.

3. Partitioning: [we have /dev/sda, /dev/sdb, /dev/sdc - all disks we're partitioning the same way]
Use GParted because you know that program. DON'T FORMAT YOUR PARTITIONS !!! CHOOSE ALWAYS UNFORMATTED !!! CHOOSE ALL AS A PRIMARY PARTITIONS !
Example: /dev/sda
Make partition table: GPT
/dev/sda1 -> 1MiB for bios_grub - let the GParted align this from start with 1MiB[default] - that's needed for GPT and MDADM, and for good alignment - enable bios_grub flag on
/dev/sda2 -> 200MiB for /boot - enable boot flag ON
/dev/sda3 -> we're choosing here to leave 4097MiB[RAM size + 1MiB] - If you have different size of RAM adjust this but add 1MiB to this value - that 1MiB is needed for GPT backup partition table on the end of the disk
/dev/sda4 -> choose 4096MiB or your RAM size - 1GB=1024MiB
Once again don't format partitions!, leave that 2x1MiB as a free disk size.
Repeat above identically for all 3 disks!

[added 02.02.2012]
/dev/sda1, /dev/sdb1, /dev/sdc1 -> we are leaving this for bios_grub - needed for GRUB2
/dev/sda2, /dev/sdb2, /dev/sdc2 -> /dev/md0 -> RAID1 -> /boot partition -> 200MiB[GParted is proposing in front to leave 1MiB - that's correct and do not change it]
/dev/sda3, /dev/sdb3, /dev/sdc3 -> /dev/md1 -> RAID5 -> / partition -> rest of the disk minus RAM size minus 1MiB [1GB of RAM = 1024MiB !!][for 2GB RAM you're leaving 2049MiB]
/dev/sda4, /dev/sdb4, /dev/sdc4 -> /dev/md2 -> RAID1 -> swap partition -> RAM size[for 2GB partition size is 2048MiB]

After that, you have 1MiB space on front and 1MiB on end of the disks. Front space for GPT, mdadm metadata and some MBR compatibility, end space for GPT backup partition table.
[/added 02.02.2012]

4. Open terminal
Code: Select all
sudo su


Create RAID1 for /boot
Code: Select all
mdadm --create /dev/md0 --level=1 --raid-devices=3 /dev/sd[abc]2


Create RAID5 for root partition /
Code: Select all
mdadm --create /dev/md1 --level=5 --raid-devices=3 --chunk=256 /dev/sd[abc]3


Create RAID1 for swap partition
Code: Select all
mdadm --create /dev/md2 --level=1 --raid-devices=3 /dev/sd[abc]4


Array's are creating - we can go forward.

5. Format RAID partitions - that's needed for Mint installer.
Code: Select all
sudo su
mke2fs -t ext4 /dev/md0
mke2fs -t ext4 -E stride=64,stripe-width=128 /dev/md1
mkswap /dev/md2


6. Start LinuxMint12 installation from desktop
Choose hand partitioning and point to - choose NOT to format /dev/md0 and /dev/md1:
/dev/md0 /boot ext4
/dev/md1 / ext4
/dev/md2 swap
Let the install go till the end, and on last question choose to NOT reboot yet !!
Beware - you will have an error about cannot installing grub-install - on this point choose OK, and after last installer question choose NOT to reboot.

[added 27.01.2012]
WARNING !!!
There is a bug in the Linux Mint 12 installer - when you receive an error that installer cannot install bootloader to the disks choose OK,
and on the next window called "Bootloader install failed" the OK button isn't active!
Do move forward you have to:
a) click first position "Choose a different device to install the bootloader on:"
b) open the list with disks and choose something, for example /dev/sda
OK button is now active!
c) click "Continue without a bootloader"
d) click OK
WARNING !!!
[/added 27.01.2012]

7. Adjust new installation:
Start Terminal:
Code: Select all
sudo su
mount --bind /dev /target/dev
mount --bind /dev/pts /target/dev/pts
mount --bind /proc /target/proc
mount --bind /sys /target/sys
mount --bind /tmp /target/tmp
chroot /target


Install MDADM on new installed OS:
Code: Select all
apt-get install mdadm
cd /etc/mdadm
nano mdadm.conf -> delete / from array names so they should look like /dev/md0 and /dev/md1 and /dev/md2


Run command below and on last question choose to allow RUN from degraded array.
Code: Select all
dpkg-reconfigure mdadm


Updating new settings
Code: Select all
update-initramfs -uv
update-grub
grub-install /dev/sda
grub-install /dev/sdb
grub-install /dev/sdc


Leaving chroot
Code: Select all
exit
umount /target/dev
umount /target/dev/pts
umount /target/proc
umount /target/sys
umount /target/tmp


8. Waiting for RAID to sync:
Code: Select all
watch -n1 cat /proc/mdstat


You can speed this up a little bit with:
Code: Select all
echo 200000 >/proc/sys/dev/raid/speed_limit_min

But this is effective only if the MDADM is reducing speed intentionally.
You can run this in any time.

9. After all REBOOT

10. Learn from uncle Google how to properly maintain RAID with MDADM - you should read all from http://manpages.ubuntu.com/manpages/one ... adm.8.html
Few basic rules:
1) You can take out one disk for test only when the RAID is fully synchronized ! Then you put it back and YOU MUST wait to synchronize. If you take out second disk when the RAID is not in sync your RAID5 die.
2) If your disk die for real, you have to first --fail that disk, then --remove with MDADM commands. Then you put in new disk and use --add command. If you for mistake remove wrong disk your RAID5 die.
3) RAID5 can only live with 1 disk failed. Replace failed one as soon as possible, because if in that time second disk will fail you loose all of your data!
4) Last and most important: RAID IS NOT A BACKUP FEATURE. It not protects you from fire, water etc. and MOSTLY user mistakes.
Last edited by jack_ on Wed Feb 01, 2012 7:52 pm, edited 9 times in total.
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sat Jan 07, 2012 7:46 am

WOW amazing response :) Many Thanks.

Will try this now and let you know how I get on
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sat Jan 07, 2012 1:28 pm

I have followed your guide down to the tee, however at install I am getting an install failure:

Executing 'grub-install /dev/sda' failed.

This is a fatal error

see Picture

I have tried many times following your guide, i have also tried setting the RAID up using Webmin and also Disk Utility, however all result in the same ending error at the point in the install where grub is installed.

When selecting the partitions i chose the boot loader to be installed at /dev/md0 is this correct?

Do you have any suggestions?
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Sat Jan 07, 2012 1:34 pm

Boot loader from installer always will fail, because we will do that later ourselfs - see point 7.
That's normal behavior. Choose OK. And on last question from installer choose to NOT reboot.
After that you are starting from point 7.
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sat Jan 07, 2012 1:38 pm

In your guide you advise:
apt-get install mdadm -> when it will ask you choose BOOT_DEGRADED=true !!!

After in installed mdadm i did not get this option, i have copied my terminal session below for you to see:


Code: Select all
mint / # apt-get install mdadm
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  postfix
Suggested packages:
  procmail postfix-mysql postfix-pgsql postfix-ldap postfix-pcre sasl2-bin
  dovecot-common resolvconf postfix-cdb
Recommended packages:
  default-mta mail-transport-agent
The following NEW packages will be installed:
  mdadm postfix
0 upgraded, 2 newly installed, 0 to remove and 215 not upgraded.
Need to get 1,532 kB of archives.
After this operation, 4,452 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com/ubuntu/ oneiric/main mdadm i386 3.1.4-1+8efb9d1ubuntu6 [309 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ oneiric/main postfix i386 2.8.5-2~build1 [1,223 kB]
Fetched 1,532 kB in 1s (987 kB/s)   
Preconfiguring packages ...
Selecting previously deselected package mdadm.
(Reading database ... 158452 files and directories currently installed.)
Unpacking mdadm (from .../mdadm_3.1.4-1+8efb9d1ubuntu6_i386.deb) ...
Selecting previously deselected package postfix.
Unpacking postfix (from .../postfix_2.8.5-2~build1_i386.deb) ...
Processing triggers for doc-base ...
Processing 40 changed doc-base files, 6 added doc-base files...
Registering documents with scrollkeeper...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Processing triggers for ufw ...
WARN: Couldn't find pid (is /proc mounted?)
Setting up mdadm (3.1.4-1+8efb9d1ubuntu6) ...
W: mdadm: failed to load MD subsystem.
Generating mdadm.conf... done (failed to scan arrays; /proc probably not mounted).
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: deferring update (trigger activated)
Setting up postfix (2.8.5-2~build1) ...
Adding group `postfix' (GID 126) ...
Done.
Adding system user `postfix' (UID 114) ...
Adding new user `postfix' (UID 114) with group `postfix' ...
Not creating home directory `/var/spool/postfix'.
Creating /etc/postfix/dynamicmaps.cf
Adding tcp map entry to /etc/postfix/dynamicmaps.cf
Adding group `postdrop' (GID 127) ...
Done.
/etc/aliases does not exist, creating it.

Postfix was not set up.  Start with
  cp /usr/share/postfix/main.cf.debian /etc/postfix/main.cf
.  If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed.  To view Postfix configuration
values, see postconf(1).

After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.0.0-12-generic
grep: /boot/config-3.0.0-12-generic: No such file or directory
Warning: No support for locale: en_GB.utf8
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place


Have i done something wrong?
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Sat Jan 07, 2012 1:40 pm

Run from terminal:
Code: Select all
dpkg-reconfigure mdadm
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sun Jan 08, 2012 5:56 am

Ok

I have completely followed the guide, but now when i reboot iget an error on DMI Pool verification.

ERRROR FD0 Read Error

Then boots into Grub Recovery.

Grub>

Is there a way i can recover grub boot loader from this screen?


Many thanks for your help so far :)
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sun Jan 08, 2012 6:41 am

I have booted back into the live USB and re-installed mdadm, however Disk Utility is no longer showing my RAID Arrays.

It just has one entry under multi disk devices, which states the Array is not running.

I have re-run this

cd /etc/mdadm
nano mdadm.conf

and it is only showing two of the Arrays and is now missing my boot partition md0 and the fully qualified names are now back in the cfg file, is this correct or am i looking in the wrong place?

Please see Picture

Upon closer inspection i noticed the the first partition /sda2, /sdb2 & /sdc2 have all dropped out of the array and are now unknown partitions again.

see picture

I await your response as im a bit lost where to go from here :-/
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sun Jan 08, 2012 6:53 am

Please could you post the command on how i can delete the Arrays so i can start again. As previously it has taken me nearly an hour per array to try and remove it. Having to install Webmin plus several reboots and a lot of swearing to try and remove the arrays, my command line skills are pretty poor coming form windows that I've been using for 18 years...

Now entering my 4th day trying to set this project up.. :( My girlfriend isn't that happy about it :-/
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Sun Jan 08, 2012 9:04 am

Give me detailed model of your motherboard.
Disable in BIOS all things for AMD RAID - change it to AHCI.

Firstly it would be better to use DVD disc, because your USB Drive can change disk order or something.

Do you have a floppy disk drive ??
"error: fd0 read error" - maybe disable it in BIOS
https://bugs.launchpad.net/ubuntu/+sour ... bug/568720

You've messed to much different RAID's and never cleared disks after go further.

How it's possible that you have /dev/sda2 with 200MB when you had in tutorial that /dev/sda1 should be /boot partition?
Besides, that 200MB /dev/sda1 should be also a RAID component drive.

Deleting the old arrays isn't everything - metadata of that arrays is still staying on the drive.
Try: mdadm -E /dev/sda and you will se this.

Install gdisk:
Code: Select all
sudo apt-get gdisk

Give results of:
Code: Select all
gdisk -l /dev/sda
gdisk -l /dev/sdb
gdisk -l /dev/sdc
cat /proc/mdstat
mdadm -D /dev/md0
mdadm -D /dev/md1
mdadm -D /dev/md2


To totally remove raid information from drive you have to use
Code: Select all
mdadm --zero-superblock /dev/sdX


Did you read: http://manpages.ubuntu.com/manpages/one ... adm.8.html
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby noodlemctwoodle on Sun Jan 08, 2012 9:55 am

I think I may of sorted it with the help of a friend, just rebuilding the Raid array now.
Will keep you posted :-)
noodlemctwoodle
Level 1
Level 1
 
Posts: 9
Joined: Thu Jan 05, 2012 7:59 am

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Sun Jan 08, 2012 8:30 pm

OK - but firstly clear all of drives, and start from the beginning.

To fully wipe you existing partitions and etc. you can do:
Run:
Code: Select all
gdisk /dev/sda

Choose "x", and then choose "z" - be careful - that's unrecoverable.

Then do also:
Code: Select all
dd if=/dev/zero of=/dev/sda bs=512 count=100000

This will clear all existing metadata on disks. Replace sda with sdb and sdc.

Next time be careful about partitioning:
/dev/sda1, /dev/sdb1, /dev/sdc1 -> /dev/md0 -> RAID1 -> /boot partition -> 200MiB[GParted is proposing in front to leave 1MiB - that's correct and do not change it]
/dev/sda2, /dev/sdb2, /dev/sdc2 -> /dev/md1 -> RAID5 -> / partition -> rest of the disk minus RAM size minus 1MiB [1GB of RAM = 1024MiB !!][for 2GB RAM you're leaving 2049MiB]
/dev/sda3, /dev/sdb3, /dev/sdc3 -> /dev/md2 -> RAID1 -> swap partition -> RAM size[for 2GB partition size is 2048MiB]

After that, you have 1MiB space on front and 1MiB on end of the disks. Front space for GPT, mdadm metadata and some MBR compatibility, end space for GPT backup partition table.
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby Hohlraum on Mon Jan 23, 2012 11:13 am

/dev/sda1 -> 200MiB for /boot - let the GParted align this from start with 1MiB[default] - that's needed for GPT and MDADM, and for good alignment - enable boot flag ON
/dev/sda2 -> we're choosing here to leave 4097MiB[RAM size + 1MiB] - If you have different size of RAM adjust this but add 1MiB to this value - that 1MiB is needed for GPT backup partition table on the end of the disk
/dev/sda3 -> choose 4096MiB or your RAM size - 1GB=1024MiB
Once again don't format partitions!, leave that 2x1MiB as a free disk size.


I see that you fixed the info about sda3 in a later post. You might want to update your original post because lots of sites are pointing to your guide.

Also for anyone trying this process. Best of luck. When the installer fails at the boot loader fail if you are like me the installer locks up and doesn't allow you to select for it to continue without the boot loader. Only thing you can do is hit escape which crashes the installer (which is really common, this distro is not ready for prime time in my experience (18 years of using linux 40hrs+ a week).
Hohlraum
Level 1
Level 1
 
Posts: 3
Joined: Sun Jan 22, 2012 1:56 pm

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby Signo on Tue Jan 24, 2012 12:23 pm

So to be more constructive were you able to complete the install after the crash or do you have a suggestion on how to fix it? I have experienced the crash you are talking about and after the install the machine failed to boot, and I could use some guidance.
Signo
Level 1
Level 1
 
Posts: 1
Joined: Tue Jan 24, 2012 12:17 pm

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby Hohlraum on Wed Jan 25, 2012 9:35 am

No, I wasn't able to complete the install. I tried twice and gave up. I decided to go with Ubuntu 11.10 instead and had it up and running with software RAID using the alternate install media in about 20 minutes.
Hohlraum
Level 1
Level 1
 
Posts: 3
Joined: Sun Jan 22, 2012 1:56 pm

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Fri Jan 27, 2012 8:24 am

My self I recommend the solution from my previous post.
viewtopic.php?f=46&t=89272

There is a RAID1 for OS and the rest using 2 disks.
My home PC station is using that solution with Linux Mint 12.

Also I have a server in my job with Linux Mint 12 Gnome from CD[light version] with server version kernel and removed not used apps like Thunderbird and etc.
There is a XEON E3 1230 processor[4-cores with HTT], 8GB of RAM and a disk structure:
RAID1 for OS using 2 disks
RAID10 for data using 6 disks [500GB] - total 1,5TB
All with mdadm software RAID.
RAID10 on this setup is reading with about 500MB/s and writes are about 170MB/s.

mint1 jk # cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sdc2[0] sdd2[1]
116427704 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sdc3[0] sdd3[1]
4193268 blocks super 1.2 [2/2] [UU]

md2 : active raid10 sdh1[5] sdg1[4] sdf1[3] sde1[2] sda1[0] sdb1[1]
1465149696 blocks super 1.2 128K chunks 2 far-copies [6/6] [UUUUUU]

unused devices: <none>
mint1 jk # hdparm -t --direct /dev/md2

/dev/md2:
Timing O_DIRECT disk reads: 1516 MB in 3.00 seconds = 504.75 MB/sec


System is used for virtual machine with KVM and Samba file sharing.
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Re: Mint 12 RAID 0 DMI Pool verification "system halt"

Postby jack_ on Fri Jan 27, 2012 3:27 pm

Hohlraum wrote:I see that you fixed the info about sda3 in a later post. You might want to update your original post because lots of sites are pointing to your guide.

Also for anyone trying this process. Best of luck. When the installer fails at the boot loader fail if you are like me the installer locks up and doesn't allow you to select for it to continue without the boot loader. Only thing you can do is hit escape which crashes the installer (which is really common, this distro is not ready for prime time in my experience (18 years of using linux 40hrs+ a week).


I've run my tutorial again today and now I understand what you mean by "installer locks up".
That's a Mint installer error - but fix is very, very simple... I've forgot to mention.

You just have to open list with disks and choose for example /dev/sda - that will unlock OK button !!!
Sorry - I've forgot to mention that.

I'm doing right now that tutorial on my virtual KVM machine and I'm doing also some screen-shots. Maybe it will help a little bit.

I've added a warning to point 6 about that.
Image
Image
Image
jack_
Level 1
Level 1
 
Posts: 22
Joined: Mon Dec 19, 2011 8:36 pm
Location: Poland

Linux Mint is funded by ads and donations.
 
Next

Return to Installation & Boot

Who is online

Users browsing this forum: austin.texas, tdockery97 and 39 guests