The lun has now partition map "master boot record"

gus's picture

The lun has now partition map "master boot record"

Postby gus » Thu Nov 28, 2013 11:37 am

We have a XSAN volume running on OSX 10.7.5 with one video LUN and one Meta LUN. For no reason the video LUN changed the partition map to master boot record and the volume is not available any more. 

Does someone have any idea how we can repair it

gus
fully protected
fully protected
 
Posts: 14
Joined: Tue Mar 17, 2009 4:02 am

Top 

Postby abstractrude » Thu Nov 28, 2013 1:44 pm

Sorry to be the bearer of bad news. U probably had a windows client format or partition your LUN. Do you have your fibre channel environment zoned?

abstractrude
Xsan Master
Xsan Master
 
Posts: 936
Joined: Thu Mar 13, 2008 2:32 pm

Top 

Postby gus » Thu Nov 28, 2013 5:28 pm

Yes it's zoned and we don't have any windows client on the fiber. 
The only thing that happened at the same time was that we connect a disk via a USB Dock that was a member of an old Xsan Lun and in that moment we got two windows to initialize since then we lost our Lun. 
Is a way to re activate or recover it ???

gus
fully protected
fully protected
 
Posts: 14
Joined: Tue Mar 17, 2009 4:02 am

Top 

Postby abstractrude » Fri Nov 29, 2013 5:54 pm

he only thing that happened at the same time was that we connect a disk via a USB Dock that was a member of an old Xsan Lun and in that moment we got two windows to initialize since then we lost our Lun.

Please explain this in detail. I understand english may not be your first language but I don't understand this. 

If the LUN was formatted on a windows computer then no you cannot recover it. If the label was simply changed or overwritten you may be able to bring it back using cvlabel. 

Give us the output of cvlabel -L

abstractrude
Xsan Master
Xsan Master
 
Posts: 936
Joined: Thu Mar 13, 2008 2:32 pm

Top 

Postby gus » Mon Dec 02, 2013 12:47 pm

Hi, 
It seems that the label have changed for no reson. Here is the output 

mdc-main:~ root# cvlabel -L 
/dev/rdisk0 [IFT A16F-G2221 347B] MBR Controller 'default', Serial '600D023000671DB2074238083AC4C200', Sector Size 512, Sectors Max 46877915103 (21.8TB) 
/dev/rdisk2 [ T380815AS N 3.BUC] EFI Controller 'default', Serial '5000C50002899162', Sector Size 512, Sectors Max 160068063 (76.3GB) 
/dev/rdisk3 [ T380815AS N 3.BUC] EFI Controller 'default', Serial '5000C50002898F0E', Sector Size 512, Sectors Max 160068063 (76.3GB) 
/dev/rdisk5 [HDS725050KLAT80 K2AO] EFI Controller '512384776144130', Serial '512384776144130L0', Sector Size 512, Sectors Max 976754703 (465.8GB) 
/dev/rdisk1 [IFT A16F-G2221 347B] acfs-VTOC "meta" Controller 'default', Serial '600D023000671DB2074238408844EB00', Sector Size 512, Sectors 976189548 (465.5GB) 
mdc-main:~ root# 

thanks in advance

gus
fully protected
fully protected
 
Posts: 14
Joined: Tue Mar 17, 2009 4:02 am

Top 

Postby gus » Fri Dec 06, 2013 6:57 am

Hi abstractrude, 

Do you believe that we reverse the MBR ? What will be the commands that I will have to give to the server? 

Regards

gus
fully protected
fully protected
 
Posts: 14
Joined: Tue Mar 17, 2009 4:02 am

Top 

Postby JSamuel » Sat Dec 07, 2013 12:27 pm

gus wrote:Do you believe that we reverse the MBR ? What will be the commands that I will have to give to the server?

Once formatted with MBR, you can't get it back, it's not a reversable action. I assume you have backups? :shock:

JSamuel
Xsan Master
Xsan Master
 
Posts: 193
Joined: Wed Jan 05, 2011 10:20 pm
  •  

Top 

Postby ludo » Sun Dec 08, 2013 7:05 pm

Hi, 

The same happened to me. I have no Windows computer on my network and my FC network is zoned. How this MBR just appeared? Don't tell me I've lost the whole volume please... 

Ludo

ludo
partially protected
partially protected
 
Posts: 9
Joined: Fri Feb 15, 2008 10:53 am

Top 

Postby JSamuel » Tue Dec 10, 2013 5:12 am

BootCamp perhaps? Of course DiskUtil can create a MBR partition map, but DiskUtil should not let you touch the partition once it's seen the labelled LUN.

JSamuel
Xsan Master
Xsan Master
 
Posts: 193
Joined: Wed Jan 05, 2011 10:20 pm
  •  

Top 

Postby gus » Tue Dec 10, 2013 5:33 pm

Hi, 

We did not have any system with boot camp running windows. And yes if you have a Xsan Lun disk util can not erase it and I think not windows can erase it you need first to un Lun it and then connect it to windows to change the partition map. 
Two things we have that may cause this 
The first is that we install a data recovery to try to recover a lacie USB external disk. 
And the second is that we attach via USB connection an old disk that was a member of raid 5 volume ( of Eonstor raid chassis storage ) that was a lun from old configuration of Xsan. 

Those maybe are not relevant. 

Is a way to change the partition map without losing any data ? 
Is there a way to recover the data ?

gus
fully protected
fully protected
 
Posts: 14
Joined: Tue Mar 17, 2009 4:02 am

Top 

Postby abstractrude » Wed Dec 11, 2013 2:15 pm

you never got back to me on this. 

Yes it's zoned and we don't have any windows client on the fiber. 
The only thing that happened at the same time was that we connect a disk via a USB Dock that was a member of an old Xsan Lun and in that moment we got two windows to initialize since then we lost our Lun. 
Is a way to re activate or recover it ???
abstractrude
Xsan Master
Xsan Master
 
Posts: 936
Joined: Thu Mar 13, 2008 2:32 pm

Top 

Postby ludo » Thu Dec 12, 2013 7:46 am

With the help of an Apple engineer I got mine back. Solution was to relabel the LUNs and voila! 

The danger here is that the device nodes (/dev/rdiskX) can change at every restart so if you have restarted your controller since you lost your LUN label, the disk number could have changed. You have to go back in your backup xsan config files or in the controller's logs to match the name of missing label and the serial number of the corresponding disk. 

You will find the serial number of the disk by using cvlabel -c. You will also see there the current rdisk number. 

Once you know what label goes with which serial number and current device node you can create a text file like this (replacing MyLabelX with your labels and rdiskX with the right device node): 

MyLabel1 /dev/rdisk3 
MyLabel2 /dev/rdisk5 

Name that text file cvlabel_correct.txt and place it on the desktop. 
Make sure the volume is stopped and then run 

sudo cvlabel ~/Desktop/cvlabel_correct.txt 

Answer yes when asked to change the label, once per LUN. 

Verify that the labels show up as expected (sudo cvlabel -c) 

Try to start the volume. 

It worked for me. I hope it'll work for you. 

Good luck!

ludo
partially protected
partially protected
 
Posts: 9
Joined: Fri Feb 15, 2008 10:53 am

 

Here is our old conversation 

Hi Ludo,

It worked but it seems that the lun it isn't included to any pool or volume. The original pool is there but the lun that I re-labled it is not included. 

Is a way to fix this also ?

Do you thing if we restore the OS in a previous date  with time machine will bring back the volume ?