This is a discussion on system moved within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> i moved sys from hda1(5gb) to hdb1(60gb) but "df" report always the old hd space (5gb)! anyone know how ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| ~SCRØØGE~ wrote: > i moved sys from hda1(5gb) to hdb1(60gb) but "df" report always the old hd > space (5gb)! anyone know how to fix? > thanx! How did you move it, "dd" or "cp"? Try it like this. First partition and format the 60GB drive. cd / mkdir /new mount /dev/hdb1 /new DON"T copy /proc or /new cp -ax bin boot dev etc ... /new/ mkdir /new/proc If you are going to use the drive from a different device (hdb,hdc,...) then you will need to edit /etc/fstab and change the devices used to mount the partitions. -- Confucius: He who play in root, eventually kill tree. Registered with The Linux Counter. http://counter.li.org/ Slackware 9.1.0 Kernel 2.4.26 SMP i686 (GCC) 3.3.3 Uptime:7 days, 11:29, 1 user, load average: 1.12, 1.04, 1.01 |
| |||
| scrooge@kkk.gov wrote : > i moved sys from hda1(5gb) to hdb1(60gb) but "df" report always the old hd > space (5gb)! Then i guess that you used 'dd' for the job. The problem is that 'dd' makes an exact clone. > anyone know how to fix? Maybe GNU-parted can handle this? I'm just guessing. But if you still has the old system disk around then plug it back and start by reading /usr/doc/Linux-HOWTOs/Hard-Disk-Upgrade -- Thomas O. This area is designed to become quite warm during normal operation. |
| |||
| Thomas Overgaard wrote: > Then i guess that you used 'dd' for the job. The problem is that 'dd' > makes an exact clone. nope, i've used only cp :-\ >> anyone know how to fix? > Maybe GNU-parted can handle this? I'm just guessing. mmm nice hint, i've to see |
| |||
| David wrote: > ~SCRØØGE~ wrote: >> i moved sys from hda1(5gb) to hdb1(60gb) but "df" report always the old >> hd space (5gb)! anyone know how to fix? >> thanx! > > How did you move it, "dd" or "cp"? cp! > Try it like this. > > First partition and format the 60GB drive. > > cd / > mkdir /new > mount /dev/hdb1 /new > > DON"T copy /proc or /new > cp -ax bin boot dev etc ... /new/ > mkdir /new/proc is what exactly i've done! perhaps in init 1 ! :-( |
| |||
| ~SCRØØGE~ wrote: > > is what exactly i've done! perhaps in init 1 ! :-( Did you edit /etc/fstab on the 60GB disk so it mounts the new drive instead of the 5GB drive/partition or did you move the 60GB drive to /dev/hda ? Did you also edit /etc/lilo.conf so it mounts /dev/hdb1 as the "/" root partition? -- Confucius: He who play in root, eventually kill tree. Registered with The Linux Counter. http://counter.li.org/ Slackware 9.1.0 Kernel 2.4.26 SMP i686 (GCC) 3.3.3 Uptime:7 days, 11:49, 1 user, load average: 1.02, 1.04, 1.00 |
| |||
| ~SCRØØGE~ wrote: > i moved sys from hda1(5gb) to hdb1(60gb) but "df" report always the old > hd space (5gb)! anyone know how to fix? > thanx! It sounds like you somehow copied the raw device instead of the files. The way I usually do it is... (1) boot up an installation cd (2) partition target drive (3) make filesystem on destination drive (4) mount both the source & destination partitions let's say the mount points are /1 and /2 (5) cp -a /1/* /2 (6) fix /etc/fstab on the new copy I prefer that the source partition is not the system running because some things change dynamically while it is running. Neil |
| |||
| David wrote: > Did you edit /etc/fstab on the 60GB disk so it mounts the new > drive instead of the 5GB drive/partition or did you move the 60GB > drive to /dev/hda ? > Did you also edit /etc/lilo.conf so it mounts /dev/hdb1 as the > "/" root partition? yes :-( |