View previous topic :: View next topic |
Author |
Message |
atticus n00b
Joined: 29 Nov 2002 Posts: 35 Location: Northern Virginia
|
Posted: Sun Dec 01, 2002 2:49 am Post subject: Okay, another "drives" problem. |
|
|
I have three 2 gig hard drives in my machine. They're all the same make and model.
During the installation process, I cfdisked them, and made /dev/hda my main gentoo drive, /dev/hdb for /usr and /dev/hdc for /var.
I created the mount points, as told to, i.e.
Code: |
mkdir /mnt/gentoo/
mount /dev/hda3 /mnt/gentoo
mkdir /mnt/gentoo/boot
mount /dev/hda1 /mnt/gentoo/boot
mkdir /mnt/gentoo/usr
mount /dev/hdb1 /mnt/gentoo/usr
mkdir /mnt/gentoo/var
mount /dev/hdc1 /mnt/gentoo/var
|
It seemed to work okay, but, the first time, I tried untarring, and got errors. I ran "mount," to find that /dev/hdc was mounted as vfat. wtf. So, I ran cfdisk on /dev/hdc and got an error. Okay.... so, I then ran fdisk on /dev/hdc, deleted the partition, wrote to the table, and quit. I then ran cfdisk on /dev/hdc, and got no error, but a normal screen, with /dev/hdc1 formatted as ext3, full space utilized. So, for shits and giggles, I deleted the partition, recreated, rebooted, formatted the partition as ext3 (again), and then tried untarring. Hooray! Success this time!
But...
After I chrooted, I ran "env-update," and got this:
Code: |
>>> /var/tmp doesn't exit, creating it...
portage: couldn't create /var/tmp; exiting.
|
Getting ready to go insane here. Any help would be greatly appreciated. |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Sun Dec 01, 2002 6:43 am Post subject: |
|
|
I bet it's still mounted read-only as vfat. If so, try searching the forums for "ghost and superblock". _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
lx Veteran
Joined: 28 May 2002 Posts: 1012 Location: Netherlands
|
Posted: Sun Dec 01, 2002 12:10 pm Post subject: |
|
|
The problem defined by rac (old vfat block screws up mount autodetection of partition type) should give errors during untarring the image, but as you stated this succeeds.
The /var/tmp dir and other files are in the tar image file, so probably you extracted them to one partition instead of over the already mounted structure (check if they exist by doing ls /var, ), so mounting on var will give the empty partition, if so just untar over the mounted structure or mount the files on a temporary empty dir and mv the files into the correct partition. (ea. mv /mnt/gentoo/var/tmp/* /mnt/tmp).
Hope you fix it,
Cya lX. _________________ "Remember there's a big difference between kneeling down and bending over.", Frank Zappa |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Sun Dec 01, 2002 5:45 pm Post subject: |
|
|
lx wrote: | The problem defined by rac (old vfat block screws up mount autodetection of partition type) should give errors during untarring the image, but as you stated this succeeds. |
I was figuring that the partition could have been mounted with an explicit filesystem type during the untarring, but then was remounted just using fstab later on. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
atticus n00b
Joined: 29 Nov 2002 Posts: 35 Location: Northern Virginia
|
Posted: Sun Dec 01, 2002 5:47 pm Post subject: |
|
|
Nope! A much easier solution was brought to me in a PM by a friendly forum user!
This user suggested to me, mounting the partitions explicitly using -t.
i.e.
Code: |
mkdir /mnt/gentoo/usr
mount -t ext3 /dev/hdb1 /mnt/gentoo/usr
mkdir /mnt/gentoo/var
mount -t ext3 /dev/hdc1 /mnt/gentoo/var
|
Worked great. |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Sun Dec 01, 2002 6:35 pm Post subject: |
|
|
That's exactly what I was talking about. Does this solution survive a reboot? _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
atticus n00b
Joined: 29 Nov 2002 Posts: 35 Location: Northern Virginia
|
Posted: Sun Dec 01, 2002 6:40 pm Post subject: |
|
|
no telling yet. I'm still compiling/building.... |
|
Back to top |
|
|
lx Veteran
Joined: 28 May 2002 Posts: 1012 Location: Netherlands
|
Posted: Sun Dec 01, 2002 8:18 pm Post subject: |
|
|
Well in /etc/fstab the filetype is stated, so it probably survives a reboot, but I don't think the remaining vfat block is overwritten (ever), so you can run in some trouble later on, well if you mount it manually just remember to give the correct type,
Cya lX. _________________ "Remember there's a big difference between kneeling down and bending over.", Frank Zappa |
|
Back to top |
|
|
atticus n00b
Joined: 29 Nov 2002 Posts: 35 Location: Northern Virginia
|
Posted: Sun Dec 01, 2002 10:03 pm Post subject: |
|
|
Okay, "grub" went fine. I think it froze the last time because of a defective 3 gig drive I had in my machine. I removed it, and replaced it with a different two-gigger.
Anyway, I ran
and got
Code: |
Filesystem type is ext2fs, partition type 0x83
|
Is this normal? My /boot partition is formatted as ext3, FYI |
|
Back to top |
|
|
atticus n00b
Joined: 29 Nov 2002 Posts: 35 Location: Northern Virginia
|
Posted: Sun Dec 01, 2002 10:36 pm Post subject: |
|
|
I guess it's no cause for alarm, since I seem to be booting just fine.
Where's the cool splash screen logo?
All I got was a goofy little menu... :O |
|
Back to top |
|
|
BradN Advocate
Joined: 19 Apr 2002 Posts: 2391 Location: Wisconsin (USA)
|
Posted: Tue Dec 03, 2002 3:37 am Post subject: |
|
|
Yeah, ext3 is just ext2 with journalling added on - it can be read with ext2 drivers just fine as far as I know. |
|
Back to top |
|
|
uziel n00b
Joined: 14 Feb 2003 Posts: 32
|
Posted: Thu Feb 20, 2003 9:44 am Post subject: empty partition or entire disk with dd |
|
|
As long as there is no data on the disk, you could as well use dd to clean up the beginning of the disk or partition. Just
Code: | dd if=/dev/zero of=/dev/hdX(Y) bs=1k count=1024 |
to erase the first MB of the HD or partition.
THIS WILL ERASE ALL DATA ON /dev/hdX or /dev/hdXY RESPECTIVELY
Then you can create your desired FS. If you cleaned the whole drive, e.g. hda instead of hda1, you need to re-create your partition, of course
If mount still does not default to the desired FS, just leave out the count to erase the whole partition or hd, instead of just the beginning. It sure takes some time, especially with huge disks available these days, but hey - I always did that, so unfortunately I can't tell if the "quick fix" would do the job in every single case. But the complete zero-ing of course will.
Chris _________________ Those who promise their way of freedom and peace still do not understand the meaning of the word... |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|