1. 服务器/VPS/主机用户Telegram电报群: https://t.me/openos
    黑群晖 Synology Telegram电报群: https://t.me/nasfan
    排除公告

升级6.1.6-15266 U1失败,求救

本帖由 helleon2018-04-15 发布。版面名称:群晖 Synology DSM

  1. helleon

    helleon New Member

    注册:
    2018-04-14
    帖子:
    10
    跑在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上选恢复,重启之后回到上述状态。

    我猜数据是好的,就是启动不知道卡哪了,求破。
     
  2. henryshmak

    henryshmak New Member

    注册:
    2017-07-13
    帖子:
    10
    论坛下载中心有DSM 6.1.6-15266的引导文件(loader),用那个试试看。
     
  3. helleon

    helleon New Member

    注册:
    2018-04-14
    帖子:
    10
    感谢,我去试试,另外我导出了console,求大神帮看这是咋了:
    代码:
    START /linuxrc.syno
    Insert Marvell 1475 SATA controller driver
    Insert basic USB modules...
    :: Loading module usb-common ... [  OK  ]
    :: Loading module usbcore ... [  OK  ]
    :: Loading module ehci-hcd ... [  OK  ]
    :: Loading module ehci-pci ... [  OK  ]
    :: Loading module ohci-hcd ... [  OK  ]
    :: Loading module uhci-hcd ... [  OK  ]
    :: Loading module xhci-hcd ... [  OK  ]
    :: Loading module usb-storage ... [  OK  ]
    :: Loading module BusLogic ... [  OK  ]
    :: Loading module vmw_pvscsi ... [  OK  ]
    :: Loading module megaraid_mm ... [  OK  ]
    :: Loading module megaraid_mbox ... [  OK  ]
    :: Loading module megaraid ... [  OK  ]
    :: Loading module scsi_transport_spi ... [  OK  ]
    :: Loading module mptbase ... [  OK  ]
    :: Loading module mptscsih ... [  OK  ]
    :: Loading module mptspi ... [  OK  ]
    :: Loading module mptsas ... [  OK  ]
    :: Loading module mptctl ... [  OK  ]
    :: Loading module ata_piix[    3.204068] ata7: Read current link speed fail, retry 1
    [    3.210037] ata7: Read current link speed fail, retry 2
    [    3.216023] ata7: Read current link speed fail, retry 3
    [    3.223022] ata8: Read current link speed fail, retry 1
    [    3.229035] ata8: Read current link speed fail, retry 2
    [    3.235031] ata8: Read current link speed fail, retry 3
    [    3.235790] ata8: Issued IDENTIFY to non-existent device ?!
    [    5.392071] ata8: Read current link speed fail, retry 1
    [    5.399020] ata8: Read current link speed fail, retry 2
    [    5.405023] ata8: Read current link speed fail, retry 3
    [    5.406197] ata8: Issued IDENTIFY to non-existent device ?!
    [    7.562065] ata8: Read current link speed fail, retry 1
    [    7.568066] ata8: Read current link speed fail, retry 2
    [    7.574062] ata8: Read current link speed fail, retry 3
    [    7.574783] ata8: Issued IDENTIFY to non-existent device ?!
    [    9.731066] ata8: Read current link speed fail, retry 1
    [    9.738054] ata8: Read current link speed fail, retry 2
    [    9.745023] ata8: Read current link speed fail, retry 3
     ... [  OK  ]
    :: Loading module megaraid_sas ... [  OK  ]
    :: Loading module mpt2sas ... [  OK  ]
    :: Loading module mpt3sas ... [  OK  ]
    Insert net driver(Mindspeed only)...
    Starting /usr/syno/bin/synocfgen...
    /usr/syno/bin/synocfgen returns 0
    All disk ready or timeout execeed
    [    9.786499] md: invalid raid superblock magic on sdb3
    [    9.788008] md: invalid raid superblock magic on sdc3
    Partition Version=8
     /sbin/e2fsck exists, checking /dev/md0...
    /sbin/e2fsck -pvf returns 0
    Mounting /dev/md0 /tmpRoot
    ------------upgrade
    Begin upgrade procedure
    No upgrade file exists
    End upgrade procedure
    ============upgrade
    Wait 2 seconds for synology manufactory device
    Mon Apr 16 09:10:51 UTC 2018
    /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0
    none /sys/kernel/debug debugfs rw,relatime 0 0
    sys /sys sysfs rw,relatime 0 0
    none /dev devtmpfs rw,relatime,size=2022272k,nr_inodes=505568,mode=755 0 0
    proc /proc proc rw,relatime 0 0
    linuxrc.syno executed successfully.
    Post init
    
    [   16.448571] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.484636] init: Caught abort, core dumped
    [   16.486540] init: Error while reading from descriptor: Broken pipe
    [   16.486793] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.491035] init: Caught abort, core dumped
    [   16.492707] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.493355] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.494398] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.495061] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.497205] init: Caught abort, core dumped
    [   16.499031] init: Caught abort, core dumped
    [   16.500198] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.501480] init: Caught abort, core dumped
    [   16.502762] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.505136] init: Caught abort, core dumped
    [   16.506800] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.510823] init: Caught abort, core dumped
    [   16.510942] init: Caught abort, core dumped
    [   16.513281] init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0
    [   16.514866] init: Caught abort, core dumped
    [   16.521100] init: Caught abort, core dumped
    
     
  4. helleon

    helleon New Member

    注册:
    2018-04-14
    帖子:
    10
    试过了效果是一样的,连console输出都是一样的
     
  5. jameslhc

    jameslhc New Member

    注册:
    2018-04-14
    帖子:
    3
    你用SA点恢复,然后进程开始后你再取消,看看系统是否会重启然后进入系统
    我好像也是这样的情况,目前还没发现合适的办法
     
  6. helleon

    helleon New Member

    注册:
    2018-04-14
    帖子:
    10
    搞定了,忘啦在哪里看到的:把两个数据盘挂到Win或者WinPE下,用磁盘管理软件格式化掉两个2G的系统区,大的数据区不要动。再挂回去,SA提示群晖系统丢失,需要重安装,用SA安装即可。
     
  7. jameslhc

    jameslhc New Member

    注册:
    2018-04-14
    帖子:
    3
    你这样装系统数据应该不会丢,但是是不是系统配置和设置都没有了
     
  8. helleon

    helleon New Member

    注册:
    2018-04-14
    帖子:
    10
    是的,配置都没了,不过我有备份的配置dss文件,可以说没损失了。

    另外Docker里面的东西也都还在,配置也在,比较神奇