Results 1 to 1 of 1
Hi,
I installed RHEL 5.5 using the "linux mpath" option on a SAN. At that time it had two disks (volume).
I added the device WWID in the blacklist_exceptions list ...
- 08-04-2010 #1Just Joined!
- Join Date
- Aug 2010
- Posts
- 1
mpath not found at boot (RHEL)
Hi,
I installed RHEL 5.5 using the "linux mpath" option on a SAN. At that time it had two disks (volume).
I added the device WWID in the blacklist_exceptions list in /etc/multipath.conf
I added and formatted it using the following:
*fdisk /dev/sdc: new partition that uses all space, and offset to 64 (aligning).
*/sbin/mkfs.ext3 /dev/sdc
I added it using the following command to mpath:
*/sbin/multipath
Herafter I can add it with the name /dev/mpath2p1.
The following step was to add it to the /etc/fstab filen, with the following line:
/dev/mapper/mpath2p1 /extradisk ext3 defaults 1 2
This line is nearly the same as the other partitions (besides the name => mpath2p1).
At reboot, after load of the kernel ("Red Hat nash version ...") I get:
fsck.ext3: No such file or directory while trying to open /dev/mapper/mpath2p1
/dev/mapper/mpath2p1:
The superblock could not be read or does not describe a correct ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with alternative superblock: e2fsck -b 8193 <device>
***An error occured during the file system check.
***Dropping you to a shell: the system will reboot
....
(1)When I login, I cannot see /dev/mapper/mpath2 and mpath2p1. Probably I forgot some mpath configuration?
(2)In this rescue shell, can I make the partitions writeable? Otherwise I must use gparted to set the added line in /etc/fstab as comment.
Thanks!


Reply With Quote