|
RHEL 4 doesn't see SAN devices after boot
Problem: After rebooting the RHES 4 (64-bit) server, the server halts on the following messages:
fsck.ext3: No such file or directory while trying to open /dev/hds01/lvol1
fsck.ext3: No such file or directory while trying to open /dev/hds01/lvol2
fsck.ext3: No such file or directory while trying to open /dev/hds01/lvol3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
########################################################
How I recover: While in maintenance mode, I edit the fstab, and comment out the 3 filesystems that cannot be seen.
1) reboot server
2) server now comes up (but without the 3 filesystems that are defined on the HDS SAN)
3) run "pvscan"
4) "pvscan" recognizes the filesystems on the SAN
5) "vgchange" I activate the volumegroup that defines the filesystems on the SAN
6) uncomment the 3 filesystems in /etc/fstab
7) remount fstab
8) filesystems are now available
########################################################
Hardware:Dell Poweredge 1850
2 QLogic 2460 HBAs
attached storage: Hitachi 9580
########################################################
Software Configuration:
RHEL 4 (64 bit)
LVM: 2 Volume groups (volgroup1 is defined for the internal
disk) e.g. /home /opt /tmp /var etc.
(volgroup2 is defined for the external Hitachi SAN
storage) e.g. /oracle /dba /dbs
Filesystem format: ext3
########################################################
Asking for assistance here:
So, does anyone have any ideas why these drives (filesystems) are not accessible during the boot process, but they can be recovered once RHEL is completely up?
|