Probleming installing Fadora Core 4 on new SATA harddrive; maybe manual parition?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Probleming installing Fadora Core 4 on new SATA harddrive; maybe manual parition?
Hello everyone. I ran into some problems, i think it was from manually partitioning the harddrive. I used Fadora Core's built in paritioning software to do it though. I'm a big noob so bare with me! I never did a manual parition.
I have a 200 Gig SATA harddrive and i layed the partitions out as follows:
Then it listed my NTFS harddrive that i'm on right now
everything i thought went fine,
then I selected to install packages, i went to custom and added all the packages becuase i have alot of room might as well use it. Well then the next screen came on and said,
"Error: informing the kernal about modifications to parition /dev/sda2-device or resource busy. This means linux won't know about any changes you made to /dev/sda2 until you reboot-so you shouldn't mount it or use it in any way before rebooting. So i clicked ignore. Then I got a list of errros, i was able to save it to a flopppy drive. its 856kb though so i'm not going to copy and paste it!
but i think the beginning is the improtant stuff!
Traceback (most recent call last):
File "/usr/lib/anaconda/gui.py", line 1137, in handleRenderCallback
File "/usr/lib/anaconda/iw/progress_gui.py", line 244, in renderCallback
File "/usr/lib/anaconda/gui.py", line 873, in nextClicked
File "/usr/lib/anaconda/dispatch.py", line 174, in gotoNext
File "/usr/lib/anaconda/dispatch.py", line 242, in moveStep
rc = apply(func, self.bindArgs(args))
File "/usr/lib/anaconda/packages.py", line 579, in turnOnFilesystems
File "/usr/lib/anaconda/partedUtils.py", line 726, in savePartitions
error: Error: Error informing the kernel about modifications to partition /dev/sda2 - Device or resource busy. This means Linux won't know about any changes you made to /dev/sda2 until you reboot - so you shouldn't mount it or use it in any way before rebooting.
Local variables in innermost frame:
self: <partedUtils.DiskSet instance at 0xb7cf190c>
disk: <PedDisk object at 0xb7f1df08>
* No growable logical volumes defined in VG VG Request -- name: VolGroup00 uniqueID: 23
format: None pesize: 32768
* Used size vs. available for vg VolGroup00: 194336 194336
* moving (1) to step partitiondone
* moving (1) to step bootloadersetup
* moving (1) to step bootloader
* moving (1) to step networkdevicecheck
* moving (1) to step network
* moving (1) to step firewall
* moving (1) to step timezone
* moving (1) to step accounts
* moving (1) to step readcomps
* Using file:///mnt/source/Fedora/base/comps.xml
* base references package cryptsetup which doesn't exist
* base references package openCryptoki which doesn't exist
* base references package prctl which doesn't exist
* legacy-software-development references package compat-libstdc++-devel which doesn't exist
* legacy-software-development references package compat-gcc-c++ which doesn't exist
* legacy-software-development references package compat-gcc-295 which doesn't exist
* legacy-software-development references package compat-gcc-296 which doesn't exist
* legacy-software-development references package compat-gcc which doesn't exist
* legacy-software-development references package compat-libstdc++ which doesn't exist
* legacy-software-development references package compat-libstdc++-295 which doesn't exist
* legacy-software-development references package compat-libstdc++-32 which doesn't exist
* legacy-software-development references package compat-gcc-c++-32 which doesn't exist
* compat-arch-support references package libtool-libs which doesn't exist
* compat-arch-support references package openCryptoki which doesn't exist
* compat-arch-support references package libf2c which doesn't exist
* legacy-software-support references package compat-pwdb which doesn't exist
* java-development references package jakarta-commons-daemon which doesn't exist
* java-development references package beecrypt-java which doesn't exist
* java-development references package jakarta-commons-daemon-javadoc which doesn't exist
* gnome-desktop references package gnome-backgrounds which doesn't exist
* core references package yaboot which doesn't exist
* core references package iprutils which doesn't exist
* core references package elilo which doesn't exist
* core references package s390utils which doesn't exist
* core references package ppc64-utils which doesn't exist
* japanese-support references package jcode.pl which doesn't exist
* mail-server references package perl-Cyrus which doesn't exist
* miscallvars references package anaconda-product which doesn't exist
* miscallvars references package lilo which doesn't exist
* kannada-support references package openoffice.org-langpack-kn_IN which doesn't exist
* web-server references package struts11-webapps-tomcat5 which doesn't exist
* web-server references package httpd-suexec which doesn't exist
* base-x references package desktop-backgrounds-extra which doesn't exist
* development-tools references package gcc-ppc32 which doesn't exist
* development-tools references package pfmon which doesn't exist
* development-tools references package gcc-c++-ppc32 which doesn't exist
* moving (1) to step desktopchoice
* moving (1) to step selectlangpackages
* moving (1) to step package-selection
* moving (1) to step handleX11pkgs
* moving (1) to step handlemiscpkgs
* No pcic controller detected
* Needed lvm2 for None
* Needed lvm2 for None
* Needed e2fsprogs for /
* Needed e2fsprogs for /boot
* Needed e2fsprogs for /home
* moving (1) to step fixupconditionals
* moving (1) to step checkdeps
* moving (1) to step confirminstall
* discNums is [1, 2, 3, 4, 5]
* moving (1) to step install
* moving (1) to step enablefilesystems
* parted exception: Error: Error informing the kernel about modifications to partition /dev/sda2 - Device or resource busy. This means Linux won't know about any changes you made to /dev/sda2 until you reboot - so you shouldn't mount it or use it in any way before rebooting.
No volume groups found
Wiping internal VG cache
Finding all volume groups
No volume groups found
Reading all physical volumes. This may take a while...
cal volumes. This may take a while...
I think the problem isn't in the fact that you partitioned it manually, but partitioned it incorrectly. I haven't installed LVM on Fedora, but in Debian I have to tell it on the main partition screen that the space (/dev/sda2 in your case) is space for a LVM. Then once the space is established, (looks like all of the 200 GB drive minus 100 MB for boot), I have to configure the LVM, which is where you would subdivide the LVM into the swap, root, and home partitions. Something in there was screwed up. Try to redo it, and see if you get better results.
Thanks Jim, frankly i don't even know what an LVM is, do I need an LVM? I just saw it there, and orginally, the 180 gigs or so was all in the / or root and there wasn't any /home! i was like wtf! so i changed it, and added a few things. And when you say you have to tell it on the mian parition screen (/dev/sda2) thta its an LVM, how did you do that? I thought thats what I did already because it says:
--/dev/sda2 VolGroup00 LVMPV
where LVMPV is the file type of that partition, so doesn't that mean i did it?
and I did subdivide the LVM into the swap,root, and home paritions here:
LVM Volume Groups:
I made the swap part of the LVM to be of type swap and to be 1984 megs, i made the root be of type ext and be 7000 megs and i made the home occupy the rest - the /boot which occupied a 100 and wasn't in the LVM becuase oringally it wasn't, so i didn't mess with it.
maybe my format was confusing, or maybe i'm just too noobish to understand what your trying to tell me.
If you don't know what a LVM is, I would look that up first. It stands for Logical Volume Manager(Management). It allows you to add and remove space to your system. In non LVM systems, if you add a new hard drive, it isn't just included into the root (/) of the filesystem. You have to manually tell the linux system that you have a new drive, and you want to mount X on that drive. LVM takes some of that akwardness away, but it adds a whole new set of it. With the LVM you could add another disk and then add it to the VLM groups, and simply have more space. I can't see why you would need all but /boot in an LVM, but if you want to do it that way, there isn't a reason I know of that you "can't".
You need to keep /boot out of the LVM because /boot contains the kernel, and the LVM needs to be read off the system, which requires the kernel to be up. If you put /boot in the LVM, you'd have no way to read the LVM without the kernel, and you'd be SOL. On my home machine I have /home in an lvm, but leave the root / and swap outside of the LVM. Also, don't waste 2 Gb on swap. The old double ram rule for swap goes back a long way. I have 750 MB ram, and 1 GB of swap. In the 9 months I have used my current machine, I have never used swap even once. I would scale down your swap to 500 MB at the most, and dump the freed space into /home.
You don't "need" LVM at all, and it can be a PITA at times. Since this seems to be your first system, I would suggest just partitioning the drive into you speratate things (/boot / /home swap) and letting that be it. Make /boot the first partition, and let it overwite the MBR on the IDE drive if that is what boots by default.
The Place to select what type of space is used is the same where you selected swap vs ext3. If you look through the whole list, you see choices. I think ext3 is 83, and swap is 82, or something like that. One of the choices is space for LVM. I don't remember the number, but it can be configured. First time out, I wouldn't bother with it. You can always use programs like qtparted to change partition sizes down the road if you have too much/little space.
I'm so close!! thank you JIM!! but still i'm not done haha, okay i got rid of the LVM's!
I started ncie and clean, with just
so my first move was to click the freespace and then click NEW, then i choose my mount point to be root: / size: 7000 fixed sized, didn't check the button thta said force to be a primary partition.
I then went on to create a /boot to be 100 megs because fedora core says its gota be 75 or more.
created swap to be 500
then last but not least i put the rest into /home so when i was done it looked like this:
So i got to install, and everytihg is working fine, its preparing to install the packages and it says:
934megs of space needed, wouldn't 7000 megs be enough for r00t? is it instaling all the progams in r00t and not /home or what? thank you again!
I would expect a Fedora Core install to be much more than 936 Mb in root. All the rpm based distros are among the largest, as they come with the most packages "built in". Also, I think you mentioned earlier that you told it to install everything, since you had the space. If that is still the case, You will need way more than 7 Gb for /.
I just looked, and you did say you checked everything. In that case, you'll need to steal several GB from home, and move the space into root. The 936 Mb error was just that you needed 936 Mb of ADDITIONAL space to fit everything, and that is before they are unpacked and in use! With everything, I would bet you'll need more like 15 Gb of space. Even 20 wouldn't be too much considering the size of your drive. And yes, all system wide programs do not go in /home. The only things in /home are your personal files. The vast majority of system files are in /usr and /var, and controlled by the files in /etc.
Jim I ran into yet another problem. I jacked up my r00t space to 10 gigs, that was enough, everything installed I thought fine, but no.
I reb00t the system as it said, its in console mode, its doing all its checked it passed like the first hardware check, then it went into graphical mode (quite nice) and then it goes back into text based install then i see a nice big red [FAIL] Checking filesystem:
fsck.ext 3: unable to resolve:
(Label = /home)
it told me to enter my root password in for maintence, so i did, and it dropped me a shell, i have no idea what to do with the shell so i typed in ls, and it had alot of folders, /home, /dev, /root, /tmp, etc. but Without a file system, i'm screwed. So I rebooted and tried the bootloader when it says to press any key to enter menu at the start up screen of fadora, i saw 2 versions of linux, same version, the 2nd one was just named somthing different then windows, i tried all of them, both versions failed, and trying to boot to windows also failed i got a:
What could i have possiblity did wrong with the partitioning? I started off with Free Space, did everything i showed u, Do i have to make one of these things paritions a primary partition? Maybe that will fix my problem? Becuase everytime i made a new parition with the program fedora core supplied, i didn't click the Force to be a primary partition. But other then that, i don't see what i did wrong!
Another odd thing, everytime i go back in there to try to fix my earlier failure it always puts a different parition into the "Extended" part like this:
first time i did it:
OH yeah, one time i did try to make /home the primary partition and i got that error saying how my sda2 (/home) is busy and it gave my above error i had awhile ago with VML's, ahhh mandrake 8.2 was much easier to install back when i was 16! Now i'm 20 and i'm clueless hah.
Just a sda1 (10Gb) as the root or "/" and another sda2 1Gb for swap. Save a lot of bother.
So you don't even need a /home? And where would i put the rest of my memory? i have 200 gigs dedicated to linux
Maybe a problem with the names of the drives. You have 2 physical drives correct? An IDE drive that has Windows and the SATA with linux? What is the primary boot drive (as determined by BIOS)? If you boot from the IDE first, then the Windows command should probably be
When the grub screen appears, move the highlight down to windows, and then hit "e" for edit. Change the command to hd0,0 from hd1,0. Hopefully that will be your issue. If the SATA is set as the primary boot device, then the hd1,0 should be correct.
I'm not clear on the difference between primary and extended partitions, but you can only have 4 primary partitions, 3 if you also have extended partitions, because the 4th is used to map the extended ones. It makes absolutely no difference in most cases wether a partition is on a primary or extended partition, but /boot should be on a primary. It used to have to be the first primary, but I think that has changed with the passing of years.
I would google the error message that you got. fsdk is a disk check program, suggesting that the drive is somehow/someway flawed, but that makes little sense as it has not been used. You did format the drive as it was being created no? It takes MUCH less time than MS formatting.
You don't need to put /home on a separate partition, but if you move from one distro to another, you'll be glad that you did. If you just do the 2 partitions, / and swap, then everything is on the single space. Any reinstall with format will kill everything you have. With a separate /home, you can move to something else, and save the things you downloaded/played with/wrote.
I'm busy with hardware failures here, so I may not see your reply(s) till tomorrow, but try http://www.google.com/linuxfor your error, also check regular google, groups.google, and of course the great boards here. Chances are very good that somebody has had the same problem, and that it has been solved and written about here.
Since you have no MS system in sda, with which you have installed Fedora, and it is booting then this implies you have pushed your Windows disk down by one in the booting queue. Therefore the Windows orginally installed in the 1st bootable disk will not work.
The Windows disk (hd1) needs to be "re-mapped" as follow