Hi all,

I need some help mounting my raid array on CentOS 5.2 samba server. Here are my hardware specs:

Motherboard: Tyan S2510 LE dual PIII
CPU's: Intel PIII 850ghz socket 370
Memory: 4 gig Crucial 133 ECC SDRAM
OS: 2 x'x IBM Travelstar 6.4 gig 2.5 hard drives, (low heat/noise)
Storage: 4 x's Seagate 500 gig IDE 7200 rpm
RAID controller: 3Ware 7500-12 controller, (RAID 5) (66 mhz PCI bus)
NIC: 3COM 3C996B-T gigabit NIC, (66 mhz PCI bus)

I have the 2 IBM's set as RAID 1, (mirror), and the 4 Seagates as RAID 5, (1.5 TB) I have installed the OS with minor problems, (motherboard doesn't like the 2.6.18-128.1.14.el5 kernel, removed it from my grub.conf).

My problem is mounting the RAID array. I have done the following:

formated with fdisk;

fdisk /dev/sdb

Then formated with the following command;

mkfs.ext3 -m 0 /dev/sdb

The hard drive was formatted with the ext3 files system, but I have mounted it as an ext2 file system as I don't want 'journaling' to occur.

I then edited my /ect/fstab like this:

/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/sdb /home ext2 defaults,noatime 0 0


Then: mount -a

When I go into my "home" directory and type ls, I get the following:

[root@hydra home]# ls -l
total 24
drwx------ 2 zog zog 4096 Jun 23 15:50 zog
lrwxrwxrwx 1 root root 6 Jun 23 15:46 home -> /home/
drwxrwxrwx 2 root root 16384 Jun 23 15:34 lost+found
drwxr-xr-x 2 root root 4096 Jun 23 17:18 tmp
[
Can anyone explain to me why my home directory is showing under home? (I.e. what did I do wrong?).

Thanks

zog

Partitioning a whole disk should result in one or more partitions.
If there's just one primary it should be called /dev/sdb1.
That's the one to mkfs and mount.


...meaning "/home" (still?) resides on "/" (aka LV LogVol00)?

Hi unSpawn,

I tried what you suggested, but got the following error:

[root@hydra ~]# mkfs.ext3 -m 0 /dev/sdb1
mke2fs 1.39 (29-May-2006)
/dev/sdb1 is apparently in use by the system; will not make a filesystem here!

So I deleted the partion and recreated it with the following:

[root@hydra ~]# fdisk /dev/sdb

The number of cylinders for this disk is set to 1430813.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1430813, default 1): 1
Last cylinder or +size or +sizeM or +sizeK (1-1430813, default 1430813): 1430813

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 0: Success.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.

However, I am still getting this error:

[root@hydra ~]# mkfs.ext3 -m 0 /dev/sdb1
mke2fs 1.39 (29-May-2006)
/dev/sdb1 is apparently in use by the system; will not make a filesystem here!

Do you have any suggestions to what I am doing wrong?

Thanks

zog

What does 'sfdisk -l' say?

Hi unSpawn

Here is the out put of sfdisk -l


[root@hydra /]# sfdisk -l

Disk /dev/sda: 4644 cylinders, 64 heads, 32 sectors/track
Warning: The partition table looks like it was made
for C/H/S=*/255/63 (instead of 4644/64/32).
For this listing I'll assume that geometry.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 12 13- 104391 83 Linux
/dev/sda2 13 591 579 4650817+ 8e Linux LVM
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty

Disk /dev/sdb: 1430813 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 1430812 1430813- 1465152496 83 Linux
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
[root@hydra /]#


zog

Neat. See if you can edit your fstab line to read "/dev/sdb1 /home ext2 defaults,noatime 0 0" and reboot.

Ok, did as you suggested, on reboot I had an the following error:

Jun 24 18:27:39 hydra kernel: EXT3 FS on dm-0, internal journal
Jun 24 18:27:39 hydra kernel: kjournald starting. Commit interval 5 seconds
Jun 24 18:27:39 hydra kernel: EXT3 FS on sda1, internal journal
Jun 24 18:27:39 hydra kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 24 18:27:39 hydra kernel: VFS: Can't find an ext2 filesystem on dev sdb1.
Jun 24 18:27:39 hydra kernel: Adding 2031608k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1 across:2031608k

then I did the following:

[root@hydra ~]# mkfs.ext3 -m 0 /dev/sdb1
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
183156736 inodes, 366288124 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
11179 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 32 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@hydra ~]# mount -a


Rebooted again, no errors, however, I am not sure if my drive is mounted in the right place. When I type df -h:

[root@hydra ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2.4G 1.2G 1.2G 51% /
/dev/sda1 99M 18M 77M 19% /boot
tmpfs 1.5G 0 1.5G 0% /dev/shm
/dev/sdb1 1.4T 198M 1.4T 1% /home

So it seems right, however I get the following out put with du -hs:

[root@hydra ~]# du -hs /home/
20K /home/

Is there a simple way to check if the drive is mounted in the right place?

I have also included the output of sfdisk -l:

[root@hydra home]# sfdisk -l

Disk /dev/sda: 4644 cylinders, 64 heads, 32 sectors/track
Warning: The partition table looks like it was made
for C/H/S=*/255/63 (instead of 4644/64/32).
For this listing I'll assume that geometry.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 12 13- 104391 83 Linux
/dev/sda2 13 591 579 4650817+ 8e Linux LVM
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty

Disk /dev/sdb: 1430813 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 1430812 1430813- 1465152496 83 Linux
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty

thanks

zog

Looks OK to me. Df: report free disk space, du: estimate file space usage.

Hey unSpawn,

Yes, just realized my error by doing a Google search on it.

I really do appreciate all of your assistance.

Take care

zog

You're welcome. Have fun!