Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Commodore
Commodore
858 views

NW 6.5 SP8 USB hard drive not found after sys volume crashed

I have an esoteric issue that i need help with please.

We had a NW 6.5 SP8 server that was running fine and I have added a USB hard drive to the machine for backup.  We would map the drive and it ran fine for a year or so as backup. Then the Sys volume hard drive died. We rebuilt if from the ground up, applied just about every patch available but the USB drive volume seems gone. It is not visible for drive repair. Is there an NSS repair option somewhere or some other way to recover it? Is this a verboten concept with NW6.5 sp8?

Thanks!

0 Likes
10 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Please post the results of

m *cad

and

list storage adapters

 

If you like it: like it.
0 Likes
Commodore
Commodore

Thanks. Details below!

m *cad:

UHCIDRV.CAD
Loaded from [C:\NWSERVER\DRIVERS\] on Aug 4, 2020 6:17:15 pm
(Address Space = OS)
Novell Universal Serial Bus UHCI driver
Version 1.07 (Build 5) February 26, 2008
Copyright (C) 2001-2008 Novell, Inc. All Rights Reserved.
EHCIDRV.CAD
Loaded from [C:\NWSERVER\DRIVERS\] on Aug 4, 2020 6:17:16 pm
(Address Space = OS)
Novell Universal Serial Bus EHCI driver
Version 1.05 (Build 4) February 26, 2008
Copyright (C) 2007-2008 Novell, Inc. All Rights Reserved.

 

List storage adapters:

0x00 [V024-A0] Legacy FLOPPY Controller [slot 0]
0x01 [V024-A0-D1:0] Legacy Floppy
0x02 [V100-A100] USB UHCI Controller [slot 0]
0x03 [V100-A101] USB UHCI Controller [slot 0]
0x04 [V100-A102] USB EHCI Controller [slot 0]
0x05 [V100-A102-D2:0] SATA SSD 0701 (USB)
0x07 [V025-A1] Novell ATA/IDE Host Adapter Module [slot 0]
0x08 [V025-A1-D1:0] HL-DT-ST DVD-ROM GDR8163B f/w:0L23
0x09 [V358-A2] LSI_53C1030:10017 [slot 10017]
0x10 [V358-A2-D5:0] SEAGATE ST3300655LC f/w:0003
0x0B [V358-A2-D0:0] SEAGATE ST3300007LC f/w:D704
0x0C [V358-A2-D1:0] COMPAQ BF07288285 f/w:HPB1
0x0D [V358-A2-D2:0] SEAGATE ST3146854LC f/w:0004
0x0E [V358-A2-D3:0] SEAGATE ST318404LC f/w:0005
0x0F [V358-A2-D4:0] SEAGATE ST336607LC f/w:0007
0x0A [V358-A3] LSI_53C1030:10018 [slot 10018]

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Well, at least the drive itself is recognized by the OS.

x04 [V100-A102] USB EHCI Controller [slot 0]
0x05 [V100-A102-D2:0] SATA SSD 0701 (USB)

If you've really rebuilt the box from scratch pool and volume likely just don't get auto-activated / mounted.

You can check this e.g. from within "nssmu". And you can also activate and mount stuff from there. This usually has to be done just once, i.e. once you've done this manually it will likely come up "on its own" after reboots.

If you like it: like it.
0 Likes
Commodore
Commodore

Thanks. I tried that and it says there is no volume on this device. Is there an NSS rebuild too like Vrepair?

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

You can, of course, rebuild a pool. But that would require the OS to recognize the pool at all. Do you see a partition on this device from within nssmu? If, so does the partition show a pool?

 

If you like it: like it.
0 Likes
Commodore
Commodore

It is listed in devices as shown below: But when I hit enter, it says NO Partitions found on this device.

Devices Device Information

0x10 Name: [V100-A102-D2:0] SATA SSD 070
0x5
0xB ModuleID: 100
0xC Adapter: 102
0xD Device: 2:0
0xE
0xF Capacity: 447.13 GB
Partitioned Space: 0 KB
Unpartitioned Space: 0 KB

Sharable for Clustering: No

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

This is merely an "uninitialized" state. From the NetWare perspective there's not much you could do about that (other than checking with a disk editor such as Portlock Storage Manager). You could e.g.

- try with the device attached to another USB port

- boot the server with a Linux Live CD (or e.g. gparted live) and check for a partition to rule out an OS / driver issue

- attach the device to another box (running Linux) and check with gparted from there

If you don't need the data which did reside on the device you can, of course, simply initialize it and create new pools and volumes.

While it's sometimes  just about a single byte in the partition record, this kind of recovery would likely be out of the scope of this forum. Other than that, there are professional recovery services which might help.

 

 

If you like it: like it.
0 Likes
Commodore
Commodore

Interesting. Does netware do something unusual like code the USB port number in the boot record of a drive? I can try connecting to another USB port on the machine. Thanks.

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

No. NetWare and OES are pretty tolerant. If there's a valid partition on a device you could attach it to a brandnew hardware running let's say OES2018 and mount it there.

 

If you like it: like it.
0 Likes
Commodore
Commodore

Thanks. Then I presume that when the sys volume died that it tool the backup SSD USB drive with it in some manor. I had portlock around here somewhere from a long time ago!  It was a backup so it is not critical but I think that there may be some interplay being an SSD..so maybe a HD based drive is preferable.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.