Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: beakersloco on July 23, 2006, 09:07:14 AM
-
I am having a problem attempting to add a drive. A buddy wants to play around with SME and we spent 2 hours before giving up for the night talking via phone and me directing him what to type. Hes not very familiar with the command line level stuff so im attempting to help him thru some of the hard stuff. Part of our problem was that we were running the commands thru putty and should have been on the server itself.
I was using the instructions found here
http://mirror.contribs.org/smeserver/contribs//mblotwijk/HowToGuides/AddExtraHardDisk.htm
His machine has 2 drives in it a 40 and a 60 I believe
We were getting up to step 3 and after running the command
everything was fine untill he ran the following
If you are using SME 5.6 or newer, it is recommended to convert the partition to the ext3 format: [root@hogwarts /]# tune2fs -j /dev/md2
root@cube-0 ~]# tune2fs -j /dev/md2
tune2fs 1.35 (28-Feb-2004)
Creating journal inode: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@cube-0 ~]# mkdir /mnt/bigdisk
-bash: mkdir: command not found
[root@cube-0 ~]#
I figured the first time it was the above command so he reloaded the machine and then we started again and after running this command
mkfs -t ext2 /dev/md2
skipped to step 4 and received a bunch of error messages device busy and another one . Are we not giving the mkfs -t ext2 /dev/md2 command enough time to run ?
At this point we are going to try again next weekend and I think Im going to load 7 on a machine that I have to test the commands on.
here is what he got when we ran the commands in putty which leads me to think the format was done
[root@cube-0 ~]# mkfs -t ext2 /dev/md2
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
4872896 inodes, 9743392 blocks
487169 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=12582912
298 block groups
32768 blocks per group, 32768 fragments per group
16352 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@cube-0 ~]#
He claims that both drives are on the same IDE cable ... I thinking of having him but one drive on the other cable if that will help . Any ideas would be appreciated Thanks
-
Why are you using /dev/md2? that is part of the server setup when you first install the sme server you have /dev/md1 and /dev/md2 as per system install.
if it's on the primary secondary then it will be /dev/hdb
Have a search on here I did a draft how to on getting another drive working.
-
I did do a search ..that is why I asked for help because what I found did not help me. I also tried using the hdb and it gave an error I dont recall what it was and after I had him do a df I saw this
[root@cube-0 ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/main-root
37285432 1008472 34382972 3% /
/dev/md1 101018 12320 83482 13% /boot
none 257240 0 257240 0% /dev/shm
[root@cube-0 ~]#
Since when I do a df on my 6.1 system is shows differently I figured that might be what we needed to use. Then the command worked. Now it could be that the person I am attempting to help setup his server might have miskeyed what I was telling him. Latter on this week before the weekend I am going to try it myself just to make sure but figured a post here would not hurt and thier might be an updated workstep that my search did not find !
Also if you want to help then help I dont need a lecture on using the search button as I have already done so. But keep in mind I am not perfect so I might have overlooked the post with the info I need.
Thanks for any assistance in advance
-
root@cube-0 ~]# fdisk -l
Disk /dev/hda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 fd Linux raid autodetect
/dev/hda2 14 7297 58508730 fd Linux raid autodetect
Disk /dev/hdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 fd Linux raid autodetect
/dev/hdb2 14 4865 38973690 fd Linux raid autodetect
Disk /dev/md1: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2: 39.9 GB, 39908933632 bytes
2 heads, 4 sectors/track, 9743392 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md2 doesn't contain a valid partition table
Some other info he was able to email me off the system that might help someone to help me.
-
Also if you want to help then help I dont need a lecture on using the search button as I have already done so.
I do not see a lecture, I do see someone asking for help and in return being rude to some who offers help.
Dave
-
Also if you want to help then help I dont need a lecture on using the search button as I have already done so. But keep in mind I am not perfect so I might have overlooked the post with the info I need.
That wasn't a lecture merely a statement suggesting a search, didn't say you was not perfect, no-one is perfect that why we are humans not robots.
Anyway I'm prepared to look past that comment, now can you tell us did he have both drives installed at time of installation? I would say that's why you are seeing when you type fdisk...
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 fd Linux raid autodetect
/dev/hdb2 14 4865 38973690 fd Linux raid autodetect
If he did and he wants to add the additional drive for seperate users partition then reinstall the smeserver with one drive left unpowered, now try fdisk the correct drive make sure you give it the correct id i.e press "t" when you are on fdisk and you will see different options, then maybe have a look at this post http://forums.contribs.org/index.php?topic=31588.0
-
Thanks I will have him try it .......... Sorry it just ticks me off when people ask for help and then thier is always someone that says use the search button.