NOVELL FORUMS

Michael_Fleming · #1 16-Oct-2009, 11:10 AM

I have an OES2 server that is using iSCSI to a SAN and it has an NSS pool and volume created off that. It was all working fine, until after a reboot the NSS pool or volume is no longer found.

If I look in NSSMU the device is found and its got the entire disk as unpartitioned space and when I hit show partitions it displays only a traditional partition not NSS. In Partitions screen that device is not displayed. Pools and volumes screen is completely blank.

In YAST>partitioner the partition type is displayed as Novell Netware, also the EVMS device/types/mounts are no longer there. I've tried activating EMS but no luck. NSS /pools doesn't display anything. When I restart NSS I get the error below. See attached pic for Partitioner.

To me it looks like the entire drive has been wiped so thats why it can't see the pools. But it has only been rebooted so it doesn't make sense.

Any ideas or things to try?

Cheers

Oct 16 14:47:09 data-srv1 nss: NSS started up
Oct 16 14:52:31 data-srv1 nss: Starting Novell Storage Services (NSS)
Oct 16 14:52:31 data-srv1 nss: Start up eDir and LUM
Oct 16 14:53:49 data-srv1 nss: Start up NSS modules
Oct 16 14:53:51 data-srv1 kernel: hda: packet command error: status=0x51 { DriveReady SeekComplete Error }
Oct 16 14:53:51 data-srv1 kernel: hda: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Oct 16 14:53:51 data-srv1 kernel: ide: failed opcode was: unknown
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:52 data-srv1 kernel: device-mapper: dm-linear: Device lookup failed
Oct 16 14:53:52 data-srv1 kernel: device-mapper: error adding target to table
Oct 16 14:53:56 data-srv1 kernel: NSSLOG ==> [Error] comnVol.c[2985]
Oct 16 14:53:56 data-srv1 kernel: Oct 16, 2009 2:53:56 pm NSS<COMN>-4.10a-660:
Oct 16 14:53:56 data-srv1 kernel: Volume DATA not found. Verify Media, Devices, Drivers and power
Oct 16 14:53:56 data-srv1 kernel: to subsystem. Try NSS /Activate=DATA and or type NSS /volumes and
Oct 16 14:53:56 data-srv1 kernel: verify spelling of the volume
Oct 16 14:53:56 data-srv1 kernel: Volume Change State failed. Error = 20801