跑在esxi 6.5平台上的虚拟机，一个50m的vmdk启动盘，是jun的6.x的1.02b loader，另有两个RDM的数据盘做带集。

之前是6.1.5 u几忘了，从最早的6.1一路升上来没出过事，大意了，没在测试机上试过直接就升了，结果出事了。

现在的状态是，看console是正常启动的画面，但是ping不到，也没有去路由拿DHCP，SA搜不到。

把那个50m的vmdk换成新的，能起来被SA发现，状态是发现可恢复的数据盘。可是SA/Web上选恢复，重启之后回到上述状态。

我猜数据是好的，就是启动不知道卡哪了，求破。

应该是升级后驱动不支持你的网卡原因，我的rtl8111F升级1.02b loader也连接不上，用1.02loader重新安装才成功。

50MB的vmdk需要改成是scsi类型的。

yc_dfc 发表于 2018-4-16 10:24
应该是升级后驱动不支持你的网卡原因，我的rtl8111F升级1.02b loader也连接不上，用1.02loader重新安装才成 ...

感谢提醒，我去试试

vmmzz 发表于 2018-4-16 10:31
50MB的vmdk需要改成是scsi类型的。

一直都是SCSI的，没变过

想办法导出了 console，各位大神给看看：

1. START /linuxrc.syno
   
2. Insert Marvell 1475 SATA controller driver
   
3. Insert basic USB modules...
   
4. :: Loading module usb-common ... [  OK  ]
   
5. :: Loading module usbcore ... [  OK  ]
   
6. :: Loading module ehci-hcd ... [  OK  ]
   
7. :: Loading module ehci-pci ... [  OK  ]
   
8. :: Loading module ohci-hcd ... [  OK  ]
   
9. :: Loading module uhci-hcd ... [  OK  ]
   
10. :: Loading module xhci-hcd ... [  OK  ]
    
11. :: Loading module usb-storage ... [  OK  ]
    
12. :: Loading module BusLogic ... [  OK  ]
    
13. :: Loading module vmw_pvscsi ... [  OK  ]
    
14. :: Loading module megaraid_mm ... [  OK  ]
    
15. :: Loading module megaraid_mbox ... [  OK  ]
    
16. :: Loading module megaraid ... [  OK  ]
    
17. :: Loading module scsi_transport_spi ... [  OK  ]
    
18. :: Loading module mptbase ... [  OK  ]
    
19. :: Loading module mptscsih ... [  OK  ]
    
20. :: Loading module mptspi ... [  OK  ]
    
21. :: Loading module mptsas ... [  OK  ]
    
22. :: Loading module mptctl ... [  OK  ]
    
23. :: Loading module ata_piix[    3.204068] ata7: Read current link speed fail, retry 1
    
24. [    3.210037] ata7: Read current link speed fail, retry 2
    
25. [    3.216023] ata7: Read current link speed fail, retry 3
    
26. [    3.223022] ata8: Read current link speed fail, retry 1
    
27. [    3.229035] ata8: Read current link speed fail, retry 2
    
28. [    3.235031] ata8: Read current link speed fail, retry 3
    
29. [    3.235790] ata8: Issued IDENTIFY to non-existent device ?!
    
30. [    5.392071] ata8: Read current link speed fail, retry 1
    
31. [    5.399020] ata8: Read current link speed fail, retry 2
    
32. [    5.405023] ata8: Read current link speed fail, retry 3
    
33. [    5.406197] ata8: Issued IDENTIFY to non-existent device ?!
    
34. [    7.562065] ata8: Read current link speed fail, retry 1
    
35. [    7.568066] ata8: Read current link speed fail, retry 2
    
36. [    7.574062] ata8: Read current link speed fail, retry 3
    
37. [    7.574783] ata8: Issued IDENTIFY to non-existent device ?!
    
38. [    9.731066] ata8: Read current link speed fail, retry 1
    
39. [    9.738054] ata8: Read current link speed fail, retry 2
    
40. [    9.745023] ata8: Read current link speed fail, retry 3
    
41. ... [  OK  ]
    
42. :: Loading module megaraid_sas ... [  OK  ]
    
43. :: Loading module mpt2sas ... [  OK  ]
    
44. :: Loading module mpt3sas ... [  OK  ]
    
45. Insert net driver(Mindspeed only)...
    
46. Starting /usr/syno/bin/synocfgen...
    
47. /usr/syno/bin/synocfgen returns 0
    
48. All disk ready or timeout execeed
    
49. [    9.786499] md: invalid raid superblock magic on sdb3
    
50. [    9.788008] md: invalid raid superblock magic on sdc3
    
51. Partition Version=8
    
52. /sbin/e2fsck exists, checking /dev/md0...
    
53. /sbin/e2fsck -pvf returns 0
    
54. Mounting /dev/md0 /tmpRoot
    
55. ------------upgrade
    
56. Begin upgrade procedure
    
57. No upgrade file exists
    
