*.vmdk und flat.vmdk verloren
Verfasst: 13.07.2011, 17:26
Hallo Kollegen,
leider hat mein esxi 4.1 nach einem absturtz einige platten verloren.
Alle *.vmdk sind verschwunden.
Ich weiß backup usw.
Leider giebt es keins.
Frage: Gibes eine möglichkeit die Platten neu zu initialisieren anhand der log infos.
Grundsätzlich könnte das doch möglich sein.
Apr 23 17:08:57.312: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' persistent R[]
Apr 23 17:08:57.428: vmx| DISKLIB-VMFS : "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455-flat.vmdk" : open successful (10) size = 53687451648, hd = 7465599. Type 3
Apr 23 17:08:57.428: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455-flat.vmdk" (0xa)
Apr 23 17:08:57.428: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' (0xa): vmfs, 104858304 sectors / 50 GB.
Apr 23 17:08:57.429: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.429: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.430: vmx| DISK: Disk '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' has UUID '60 00 c2 92 6a 50 94 cc-f8 cf 7c aa b9 d3 1a 84'
Apr 23 17:08:57.430: vmx| DISK: OPEN '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' Geo (6527/255/63) BIOS Geo (6527/255/63)
Apr 23 17:08:57.434: vmx| DISK: OPEN scsi0:1 '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' persistent R[]
Apr 23 17:08:57.453: vmx| DISKLIB-VMFS : "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1-flat.vmdk" : open successful (10) size = 536881524736, hd = 5253760. Type 3
Apr 23 17:08:57.453: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455_1-flat.vmdk" (0xa)
Apr 23 17:08:57.453: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' (0xa): vmfs, 1048596728 sectors / 500 GB.
Apr 23 17:08:57.453: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.453: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.454: vmx| DISK: Disk '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' has UUID '60 00 c2 94 f8 96 21 af-a2 0d 69 11 52 1b 23 9a'
Apr 23 17:08:57.454: vmx| DISK: OPEN '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' Geo (65272/255/63) BIOS Geo (65272/255/63)
Apr 23 17:08:57.460: vmx| DISK: OPEN scsi0:2 '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' persistent R[]
Apr 23 17:08:57.465: vmx| DISKLIB-VMFS : "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2-flat.vmdk" : open successful (10) size = 107382079488, hd = 5745281. Type 3
Apr 23 17:08:57.465: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455_2-flat.vmdk" (0xa)
Apr 23 17:08:57.465: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' (0xa): vmfs, 209730624 sectors / 100 GB.
Apr 23 17:08:57.465: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.466: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.466: vmx| DISK: Disk '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' has UUID '60 00 c2 98 b9 f9 c5 c2-68 5e 1c 37 77 f1 26 06'
Apr 23 17:08:57.466: vmx| DISK: OPEN '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' Geo (13055/255/63) BIOS Geo (13055/255/63)
Apr 23 17:08:57.471: vmx| DISK: OPEN scsi0:3 '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' persistent R[]
Apr 23 17:08:57.492: vmx| DISKLIB-VMFS : "/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3-flat.vmdk" : open successful (10) size = 214748364800, hd = 4582018. Type 3
Apr 23 17:08:57.492: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455_3-flat.vmdk" (0xa)
Apr 23 17:08:57.492: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' (0xa): vmfs, 419430400 sectors / 200 GB.
Apr 23 17:08:57.492: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.492: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.493: vmx| DISK: Disk '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' has UUID '60 00 c2 9f 97 ff a7 3a-e0 55 01 b1 d1 61 64 36'
Apr 23 17:08:57.493: vmx| DISK: OPEN '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' Geo (26108/255/63) BIOS Geo (0/0/0)
Apr 23 17:08:57.498: vmx| TimeTracker host to guest rate conversion 693334924435485 @ 2393999000Hz -> 693334924435485 @ 2393999000Hz
Apr 23 17:08:57.498: vmx| TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + 0
B
leider hat mein esxi 4.1 nach einem absturtz einige platten verloren.
Alle *.vmdk sind verschwunden.
Ich weiß backup usw.
Leider giebt es keins.
Frage: Gibes eine möglichkeit die Platten neu zu initialisieren anhand der log infos.
Grundsätzlich könnte das doch möglich sein.
Apr 23 17:08:57.312: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' persistent R[]
Apr 23 17:08:57.428: vmx| DISKLIB-VMFS : "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455-flat.vmdk" : open successful (10) size = 53687451648, hd = 7465599. Type 3
Apr 23 17:08:57.428: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455-flat.vmdk" (0xa)
Apr 23 17:08:57.428: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' (0xa): vmfs, 104858304 sectors / 50 GB.
Apr 23 17:08:57.429: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.429: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.430: vmx| DISK: Disk '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' has UUID '60 00 c2 92 6a 50 94 cc-f8 cf 7c aa b9 d3 1a 84'
Apr 23 17:08:57.430: vmx| DISK: OPEN '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455.vmdk' Geo (6527/255/63) BIOS Geo (6527/255/63)
Apr 23 17:08:57.434: vmx| DISK: OPEN scsi0:1 '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' persistent R[]
Apr 23 17:08:57.453: vmx| DISKLIB-VMFS : "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1-flat.vmdk" : open successful (10) size = 536881524736, hd = 5253760. Type 3
Apr 23 17:08:57.453: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455_1-flat.vmdk" (0xa)
Apr 23 17:08:57.453: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' (0xa): vmfs, 1048596728 sectors / 500 GB.
Apr 23 17:08:57.453: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.453: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.454: vmx| DISK: Disk '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' has UUID '60 00 c2 94 f8 96 21 af-a2 0d 69 11 52 1b 23 9a'
Apr 23 17:08:57.454: vmx| DISK: OPEN '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_1.vmdk' Geo (65272/255/63) BIOS Geo (65272/255/63)
Apr 23 17:08:57.460: vmx| DISK: OPEN scsi0:2 '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' persistent R[]
Apr 23 17:08:57.465: vmx| DISKLIB-VMFS : "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2-flat.vmdk" : open successful (10) size = 107382079488, hd = 5745281. Type 3
Apr 23 17:08:57.465: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455_2-flat.vmdk" (0xa)
Apr 23 17:08:57.465: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' (0xa): vmfs, 209730624 sectors / 100 GB.
Apr 23 17:08:57.465: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.466: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.466: vmx| DISK: Disk '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' has UUID '60 00 c2 98 b9 f9 c5 c2-68 5e 1c 37 77 f1 26 06'
Apr 23 17:08:57.466: vmx| DISK: OPEN '/vmfs/volumes/4bb9b5e5-43284e7d-426e-001b2120e555/ORA1455/ORA1455_2.vmdk' Geo (13055/255/63) BIOS Geo (13055/255/63)
Apr 23 17:08:57.471: vmx| DISK: OPEN scsi0:3 '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' persistent R[]
Apr 23 17:08:57.492: vmx| DISKLIB-VMFS : "/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3-flat.vmdk" : open successful (10) size = 214748364800, hd = 4582018. Type 3
Apr 23 17:08:57.492: vmx| DISKLIB-DSCPTR: Opened [0]: "ORA1455_3-flat.vmdk" (0xa)
Apr 23 17:08:57.492: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' (0xa): vmfs, 419430400 sectors / 200 GB.
Apr 23 17:08:57.492: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk" (flags 0xa, type vmfs).
Apr 23 17:08:57.492: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Apr 23 17:08:57.493: vmx| DISK: Disk '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' has UUID '60 00 c2 9f 97 ff a7 3a-e0 55 01 b1 d1 61 64 36'
Apr 23 17:08:57.493: vmx| DISK: OPEN '/vmfs/volumes/4ba0dd5b-501850c5-3060-001b2120e555/ORA1455/ORA1455_3.vmdk' Geo (26108/255/63) BIOS Geo (0/0/0)
Apr 23 17:08:57.498: vmx| TimeTracker host to guest rate conversion 693334924435485 @ 2393999000Hz -> 693334924435485 @ 2393999000Hz
Apr 23 17:08:57.498: vmx| TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + 0
B