Unsolved
This post is more than 5 years old
36 Posts
0
3362
loosing the persistency of mount point in suse linux
I just got a new additional lun from CX..
powermt display dev=all looks good. so;
I run powermt config, powermt save.. and did the formatting and mounting stuff.. All went fine
I edit my /etc/fstab just to make sure it is persistent..
However after I reboot and run again df -ah, the mount point is gone. I double checked my /fstab and it is there..
What could it be?
powermt display dev=all looks good. so;
I run powermt config, powermt save.. and did the formatting and mounting stuff.. All went fine
I edit my /etc/fstab just to make sure it is persistent..
However after I reboot and run again df -ah, the mount point is gone. I double checked my /fstab and it is there..
What could it be?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 6th, 2008 09:00
chikka1
36 Posts
0
January 6th, 2008 10:00
I used the powerpath device... /dev/emcpowerc...
any other clue?
thanks.
chikka1
36 Posts
0
January 6th, 2008 11:00
/dev/cciss/c0d0p1 / ext3 acl,user_xattr 1 1
/dev/cciss/c0d0p2 /boot ext3 acl,user_xattr 1 2
/dev/cciss/c0d0p4 /local ext3 acl,user_xattr 1 2
/dev/cciss/c0d0p3 swap swap pri=42 0 0
/dev/emcpowera /myfs1 ext3 defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0
chikka1
36 Posts
0
January 6th, 2008 11:00
mounting manually is fine. but once rebooted it is gone again.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 6th, 2008 11:00
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 6th, 2008 11:00
chikka1
36 Posts
0
January 6th, 2008 12:00
when i run powermt display dev=all.. after another reboot
I found out I'm missing the clarion ID [server name] and the logical device [lun11]
what I did run again the powermt config and then run powermt save..
when I run the powermt display dev=all this time.. it looks good, I can see my server name and the LUN11.. however after the reboot the information is missing again the server name and logical device [lun 11].
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 6th, 2008 14:00
chikka1
36 Posts
0
January 6th, 2008 23:00
It is confirmed, I'm lossing the powerpath config settings specific to LUN name and server name whenever I did reboot..
Jan 6 21:03:36 myfs-01 /etc/hotplug/block.agent[14779]: try 1 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:37 myfs-01 kernel: emcpowera: unknown partition table
Jan 6 21:03:37 myfs-01 /etc/hotplug/block.agent[14779]: try 2 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:39 myfs-01 /etc/hotplug/block.agent[14779]: try 3 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:40 myfs-01 /etc/hotplug/block.agent[14779]: try 4 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:41 myfs-01 /etc/hotplug/block.agent[14779]: try 5 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:42 myfs-01 /etc/hotplug/block.agent[14779]: new block device /block/emcpowera
Jan 6 21:17:50 myfs-01 kernel: emcpowera: unknown partition table
Jan 6 21:17:50 myfs-01 /etc/hotplug/block.agent[15414]: try 1 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:51 myfs-01 /etc/hotplug/block.agent[15414]: try 2 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:52 myfs-01 /etc/hotplug/block.agent[15414]: try 3 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:53 myfs-01 /etc/hotplug/block.agent[15414]: try 4 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:54 myfs-01 /etc/hotplug/block.agent[15414]: try 5 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:55 myfs-01 /etc/hotplug/block.agent[15414]: new block device /block/emcpowera
Jan 6 22:12:14 myfs-01 kernel: emcpowera: unknown partition table
Jan 6 22:12:14 myfs-01 /etc/hotplug/block.agent[14125]: try 1 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:15 myfs-01 /etc/hotplug/block.agent[14125]: try 2 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:16 myfs-01 /etc/hotplug/block.agent[14125]: try 3 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:17 myfs-01 /etc/hotplug/block.agent[14125]: try 4 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:18 myfs-01 /etc/hotplug/block.agent[14125]: try 5 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:19 myfs-01 /etc/hotplug/block.agent[14125]: new block device /block/emcpowera
myfs-01:~ #
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 7th, 2008 02:00
fdisk -l /dev/emcpowera
chikka1
36 Posts
0
January 7th, 2008 03:00
fdisk -l /dev/emcpowera
Disk /dev/emcpowera: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/emcpowera doesn't contain a valid partition table
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 7th, 2008 04:00
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 7th, 2008 05:00
chikka1
36 Posts
0
January 7th, 2008 05:00
My question is if I do fdisk -l after the fdisk config.. can I just rename the emcpowera1 to emcpowera..before making the file system.. need to maintain our standard naming..
thanks
enterprisestora
1 Message
0
November 6th, 2017 01:00
Hi Chikka,
Could you please share what was the solution for this issue? if you get any?