XenServer硬盘出现错误：There was an SR backend failure

昨晚Webnx机房停电，个人几台服务器出现硬盘不能使用了，VPS全部能开机，这可要人命呀！
从XenCenter发现，硬盘有个红色“X”，即使使用右键 “Repair…” 修复硬盘，出现错误：“The SR failed to complete the operation”

“The SR failed to complete the operation”这错误再次伤了我，太笼统的错误了，Google，度娘，都查了N遍又N遍，没有答案，也无效。没办法了，我只能在命令行里使用命令修复，这样就会有具体错误，使用以下命令

xe pbd-plug uuid=硬盘UUID

注：硬盘UUID，可以自己通过XenCenter查看，选择“硬盘 – General – UUID”就是

也可以用 xe pbd-list 查到UUID

执行后出现以下错误，

[root@localnost ~]# xe pbd—plug uuid=2c8al346—TdTl—e5dl—73l6—55b65l962O§a
There was an SR backend failure.
status: non—zero exit
stdout:
stderr: Traceback (most recent call last):
File “/opt/xens0urce/sm/LVMSR”, line 1447, in ?
SRCommand.run(LVHDSR, DRIVER_INFO)
File “/opt/xens0urce/sm/SRCommand.py”, line 244, in run
sr = driver(cmd, cmd.sr_uuid)
File “/opt/xensource/sm/SR.py”, line 128, in init
self.load(sr uuid) __ –
File “/opt/xens0urce/sm/LVMSR”, line 138, in load
self._undoAllJ0urnals()
File “/opt/xens0urce/sm/LVMSR”, line 627, in _undoAllJ0urnals
self._undoAllInflateJournals()
File “/opt/xens0urce/sm/LVMSR”, line 636, in _undoAllInflateJ0urnals
entries = self.j0urnaler.getAll(lvndutil.JRN_INFLATE)
File “/opt/xensource/sm/journaler.py”, line 63, in getAll
entries = self._getAllEntries()
File “/opt/xensource/sm/journaler.py”, line 35, in _getAllEntries
raise JournalerException(“Bad LV name: %s” % lvName)
journaler.JournalerException: Bad LV name: c99dcba?—755b—425d—b3a7—7ed7589e84cS

我在这发现以下错误，原来是这个UUID有问题

File “/opt/xensource/sm/journaler.py”, line 35, in _getAllEntries
raise JournalerException(“Bad LV name: %s” % lvName)
journaler.JournalerException: Bad LV name: c99dcba?—755b—425d—b3a7—7ed7589e84cS

接下来就是找出有问题的UUID，执行以下命令

lvscan

然后在最下面找到这行错误

Name “VG_Xenstoragr–a7d129e4-45e5-3130-e9d2-fece417336da-leaf_526a60ac-3dc0-4321-9232-a453ac3bb306_46466711-ad30-40f0-baf3-5b3b515fd658” too long
inactive ‘/dev/VG_XenStorage-a7d129e4-45e5-3130-e9d2-fece417336da/leaf_526a60ac-3dc0-4321-9232-a453ac3bb306_46466711-ad30-40f0-baf3-5b3b515fd658’ [4.00 MB] inherit

以上可能错误可能有些丢失了，或者错误，但大致的是这些，
我从这看到这个错误的UUID“46466711-ad30-40f0-baf3-5b3b515fd655 ”，那么我就找出这个UUID属于哪个更硬盘的

可以看到 “name-label” 这个就是有问题的硬盘，发现这个对我不重要，我删删除了它，命令：

lvremove /dev/VG_XenStorage-a7d129e4-45e5-3130-e9d2-fece417336da/leaf_526a60ac-3dc0-4321-9232-a453ac3bb306_46466711-ad30-40f0-baf3-5b3b515fd658

/dev/VG_XenStorage-a7d129e4-45e5-3130-e9d2-fece417336da/VHD-255a1573-ccd7-4f6b-afa7-a9c944f5d7f0: open failed: Read-only file system
Name “VG_XenStorage–a7d129e4–45e5–3130–e9d2–fece417336da-leaf_526a60ac–3dc0–4321–9232–a453ac3bb306_46466711–ad30–40f0–baf3–5b3b515fd658” too long
Name “VG_XenStorage–a7d129e4–45e5–3130–e9d2–fece417336da-leaf_526a60ac–3dc0–4321–9232–a453ac3bb306_46466711–ad30–40f0–baf3–5b3b515fd658” too long
Name “VG_XenStorage–a7d129e4–45e5–3130–e9d2–fece417336da-leaf_526a60ac–3dc0–4321–9232–a453ac3bb306_46466711–ad30–40f0–baf3–5b3b515fd658” too long
Name “VG_XenStorage–a7d129e4–45e5–3130–e9d2–fece417336da-leaf_526a60ac–3dc0–4321–9232–a453ac3bb306_46466711–ad30–40f0–baf3–5b3b515fd658” too long
Logical volume “leaf_526a60ac-3dc0-4321-9232-a453ac3bb306_46466711-ad30-40f0-baf3-5b3b515fd658” successfully removed

删除完毕，因该没问题了，我在把硬盘plug到服务器中：

xe pbd-plug uuid=硬盘UUID

OK，完成！