I have my FC5 running neatly and all configured just the way I like it , though I have begun running out of free space on the installed partition here is what the installed partition info looks like:
/dev/hda1 * 0+ 2610 2611- 20972826 7 HPFS/NTFS >> M$ Partition /dev/hda2 2611 8484 5874 47182905 7 HPFS/NTFS start: (c,h,s) expected (1023,254,63) found (1023,0,1) /dev/hda3 8485 8497 13 104422+ 83 Linux start: (c,h,s) expected (1023,254,63) found (1023,0,1) /dev/hda4 8498 9728 1231 9888007+ 5 Extended start: (c,h,s) expected (1023,254,63) found (1023,0,1) /dev/hda5 8498+ 9728 1231- 9887976 8e Linux LVM start: (c,h,s) expected (1023,254,63) found (1023,1,1)
I don't mind breaking down the M$ partition and moving the Linux fs to /dev/hda1 . Any Best Practices that you would suggest ??
Cheers, Francis
On Wednesday 23 August 2006 14:12, Francis wrote:
I have my FC5 running neatly and all configured just the way I like it , though I have begun running out of free space on the installed partition here is what the installed partition info looks like:
Should've studied risk mgmt. Should've been more proactive ;)
I don't mind breaking down the M$ partition and moving the Linux fs to /dev/hda1 . Any Best Practices that you would suggest ??
You can try resizing your partition but it might just screw up your system :P But do have a disaster recovery plan in hand before going ahead ;) Risk mgmt....
Dinesh Joshi wrote:
You can try resizing your partition but it might just screw up your system :P
Resizing is not a good idea because I got important data on the other drives. Risk Management , well I don't mind breaking the M$ partition [/dev/hda1] there is nothing there except ten.BV all My Documents are on /dev/hda2. Here are the issues that I foresee -> Would just copying the fs from /dev/hda5 to /dev/hda1 and then changing the kernel parameter work ?? I meen /root , /media, /var as you say are mount points , so do they have to be registered ?? ->/dev/hda5 8498+ 9728 1231- 9887976 8e Linux LVM the partition was created during installation and if I just format /dev/hda1 as ext3 and create the file structure there would it be alrite , how would the OS react to that ?
Cheers Francis
On 8/24/06, Francis mail.francispereira@gmail.com wrote:
Dinesh Joshi wrote:
You can try resizing your partition but it might just screw up your system :P
Resizing is not a good idea because I got important data on the other drives. Risk Management , well I don't mind breaking the M$ partition [/dev/hda1] there is nothing there except ten.BV all My Documents are on /dev/hda2. Here are the issues that I foresee -> Would just copying the fs from /dev/hda5 to /dev/hda1 and then changing the kernel parameter work ??
In all kinds of Redhat & Fedora systems, while installing the OS, its create paritions as primary or LVM and puts a label for it even. The kernel boots just using the Label and not the direct partition.
I meen /root , /media, /var as you
say are mount points , so do they have to be registered ?? ->/dev/hda5 8498+ 9728 1231- 9887976 8e Linux LVM the partition was created during installation and if I just format /dev/hda1 as ext3 and create the file structure there would it be alrite , how would the OS react to that ?
What you can do, to try whether this works is. Format ur M$ . Be sure that GRUB is what booting ur system. Copy ur /dev/hda5 files directly into /dev/hda1. now, in grub, edit the line, remove the "LABEL=" option and put the device /dev/hda1 and try booting. and BTB, which is ur boot parition?. or are u booting GNU/Linux thru NTLDR (M$ Bootloader)?
Try it on ur own risk.. This is an option to just try. do it if u know how to recover or get out if u do any wrong.
Cheers Francis
Pushparajan V wrote:
and BTB, which is ur boot parition?. or are u booting GNU/Linux thru NTLDR (M$ Bootloader)?
I am using GRUB and I am sure I would be able to reinstall GRUB if I get it off the MRB , Though there is one thing still at the back of my mind : /dev/hda3 8485 8497 13 104422+ 83 Linux as you see the /boot is a different partition itself so if i copy the whole fs and then cerate a directory called /boot and link it to /dev/hda3 how would the system react to this change. Also my kernel and initrd is at /dev/hda3
Try it on ur own risk.. This is an option to just try. do it if u know how to recover or get out if u do any wrong.
;-)
Cheers Francis
On 8/24/06, Francis mail.francispereira@gmail.com wrote:
I am using GRUB and I am sure I would be able to reinstall GRUB if I get it off the MRB , Though there is one thing still at the back of my mind : /dev/hda3 8485 8497 13 104422+ 83 Linux as you see the /boot is a different partition itself so if i copy the whole fs and then cerate a directory called /boot and link it to /dev/hda3 how would the system react to this change. Also my kernel and initrd is at /dev/hda3
If you have a different partition for /boot (/dev/hda3) then I'm guessing that your boot sequence for grub would be something like this:
root (hd2,0) kernel /boot/vmlinuz root=/dev/hda5 ro <other params> initrd ... boot
Try this then: Create the alternate FS on hda1 and replace hda5 with hda1 in the 'kernel' line in menu.lst.
Ofcourse, "no bharchuk" ;)
Siddhesh
I took a rather different look towards moving the file , I copied each directory except the volatile ones i.e /dev and /proc on a spare harddisk to test weather or not the migration would work . Well turns out the kernel could successfully boot up . I can run the OS in run level 1 and 2 but all Hell Breaks loose when I switch to runnlevel > 2 as the system just stops at STARTING SYSTEM LOGGER. Any Inputs ?? Cheers, Francis
--- Francis mail.francispereira@gmail.com wrote:
Dinesh Joshi wrote:
You can try resizing your partition but it might
just screw up your
system :P
Resizing is not a good idea because I got important data on the other drives. Risk Management , well I don't mind breaking the M$ partition [/dev/hda1] there is nothing there except ten.BV all My Documents are on /dev/hda2. Here are the issues that I foresee -> Would just copying the fs from /dev/hda5 to /dev/hda1 and then changing the kernel parameter work ?? I meen /root , /media, /var as you say are mount points , so do they have to be registered ?? ->/dev/hda5 8498+ 9728 1231- 9887976 8e Linux LVM the partition was created during installation and if I just format /dev/hda1 as ext3 and create the file structure there would it be alrite , how would the OS react to that ?
Fransis, before you do any shifting, please backup your data on cd or else you too will be asking for file recovery softwares.
I was doing the same thing that you are planning to do. I wanted to push my running os from the last partition to the one just after vfat. The method was to use dd if=/dev/hdx of=/mountpoint/distro.img and then its reverse to paste the image on the target partition. Since I wanted to resize all my partitions after vfat, I tried to backup the img on the last vfat partition but ran into file sise limit problems for the vfat partition. Then I booted into the largest linux partition of another distro to carry out the same command. There was an unused folder that I emptied, only to find out later that some months ago, that folder was created to mount my working distro that was on another partition.
Anyway, use a large linux partition to save your working partition as an image. Then transfer the image to the target partition. Please check for file size limits for the fs on the partition you want to save the image. I wonder if dd can be used to directly move a partition's contents to another partition, like dd if=/dev/hdax of=/dev/hday. The experts can give some inputs on that.
Regards,
Rony.
___________________________________________________________ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
Some time ago Rony Bill wrote: Rony ,Thanks a lot for the heads up
I wonder if dd can be used to directly move a partition's contents to another partition, like dd if=/dev/hdax of=/dev/hday. The experts can give some inputs on that .
:-)
Regards,
Rony
Cheers Francis.
I had a look at the dmesg for the new fs and here is what i See :
EXT3 FS on hdb1, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on hda3, internal journal EXT3-fs: mounted filesystem with ordered data mode. *Adding 1048568k swap on /dev/VolGroup00/LogVol01. **Priority:-1 extents:1 across:1048568k ^^^^^^^ thats the last Entry I have* I think its the swap space thats causing the issue because I Just copied the fs on to a EXT3 partation , How do I register a new Swap Space for the newly created fs or how to I STOP the *Adding 1048568k swap on /dev/VolGroup00/LogVol01. ?? *Cheers, Francis
On 8/25/06, Francis mail.francispereira@gmail.com wrote:
I think its the swap space thats causing the issue because I Just copied the fs on to a EXT3 partation , How do I register a new Swap Space for the newly created fs or how to I STOP the *Adding 1048568k swap on /dev/VolGroup00/LogVol01. ??
See /etc/fstab. It will contain an entry for swap partition (ur swap parition seems to be LVM parition). Remove that. So that this message can be stoped. After the OS starts, you can add a partition as swap easily.
*Cheers,
Francis
Pushparajan V wrote:
See /etc/fstab. It will contain an entry for swap partition (ur swap parition seems to be LVM parition). Remove that. So that this message can be stoped. After the OS starts, you can add a partition as swap easily.
Forgot to Mentioned i have removed all the VolGrp entries in the fstab but still on boot up Even before the init starts up i.e just when the kernel uncompresses and boots up i see a message "searching for Logical Volume Groups on all Physical Drives". Yes this could be because I have the device mapper inbuilt into my kernel . But all this still does not explaing you the susyet logger cant start up . The system seems to run fine in run level 2 and 3 . Cheers, Francis
Wooo Whoooo , I just copyied the whole file system again and the OS successfuly booted rite this time . The last time I did it I had issues copying some files in the /var . I copyied it first with a live ubuntu cd for partation hda5 to partation hda1 with cp --copy-contents -f -R -p SORCE DST . Booted into the GUI of the old fs and copyied the /var Again from the GUI and it did not complain . The changes that I havd to make to the newly created fs were to fstab only and the GRUB ofcours .
Cheers, Francis
On 25/08/06, Francis mail.francispereira@gmail.com wrote:
Pushparajan V wrote:
See /etc/fstab. It will contain an entry for swap partition (ur swap parition seems to be LVM parition). Remove that. So that this message can be stoped. After the OS starts, you can add a partition as swap easily.
Forgot to Mentioned i have removed all the VolGrp entries in the fstab but still on boot up Even before the init starts up i.e just when the kernel uncompresses and boots up i see a message "searching for Logical Volume Groups on all Physical Drives". Yes this could be because I have the device mapper inbuilt into my kernel . But all this still does not explaing you the susyet logger cant start up . The system seems to run fine in run level 2 and 3 . Cheers, Francis
On 8/29/06, francis pereira mail.francispereira@gmail.com wrote:
Wooo Whoooo , I just copyied the whole file system again and the OS successfuly booted rite this time . The last time I did it I had issues copying some files in the /var . I copyied it first with a live ubuntu cd for partation hda5 to partation hda1 with cp --copy-contents -f -R -p SORCE DST . Booted into the GUI of the old fs and copyied the /var Again from the GUI and it did not complain . The changes that I havd to make to the newly created fs were to fstab only and the GRUB ofcours .
Great! It'd be good if you could write a Howto of sorts for this on your blog/site.
Siddhesh
sometime today Siddhesh wrote:
Great! It'd be good if you could write a Howto of sorts for this on your blog/site.
Will Certainly do that , Kinda tied up with work rite now but will get working on it soon .
Cheers, Francis
-
Dinesh Joshi -
Francis -
francis pereira
-
Pushparajan V -
Rony Bill -
Siddhesh Poyarekar