If underlying disks are untouched and visible to the operating system, a simple
should be all the magic required.
system will rescan the devices and import the pool if possible.
Also, it will output errors or numeric zpool identifiers to force the operations and such.
Be sure to read those.
Hope that helps
Regards
Peasant.
These 2 Users Gave Thanks to Peasant For This Post:
Had one additional HW failure and was not able to see any disks from the array using the "format" command. Had to replace the SAS controller, after which I was able to import the pools created, and can now access the files.
You're right. This has been a "very low probability, very high impact" risk, that just has not been mitigated. This was maybe too close of a call.
I'm actually now setting up a repository for the files from the old server. Moving the whole system we have to a standalone client based system, with critical work files stored in a data center version control. Anyways, need the files from the old server...which I now seem to have
With a sun storage array j4200 with a failed drive.
It's got 11 other drive right now running seagate's
ST314655SSUN146G
I'm about to replace that one drive with seagate's ST3146356SS drive.
Do anyone see this as a problem to use non-Sun drives in Sun storage array or mixing the two... (9 Replies)
Hello All:
I am trying to configure a J4200 disk array. I am a newbie.
1. I have installed CAM (Common Array Manager).
2. Upgraded the firmware.
3. Registered the array.
a. As per the user guide I should see a sas-domian which I don't.
b. I did not find instructions on how to setup a... (0 Replies)