58. End upgrade procedure
    
59. ============upgrade
    
60. Wait 2 seconds for synology manufactory device
    
61. Mon Apr 16 09:10:51 UTC 2018
    
62. /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0
    
63. none /sys/kernel/debug debugfs rw,relatime 0 0
    
64. sys /sys sysfs rw,relatime 0 0
    
65. none /dev devtmpfs rw,relatime,size=2022272k,nr_inodes=505568,mode=755 0 0
    
66. proc /proc proc rw,relatime 0 0
    
67. linuxrc.syno executed successfully.
    
68. Post init
    
69. 
    
70. [   16.448571] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
71. [   16.484636] init: Caught abort, core dumped
    
72. [   16.486540] init: Error while reading from descriptor: Broken pipe
    
73. [   16.486793] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
74. [   16.491035] init: Caught abort, core dumped
    
75. [   16.492707] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
76. [   16.493355] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
77. [   16.494398] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
78. [   16.495061] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
79. [   16.497205] init: Caught abort, core dumped
    
80. [   16.499031] init: Caught abort, core dumped
    
81. [   16.500198] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
82. [   16.501480] init: Caught abort, core dumped
    
83. [   16.502762] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
84. [   16.505136] init: Caught abort, core dumped
    
85. [   16.506800] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
86. [   16.510823] init: Caught abort, core dumped
    
87. [   16.510942] init: Caught abort, core dumped
    
88. [   16.513281] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    
89. [   16.514866] init: Caught abort, core dumped
    
90. [   16.521100] init: Caught abort, core dumped
    

复制代码

看样子够呛啊，呜呜呜

1. ==================== start udevd ====================
   
2. ===== trigger device plug event =====
   
3. [   63.471977] md/raid0:md2: too few disks (1 of 2) - aborting!
   
4. [   63.473944] Buffer I/O error on device md2, logical block 0
   
5. [   63.475728] Buffer I/O error on device md2, logical block 0
   
6. [   63.477500] Buffer I/O error on device md2, logical block 0
   
7. [   63.479272] Buffer I/O error on device md2, logical block 0
   
8. [   63.481120] Buffer I/O error on device md2, logical block in range 365068288 + 0-2(12)
   
9. [   63.483580] Buffer I/O error on device md2, logical block 365070928
   
10. [   63.863272] md/raid0:md2: too few disks (1 of 2) - aborting!
    
11. [   63.865206] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
12. [   63.867469] Buffer I/O error on device md2, logical block 0
    
13. [   63.869218] Buffer I/O error on device md2, logical block 0
    
14. [   63.870961] Buffer I/O error on device md2, logical block 0
    
15. [   64.883004] EXT3-fs (md2): error: unable to read superblock
    
16. [   64.884999] EXT2-fs (md2): error: unable to read superblock
    
17. [   64.886837] EXT4-fs (md2): unable to read superblock
    
18. [   64.888551] hfsplus: unable to parse mount options
    
19. 
    
20. vDSM login: [   73.809719] Buffer I/O error on device md2, logical block 0
    
21. [   73.811610] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
22. [   73.813878] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
23. [   73.816159] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
24. [   73.818439] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
25. [   74.194993] Buffer I/O error on device md2, logical block 0
    
26. [   74.196835] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
27. [   74.199097] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
28. [   74.201355] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
29. [   74.203607] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
30. System is going to poweroff.
    
31. [  384.083557] Buffer I/O error on device md2, logical block 0
    
32. [  384.085418] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
33. [  384.088050] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
34. [  384.090492] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
35. [  384.093130] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
36. [  384.252855] Buffer I/O error on device md2, logical block 0
    
37. [  384.254710] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
38. [  384.256966] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
39. [  384.259242] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    
40. [  384.261490] Buffer I/O error on device md2, logical block in range 0 + 0-2(12)
    

复制代码

安全的处理办法：新建一个虚拟机装好群晖，把老群晖的盘添加到新群晖中，把数据备份出来或者直接就用新群晖！

vmmzz 发表于 2018-4-17 11:01
安全的处理办法：新建一个虚拟机装好群晖，把老群晖的盘添加到新群晖中，把数据备份出来或者直接就用新群晖 ...

试过了不行。新建一个虚拟机把老盘挂进去其实是和用新的IMG拉起来，然后需要恢复是一样的。

另外说一下搞定了，忘啦在哪里看到的：把两个数据盘挂到Win或者WinPE下，用磁盘管理软件格式化掉两个2G的系统区，大的数据区不要动。再挂回去，SA提示群晖系统丢失，需要重安装，用SA安装即可。

helleon 发表于 2018-4-17 15:08
试过了不行。新建一个虚拟机把老盘挂进去其实是和用新的IMG拉起来，然后需要恢复是一样的。

另外说一 ...

嗯，你的解决办法是最后一招了，再不行就没办法了，另外，建议虚机里尽量格式化成ext4文件系统，以后有问题好处理！