- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Does Creating an Array Erase Disks???
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2006 11:23 PM
тАО07-16-2006 11:23 PM
Solutiondid a quick test for you on Windows 2003:
- created raid0 array with one logical drive on one physicall disk
- formatted NTFS, copied 6 GByte files on it
- removed disk from server
- hot inserted it in another running server
- started ACU utility/rescanned bus
- saw one unconfigured disk
- created raid0 array with one logical drive on this disk
- started disk manager and saw this disk as "Healthy" but no drive letter.
- assigned drive letter
- all data was visible and chkdsk ran without any error, could copy new files to
driveletter, all looks ok.
....
I don't consider this as a supported method but at least on Windows it seems to work just fine without downtime.
HTH
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2006 11:25 PM
тАО07-16-2006 11:25 PM
Re: Does Creating an Array Erase Disks???
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 12:19 AM
тАО07-17-2006 12:19 AM
Re: Does Creating an Array Erase Disks???
Thanks for trying that for me. That is certainly promising and more as I'd expect. I was just unsure as to whether the array/logical volume creation was would be more destructive of the disk than that.
As you say, no guarantees, but certainly more hopeful...
I'd guess that the controller sets aside a small area of the disk for the controller info and this is the area that gets edited/wiped when moving drives around from machine to machine.
I've managed to organise a reboot of this machine in a couple of days, so I'll probably leave it until then and give it the kick. If I'm feeling brave I'll try the true hot-swap method. Think I'll test my backup between now and the reboot :)
Thanks for the info.
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 06:25 AM
тАО07-17-2006 06:25 AM
Re: Does Creating an Array Erase Disks???
> area of the disk for the controller info
Yes, that is why you can move complete disk drive arrays - because the controller can find out which disks belong together.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 08:28 PM
тАО07-17-2006 08:28 PM
Re: Does Creating an Array Erase Disks???
And indeed why it should be fine to move drives about without fear of data loss. If it only edits the array config part of the drive, surely the data on the disk(s) should be left intact.
Obviously this wouldn't be feasible in certain instances (moving part of a stripe or RAID5 about would obviously fail) however mirrors and stripes of single disks *should* be unaffected.
Or am I asking too much again :)
My reboot happens tomorrow, will post any results, good or bad...
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2006 04:23 AM
тАО07-20-2006 04:23 AM
Re: Does Creating an Array Erase Disks???
Thanks for all your advice so far.
Basically, as mentioned I ended up going with the *insert drive, reboot, let the controller do its magic* method and I am glad to report it worked perfectly.
The controller did its job and sorted things and my host OS (FC5 x86_64, I decided to chuck it in a DL380 G4 x86_64 instead) displayed it as usual. I have since created a Xen VM with the drive and it is now back up and happily compiling something as we speak (once I did a setarch fudge of bash to make logons/apps believe it is an x86_32 machine).
Anyway, just reporting it worked as I'd hoped. As I'd organised a reboot there was no need to try the *live* method. Another time when I have some test data to try it on.
Thanks again
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2006 04:24 AM
тАО07-20-2006 04:24 AM
Re: Does Creating an Array Erase Disks???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2007 03:58 AM
тАО02-22-2007 03:58 AM
Re: Does Creating an Array Erase Disks???
My setup is:
Server A: ML370G3, SmartArray 642, 2x72gb raid 1 (Vol A1), 4x72gb raid 0+1 (Vol A2)
Server B: ML370G3, SmartArray 641, 2x72gb raid 1 (Vol B1), 2x72gb raid 1 (Vol B2)
The OS is Linux on both.
The operation I'd like to perform is moving Vol A2 to Server B, and moving Vol B2 to Server A, while keeping both Vol A1 and Vol B1 in place.
I always preserved the order of the disks in each operation, same disk in same slot, and I've always turned off the servers before moving disks. All operations of creation/deletion of volumes have been made from the SmartArray console (F8 at boot).
This is what I've done:
- take out Vol A2, took out Vol B2
- put Vol B2 into Server A, turned on Server A
- Server A didn't recognize the array on Vol B2
- take out Vol B2, deleted both arrays from Server A's controller, created array on Vol A1 disks (same settings) -> lost Vol A1 (I assume)
- put Vol A2 into Server B, Server B didn't recognize Vol A2 disks
- take out Vol A2, put Vol B2 back into Server B, Server B complained about a possible hardware failure, I told it to go on and now works fine (it just needed some reboots to go out of degraded mode, check filesystems etc.)
- put Vol A2 back into Server A, it recognized the array (still unable to boot, so I can't tell if there still are data on it, because Vol A1 was the OS partition).
Now the questions:
- can I assume that Vol A2 still has data on it?
- is there any way to accomplish my original objectives (moving Vol A2 to Server B and Vol B2 to Server A)? What should I do?
Next step I'd do would be the following:
- take out Vol B2
- delete the raid configuration for Vol B2 on Server B
- put Vol A2 into Server B
- pray for the autodetection to work fine
Is this the right thing to do?
Optionally I'd like to restore content on Vol A1, but that's not vital, since I can clone Server A from Server B quite easily (and Server A is going to be reinstalled anyway).
Thank you in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2007 08:36 AM
тАО02-22-2007 08:36 AM
Re: Does Creating an Array Erase Disks???
Here's the way I would try it - one change at a time.
Take B2 out and put it in Server A. Leaving the rest of Server A in it's original configuration. Only change is a new B2.
Then when all is well with Server A, remove A2 and move it to Server B. Follow the same steps.
The SA firmware should see the new disks and add them in using the configuration already on the disks.
- « Previous
-
- 1
- 2
- Next »