파일이 손상되었습니다 오류 도와주세요,,,
시스템 사양
CPU: 인텔 i3 8100
MB: 아수스 B360M-A
LAN: 리얼텍 RTL8111H
사용한 이미지 및 버전
tinycore-redpill.mshell 1.0.2.7
상황
- redpill tool chain 으로 환경에 맞게 빌드한 이미지로 918+ 모델용 7.0.1 버전을 운영중이던 시스템을 업데이트하고자 mshell 설치
- 최초에는 918+ 모델 그대로 7.2.1로 업데이트하기 위해 918+ 모델을 선택 후 7.2.1버전으로 로더 빌드함
- DSM 설치과정 중 파일이 손상되었다는 메시지 팝업
- 3622 모델이 성공확률이 높다는 의견에 3622모델로 드리프트했으나 역시나 같은 오류로 실패
- 이후 멀쩡히 운영했던 7.0.1로 되돌리기 위해 이전에 남겨둔 이미지와 패치파일을 사용해 부트로더를 만들고 시도해봤지만 무한 복구에 빠짐
- redpill tool chain을 사용했을땐 정상적으로 사용이 가능했으므로 무한복구 탈출을 위해 3622버전용 이미지를 빌드 후 재 시도해볼 예정
기존에 DSM 7.0.1이 구동되고 있던 시스템을 7.2로 업데이트 하고자 시도했으나 대차게 실패해버렸습니다.
DSM 설치시 처음에는 파일이 손상되었다고 나오다가
이제는 네트워크 연결을 확인하라는 메시지가 나오고 있네요.
아래는 DSM 설치 단계에서 오류가 있는 경우 봐야할 로그파일(/var/log/linuxrc.syno.log)의 마지막 부분입니다.
기존에 VID, PID, S/N, MAC 모두 기록해둔 시스템이라 이 부분에서는 오류가 없을겁니다. 제가 수차례 확인도 해봤구요
어디부터 봐야할까요?
sda, part of md0, has obsolete partition layout 8.
Detected data partition on sda. Must not be fresh installation.
ForceNewestLayout: Skipped
Mounting /dev/md0 /tmpRoot
insmod: can't insert '/usr/lib/modules/r8168.ko': File exists
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
End upgrade procedure
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_apollolake_918+
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_apollolake_918+
Exit on error [7] root not matched with junior...
Mon Apr 15 03:06:30 UTC 2024
:: Loading kernel modules from extensions ...
:: Loading kernel modules from extensions ... [ OK ]
:: Executing "on_jrExit" "jrExit" custom scripts ...
:: Executing "on_jrExit" custom scripts ... [ OK ]
Extensions processed
/dev/md0 /tmpRoot ext4 rw,noatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
시각이 2000년으로 리셋되네요. ㅜㅜ
혹시 rr 에서도 같은 증상이셨나요?
일단 듀얼랜중 랜을 1개만 물린상태인데, 2개다 붙여볼 생각입니다.
SynologyNAS> ll /sys/block
drwxr-xr-x 2 root root 0 Apr 18 2024 .
dr-xr-xr-x 12 root root 0 Apr 18 2024 ..
lrwxrwxrwx 1 root root 0 Apr 18 2024 md0 -> ../devices/virtual/block/md0
lrwxrwxrwx 1 root root 0 Apr 18 2024 md1 -> ../devices/virtual/block/md1
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx 1 root root 0 Apr 18 2024 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx 1 root root 0 Apr 18 2024 sata1 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sata1
lrwxrwxrwx 1 root root 0 Apr 18 2024 sata2 -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sata2
lrwxrwxrwx 1 root root 0 Apr 18 2024 synoboot -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/synoboot
SynologyNAS> ll /dev/syno*
crw-r--r-- 1 root root 201, 0 Apr 18 2024 /dev/synobios
brw------- 1 root root 135, 240 Apr 18 2024 /dev/synoboot
brw------- 1 root root 135, 241 Apr 18 2024 /dev/synoboot1
brw------- 1 root root 135, 242 Apr 18 2024 /dev/synoboot2
brw------- 1 root root 135, 243 Apr 18 2024 /dev/synoboot3
brw------- 1 root root 135, 245 Apr 18 2024 /dev/synoboot5
SynologyNAS> date
Sat Jan 1 00:02:36 UTC 2000
방화벽이 자동시간 동기화에 방해가 되는지도 한번 의심해 봐야 겠습니다.
이 PC 오늘 집에한번 가져가 보겠습니다.
mshell 이나 rr이 아니라서 터미널 접근방법을 모르니 시스템 날짜를 확인해보진 못했습니다만 DSM 설치 과정에서 나오는 메시지가 동일하므로 같은 문제일거라 추측중입니다.
xpenology.com에 관련 검색좀 해보니 보드의 전지 변경으로 해결봤다는 글이 있어 새로 사서 바꿔봤지만 소용 없었구요...
집에서는 방화벽이 없는 환경이라서 일단 집에 가져가려고 포장잘 해두었습니다.
저는 ITX 미니시스템이라서 쉽게 들고갈수가 있네요. ^^
집에 가지고 와서 반복시험을 해보고 있습니다.
집에서도 마찬가지로 DSM 설치 실패가 나고 날짜는 2000년으로 돌아가고 있습니다.
/var/log/messages 가 dmesg 보다 조금더 상세한 로그가 찍히는 곳인데요.
여기에 찍힌 내용중에 의심이 가는부분을 좀더 파보려고 합니다.
메인보드 제조사까지 체크하도록 바뀐것이 있는지 싶어서요.
바로 아래 로그에는 그러한 내용이 보이는것 같습니다.
정상적인 케이스 에서도 이런 메시지가 보이는지 대조해 봐야겠습니다.
일단 제 메인보드는 일반적인 보드는 아니고 일본이 중국에 OEM 해서 만든
Giada 의 DT-H81DL 란 m-ITX 보드입니다. 이젠 제조사 까지 망했는지 인터넷에 검색조차 잘 안되네요.
이런 부분이 연관성이 있는지 한번 살펴보겠습니다.
사용하신 보드는 ASUS 인데 그렇게 보면 또 아닌것 같기도 하네요.
일단 정상로그와 대조부터 해보고 말씀드리겠습니다.
Apr 18 12:15:34 updater: util/updater_util.cpp:90 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Apr 18 12:15:34 updater: util/check_patch_support_hw_revision.cpp:63 This patch supports HW revision of this machine
Apr 18 12:15:34 updater: child exit normally with [0]
Apr 18 12:15:34 updater: updater.c:6501 ==== Start flash update ====
Apr 18 12:15:34 updater: updater.c:6505 This is X86 platform
Apr 18 12:15:34 kernel: [ 222.375216] ext2: synoboot2 mounted, process=updater
Apr 18 12:15:34 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:22)
Apr 18 12:15:34 updater: updater.c:5823 Failed to mount boot partition
Apr 18 12:15:34 updater: updater.c:3195 No need to reset reason for v.64570
Apr 18 12:15:34 updater: updater.c:7120 Failed to accomplish the update! (errno = 21)
Apr 18 12:15:34 install.cgi: ninstaller.c:1652 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Apr 18 12:15:34 kernel: [ 222.393941] vfat: synoboot2 mounted, process=updater
Apr 18 12:15:35 install.cgi: ninstaller.c:139 Mount partion /dev/md0 /tmpRoot
Apr 18 12:15:35 install.cgi: ninstaller.c:1621 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Apr 18 12:15:35 install.cgi: ninstaller.c:168 umount partition /tmpRoot
Apr 18 12:15:35 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Apr 18 12:15:35 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Apr 18 12:15:35 install.cgi: ErrFHOSTDoUpgrade(1986): child process failed, retv=-21
Apr 18 12:15:35 install.cgi: ninstaller.c:2008(ErrFHOSTDoUpgrade) err=[-1]
Apr 18 12:15:35 install.cgi: ninstaller.c:2012(ErrFHOSTDoUpgrade) retv=[-21]
Apr 18 12:15:35 install.cgi: install.c:496 Upgrade for migration by the download patch fail.
Apr 18 12:15:35 install.cgi: install.c:765 Upgrade by download patch fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:168 umount partition /tmpData
메인보드 회사의 문제는 아닌것 같구요. synoboot2 파티션 마운트에 실패가 나는 이유를 찾아봐야 겠습니다.
Apr 18 12:45:32 updater: util/updater_util.cpp:90 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Apr 18 12:45:32 updater: util/check_patch_support_hw_revision.cpp:63 This patch supports HW revision of this machine
Apr 18 12:45:32 updater: child exit normally with [0]
Apr 18 12:45:32 updater: updater.c:6501 ==== Start flash update ====
Apr 18 12:45:32 updater: updater.c:6505 This is X86 platform
Apr 18 12:45:32 kernel: [ 549.699903] ext2: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.700962] vfat: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.708089] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:32 kernel: [ 549.709770] synoboot2 unmounted, process=updater
Apr 18 12:45:32 kernel: [ 549.715490] ext2: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.716492] vfat: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.723544] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:32 kernel: [ 549.725189] synoboot2 unmounted, process=updater
Apr 18 12:45:32 kernel: [ 549.730340] ext2: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.731325] vfat: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.738425] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:32 kernel: [ 549.740096] synoboot2 unmounted, process=updater
Apr 18 12:45:32 kernel: [ 549.744348] ext2: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.745341] vfat: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.752149] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:32 kernel: [ 549.753807] synoboot2 unmounted, process=updater
Apr 18 12:45:32 updater: updater.c:6528 The SynoBoot partitions exist.
Apr 18 12:45:32 updater: updater.c:4139 SYNORedBootUpdCheckAndApply(4139): Skip bootloader update, no uboot_do_upd.sh exists
Apr 18 12:45:32 kernel: [ 549.759397] ext2: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.760536] vfat: synoboot2 mounted, process=updater
Apr 18 12:45:32 kernel: [ 549.767706] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:32 updater: updater.c:616 checksum generated by [/bin/grep -i zImage checksum.syno >> /tmp/checksum.syno.tmp]
Apr 18 12:45:32 updater: updater.c:645 file [zImage] is being copied to [/tmp/bootmnt]
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/zImage] process done.
Apr 18 12:45:32 updater: updater.c:616 checksum generated by [/bin/grep -i rd.gz checksum.syno >> /tmp/checksum.syno.tmp]
Apr 18 12:45:32 updater: updater.c:645 file [rd.gz] is being copied to [/tmp/bootmnt]
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/rd.gz] process done.
Apr 18 12:45:32 updater: updater.c:616 checksum generated by [/bin/grep -i grub_cksum.syno checksum.syno >> /tmp/checksum.syno.tmp]
Apr 18 12:45:32 updater: updater.c:645 file [grub_cksum.syno] is being copied to [/tmp/bootmnt]
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/grub_cksum.syno] process done.
Apr 18 12:45:32 updater: updater.c:636 file [/tmp/bootmnt/hda1.tgz] is being removed
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/hda1.tgz] process done.
Apr 18 12:45:32 updater: updater.c:636 file [/tmp/bootmnt/updater] is being removed
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/updater] process done.
Apr 18 12:45:32 updater: updater.c:636 file [/tmp/bootmnt/VERSION] is being removed
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/VERSION] process done.
Apr 18 12:45:32 updater: updater.c:616 checksum generated by [/bin/grep -i model.dtb checksum.syno >> /tmp/checksum.syno.tmp]
Apr 18 12:45:32 updater: updater.c:645 file [model.dtb] is being copied to [/tmp/bootmnt]
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/model.dtb] process done.
Apr 18 12:45:32 updater: updater.c:616 checksum generated by [/bin/grep -i model_r1.dtb checksum.syno >> /tmp/checksum.syno.tmp]
Apr 18 12:45:32 updater: updater.c:645 file [model_r1.dtb] is being copied to [/tmp/bootmnt]
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/model_r1.dtb] process done.
Apr 18 12:45:32 updater: updater.c:616 checksum generated by [/bin/grep -i model_r2.dtb checksum.syno >> /tmp/checksum.syno.tmp]
Apr 18 12:45:32 updater: updater.c:645 file [model_r2.dtb] is being copied to [/tmp/bootmnt]
Apr 18 12:45:32 updater: updater.c:653 file [/tmp/bootmnt/model_r2.dtb] process done.
Apr 18 12:45:32 updater: updater.c:663 checksum file updated by [/bin/cp -f /tmp/checksum.syno.tmp /tmp/bootmnt/checksum.syno]
Apr 18 12:45:32 kernel: [ 549.972786] synoboot2 unmounted, process=updater
Apr 18 12:45:37 kernel: [ 554.983256] ext2: synoboot2 mounted, process=updater
Apr 18 12:45:37 kernel: [ 554.984318] vfat: synoboot2 mounted, process=updater
Apr 18 12:45:37 kernel: [ 554.991646] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:37 kernel: [ 555.029194] synoboot2 unmounted, process=updater
Apr 18 12:45:37 updater: updater.c:1213 This model DS920+ needs no factory upgrade
Apr 18 12:45:37 kernel: [ 555.037852] ext2: synoboot1 mounted, process=updater
Apr 18 12:45:37 kernel: [ 555.039040] vfat: synoboot1 mounted, process=updater
Apr 18 12:45:37 kernel: [ 555.047442] FAT-fs (synoboot1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 18 12:45:37 kernel: [ 555.049996] synoboot1 unmounted, process=updater
Apr 18 12:45:37 kernel: [ 555.056356] Module [phy_alloc] is removed.
Apr 18 12:45:37 updater: updater.c:6828 ==== Finish flash update ====
SynologyNAS> mount -t vfat synoboot2 /tmp/bootmnt
mount: mounting synoboot2 on /tmp/bootmnt failed: Invalid argument
vfat 파티션 마운트에 실패합니다.
정상적으로 설치가 가능한 경우는 저 위에 똑같은 커맨드에서도 마운트가 성공합니다.
fat16 으로 포맷된 vfat파티션을 마운트하지 못하는 이유를 더 찾아봐야 겠습니다.
아무래도 vfat 처리를 위한 리눅스 dosfstools 가 덜 설치된것처럼 동작되는 이유를 알아봐야겠네요.
로더를 새로운 img 이미지로 부터 다시 구워보셔야 할것 같습니다.
/dev/synoboot2 fat16 파티션이 어떤 이유에서 손상된것 같습니다.
용량이 풀이 나는경우도 원인이 될 수 있구요.
제 경우는
/dev/synoboot3 도 손상이 된것 같습니다.
시스템 시각이 리셋된 환경에서도
/dev/synoboot1 은 마운트가 잘 처리 됩니다.
저도 로더를 새롭게 다시 굽고 시도해 보겠습니다.
원인을 찾았습니다. ㅜㅜ
다시 구워도 증상이 반복되서 이상하다 싶었는데,
아마 USB 형 로더가 아니라
저용량의 MSATA 아니면 SSD 에 SATA형 부트로더를 사용하고 계실것 같네요.
제 경우는 32GB SSD 를 2장 사용하고 있었고, MSATA가 부트로더로 동작하고 있었는데,
이 MSATA 도 용량이 동일하게 32GB 입니다.
MSATA 와 SSD 디스크 크기 경계를 두는 dom_szmax= 값을 적절히 조정을 해야 하는데요.
아마 프로그램에서 32GB를 강제로 가리키도록 되어 있었을 겁니다.
이 구분을 두기 위해선 용량을 조금 낮추어야 합니다.
dom_szmax=30535.7 근처의 값이 보이신다면
dom_szmax=15000 정도로 낮춰 보십시요.
SATA 하드가 부트로더로 둔갑한 경우라 파티션이 비정상적으로 마운트되고 있었습니다.
dom_szmax=15000 으로 조정한 결과로는 저는 아래처럼 내용이 바뀌어 나옵니다.
에러가 있는 상태에서는 ll /dev/syno* 하셨을때 처음 제게 공유 주셨던 내용처럼 135,135,135,135 가 아닌 아래처럼 8,8,8,8 이 되어야 합니다.
SynologyNAS> fdisk -l
Disk /dev/sata1: 30 GB, 32017047552 bytes, 62533296 sectors
3892 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sata1p1 0,130,3 1023,254,63 8192 16785407 16777216 8192M fd Linux raid autodetect
/dev/sata1p2 1023,254,63 1023,254,63 16785408 20979711 4194304 2048M fd Linux raid autodetect
/dev/sata1p3 1023,254,63 1023,254,63 21241856 62528895 41287040 19.6G f Win95 Ext'd (LBA)
/dev/sata1p5 1023,254,63 1023,254,63 21257952 62336127 41078176 19.5G fd Linux raid autodetect
Disk /dev/sata2: 30 GB, 32017047552 bytes, 62533296 sectors
3892 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sata2p1 0,130,3 1023,254,63 8192 16785407 16777216 8192M fd Linux raid autodetect
/dev/sata2p2 1023,254,63 1023,254,63 16785408 20979711 4194304 2048M fd Linux raid autodetect
/dev/sata2p3 1023,254,63 1023,254,63 21241856 62528895 41287040 19.6G f Win95 Ext'd (LBA)
/dev/sata2p5 1023,254,63 1023,254,63 21257952 62336127 41078176 19.5G fd Linux raid autodetect
Disk /dev/md0: 8191 MB, 8589869056 bytes, 16777088 sectors
2097136 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/md1 doesn't contain a valid partition table
SynologyNAS> ll /dev/syno*
crw-r--r-- 1 root root 201, 0 Apr 18 15:02 /dev/synobios
brw-r--r-- 1 root root 8, 32 Apr 18 15:02 /dev/synoboot
brw-r--r-- 1 root root 8, 33 Apr 18 15:02 /dev/synoboot1
brw-r--r-- 1 root root 8, 34 Apr 18 15:02 /dev/synoboot2
brw-r--r-- 1 root root 8, 35 Apr 18 15:02 /dev/synoboot3
저는 일단 USB로 진행했구요 8기가, 16기가 두개 보유중이라 각각 진행해봤는데 해당 증상이었습니다.
시간여유 있을때 해당 마운트 저도 시도해보고 결과 공유 해볼게요
일단 synoboot 마운트가 잘 되는지 확인부터 해봤습니다.
SynologyNAS> mount -t vfat synoboot1 /tmp/bootmnt
SynologyNAS> umount /tmp/bootmnt
SynologyNAS> mount -t vfat synoboot2 /tmp/bootmnt
SynologyNAS> umount /tmp/bootmnt
SynologyNAS> mount -t vfat synoboot3 /tmp/bootmnt
SynologyNAS> umount /tmp/bootmnt
SynologyNAS> mount -t vfat synoboot /tmp/bootmnt
mount: mounting synoboot on /tmp/bootmnt failed: Invalid argument
synoboot1, 2, 3 까지는 잘 되는데 그냥 synoboot는 에러가 나네요
그리고 fdisk -l의 결과 내용입니다
fdisk -l
SynologyNAS> fdisk -l
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sdb1 0,0,1 1023,254,63 1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdc: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sdc1 0,0,1 1023,254,63 1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdd: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sdd1 0,0,1 1023,254,63 1 4294967295 4294967295 2047G ee EFI GPT
Disk /dev/sda: 1863 GB, 2000398934016 bytes, 3907029168 sectors
243201 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect
/dev/sda2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect
/dev/sda3 587,111,37 1023,254,63 9437184 3906824351 3897387168 1858G fd Linux raid autodetect
Disk /dev/synoboot: 14 GB, 15376318464 bytes, 30031872 sectors
14664 cylinders, 64 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/synoboot1 * 0,32,33 9,78,5 2048 149503 147456 72.0M 83 Linux
/dev/synoboot2 9,78,6 18,221,11 149504 303103 153600 75.0M 83 Linux
/dev/synoboot3 18,221,12 260,243,47 303104 4192255 3889152 1899M 83 Linux
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/md1 doesn't contain a valid partition table
다만 제 수준에서는 어떤부분이 문제일지 잘 모르겠네요,,
fdisk 상에서 보이는 아래 3개의 파티션도 모두 정상으로 보입니다.
저하고는 다른 양상이네요.
/dev/synoboot1 * 0,32,33 9,78,5 2048 149503 147456 72.0M 83 Linux
/dev/synoboot2 9,78,6 18,221,11 149504 303103 153600 75.0M 83 Linux
/dev/synoboot3 18,221,12 260,243,47 303104 4192255 3889152 1899M 83 Linux
저렇게 오류가 발생한 직후 시각이 2000년 초기화가 된 직후
/var/log/messages 파일을 좀 보여주실 수 있나요?
분석할 실력이 충분치 못하지만 한번 노력 해보겠습니다.
부팅 후 :7681 터미널로 접속하는 것 부터 DSM 설치 시도 후 2000년으로 바뀌는 것 까지 기록된 로그입니다.
cat /var/log/messages
Apr 19 07:18:21 kernel: [ 17.349751] i40e: Unknown symbol intel_auxiliary_device_init (err 0)
Apr 19 07:18:21 kernel: [ 17.357854] i40e: Unknown symbol intel___auxiliary_device_add (err 0)
Apr 19 07:18:21 kernel: [ 17.371469] i40e: Unknown symbol intel_auxiliary_device_init (err 0)
Apr 19 07:18:21 kernel: [ 17.378574] i40e: Unknown symbol intel___auxiliary_device_add (err 0)
Apr 19 07:18:21 kernel: [ 17.420549] RPC: Registered named UNIX socket transport module.
Apr 19 07:18:21 kernel: [ 17.427022] RPC: Registered udp transport module.
Apr 19 07:18:21 kernel: [ 17.432165] RPC: Registered tcp transport module.
Apr 19 07:18:21 kernel: [ 17.437283] RPC: Registered tcp NFSv4.1 backchannel transport module.
Apr 19 07:18:21 kernel: [ 18.491989] Module [adt7475] is removed.
Apr 19 07:18:21 kernel: [ 18.504500] Module [i2c_i801] is removed.
Apr 19 07:18:21 kernel: [ 20.554366] Module [adt7475] is removed.
Apr 19 07:18:21 kernel: [ 20.570223] Module [i2c_i801] is removed.
Apr 19 07:18:21 kernel: [ 22.619938] Module [adt7475] is removed.
Apr 19 07:18:21 kernel: [ 22.636940] Module [i2c_i801] is removed.
Apr 19 07:18:21 kernel: [ 23.728137] synobios open /dev/ttyS1 success
Apr 19 07:18:21 kernel: [ 23.733138] 2024-4-19 7:18:18 UTC
Apr 19 07:18:21 kernel: [ 23.736733] synobios: load, major number 201
Apr 19 07:18:21 kernel: [ 23.741385] Brand: Synology
Apr 19 07:18:21 kernel: [ 23.744440] Model: DS-3622xs+
Apr 19 07:18:21 kernel: [ 23.747676] set group disks wakeup number to 4, spinup time deno 7
Apr 19 07:18:21 kernel: [ 23.754377] synobios cpu_arch proc entry initialized
Apr 19 07:18:21 kernel: [ 23.759650] synobios crypto_hw proc entry initialized
Apr 19 07:18:21 kernel: [ 23.765100] synobios syno_platform proc entry initialized
Apr 19 07:18:21 kernel: [ 24.375578] Module [broadwellnk_synobios] is removed.
Apr 19 07:18:21 kernel: [ 24.381026] synobios: unload
Apr 19 07:18:21 kernel: [ 24.408079] synobios open /dev/ttyS1 success
Apr 19 07:18:21 kernel: [ 24.412878] 2024-4-19 7:18:19 UTC
Apr 19 07:18:21 kernel: [ 24.416415] synobios: load, major number 201
Apr 19 07:18:21 kernel: [ 24.420964] Brand: Synology
Apr 19 07:18:21 kernel: [ 24.423959] Model: DS-3622xs+
Apr 19 07:18:21 kernel: [ 24.427120] set group disks wakeup number to 4, spinup time deno 7
Apr 19 07:18:21 kernel: [ 24.433697] synobios cpu_arch proc entry initialized
Apr 19 07:18:21 kernel: [ 24.439043] synobios crypto_hw proc entry initialized
Apr 19 07:18:21 kernel: [ 24.444424] synobios syno_platform proc entry initialized
Apr 19 07:18:21 kernel: [ 25.859474] eth0: (MAC), (MAC), IRQ 123
Apr 19 07:18:21 scemd: scemd.c:860(main) start scemd
Apr 19 07:18:23 kernel: [ 28.953367] r8168: eth0: link up
Apr 19 07:18:23 udhcpc: networking/udhcp/synoether.c (170) MAC address of interface eth0 is [(MAC)]
Apr 19 07:18:23 udhcpc: networking/udhcp/synoether.c (278) Broadcasting ARPOP_REQUEST for 169.254.203.222
Apr 19 07:18:28 scemd: net/net_wol_enable.c:117 Cannot get current wake-on-lan settings
Apr 19 07:18:28 scemd: net/net_wol_enable.c:256 Failed to set wake-on-lan eth99 d
Apr 19 07:18:28 scemd: scemd.c:304 failed to disable WOL. Interface [eth99]
Apr 19 07:18:28 findhostd: ninstaller.c:699 Dev: sda, DiskPath: /dev/sda, Partition version: 8
Apr 19 07:18:28 findhostd: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:18:28 kernel: [ 34.164604] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:28 avahi-daemon[9020]: /etc/avahi/services/http.service: parse failure: service group incomplete.
Apr 19 07:18:28 avahi-daemon[9020]: Failed to load service group file /etc/avahi/services/http.service, ignoring.
Apr 19 07:18:28 kernel: [ 34.189158] uhci_hcd: USB Universal Host Controller Interface driver
Apr 19 07:18:28 kernel: [ 34.200333] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:28 findhostd: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:18:28 kernel: [ 34.212839] usbcore: registered new interface driver usbhid
Apr 19 07:18:28 kernel: [ 34.219295] usbhid: USB HID core driver
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:595 synoinstall: synoarchive: [/tmp/JEP.jep][OPEN] Type: JuniorExpansionPack
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:84 synoinstall: synoarchive: [/tmp/JEP.jep][INIT] [/tmp/JEP.extract]
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:92 synoinstall: synoarchive: [/tmp/JEP.jep][OPEN] Start
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:102 synoinstall: synoarchive: [/tmp/JEP.jep][OPEN] End: [Success][3688618971][0.012s]
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:286 synoinstall: synoarchive: [/tmp/JEP.jep][EXTRACT_ALL] Start
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:299 synoinstall: synoarchive: [/tmp/JEP.jep][EXTRACT_ALL] End: [Success][3688618971][0.014s]
Apr 19 07:18:29 syno_extract_junior_expansion_pack: lib/synoarchive.c:229 synoinstall: synoarchive: [/tmp/JEP.jep][FREE]
Apr 19 07:18:30 findhostd: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:18:30 kernel: [ 36.067997] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:30 kernel: [ 36.111071] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:30 findhostd: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:18:30 findhostd: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:18:30 kernel: [ 36.167081] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:30 kernel: [ 36.188204] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:30 findhostd: ninstaller.c:511 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Apr 19 07:18:31 findhostd: util_junior.c:353 Models are not the same. [synology_broadwellnk_3622xs+, synology_apollolake_918+]
Apr 19 07:18:31 findhostd: ninstaller.c:881 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf]
Apr 19 07:18:31 findhostd: ninstaller.c:1307 SYSTEM_NORMAL, [Recoverable=0]
Apr 19 07:18:31 findhostd: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:18:31 findhostd: ninstaller.c:1222(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Apr 19 07:18:31 findhostd: ninstaller.c:1223(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Apr 19 07:18:31 findhostd: ninstaller.c:1331 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Apr 19 07:18:31 synoupgrade: ninstaller.c:699 Dev: sda, DiskPath: /dev/sda, Partition version: 8
Apr 19 07:18:31 root: Failed to register alias [1]
Apr 19 07:18:31 synoupgrade: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:18:31 root: Failed to register quickconnect alias []
Apr 19 07:18:31 root: Failed to run https installation
Apr 19 07:18:31 root: Failed to run JuniorExpansionPack [1]
Apr 19 07:18:31 root: Failed to run JuniorExpansionPack
Apr 19 07:18:31 kernel: [ 36.648310] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:31 kernel: [ 36.669095] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:31 synoupgrade: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:18:31 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:33 synoupgrade: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:18:33 kernel: [ 38.495434] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:33 kernel: [ 38.534560] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:33 synoupgrade: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:18:33 synoupgrade: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:18:33 kernel: [ 38.588356] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:33 kernel: [ 38.609102] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:33 synoupgrade: ninstaller.c:511 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Apr 19 07:18:33 synoupgrade: util_junior.c:353 Models are not the same. [synology_broadwellnk_3622xs+, synology_apollolake_918+]
Apr 19 07:18:33 synoupgrade: ninstaller.c:881 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf]
Apr 19 07:18:33 synoupgrade: ninstaller.c:1307 SYSTEM_NORMAL, [Recoverable=0]
Apr 19 07:18:33 synoupgrade: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:18:33 synoupgrade: ninstaller.c:1222(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Apr 19 07:18:33 synoupgrade: ninstaller.c:1223(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Apr 19 07:18:33 synoupgrade: ninstaller.c:1331 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Apr 19 07:18:35 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:38 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:38 synoagentregisterd: synoagentregisterd.c:149 Generating register key...
Apr 19 07:18:38 synoagentregisterd: synoagentregisterd.c:163 Generated register key [(KEY)].
Apr 19 07:18:38 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:40 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Apr 19 07:18:40 kernel: [ 49.062103] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:18:40 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Apr 19 07:18:40 synoupgrade: get_disk_dsm_version.c:59 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Apr 19 07:18:40 kernel: [ 49.103244] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:18:40 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Apr 19 07:18:40 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Apr 19 07:18:40 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
Apr 19 07:18:41 login[9357]: root login on 'pts/0'
Apr 19 07:18:41 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:45 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:48 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:51 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:55 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:18:58 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:01 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:04 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:08 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:11 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:14 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:17 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:21 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:22 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 07:19:22 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 07:19:22 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 07:19:22 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
Apr 19 07:19:24 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:27 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 07:19:27 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 07:19:27 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 07:19:27 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
Apr 19 07:19:27 install.cgi: install.c:571 Unknown param localinstallreq=false
Apr 19 07:19:27 install.cgi: install.c:571 Unknown param _dc=1713511167980
Apr 19 07:19:27 install.cgi: ninstaller.c:699 Dev: sda, DiskPath: /dev/sda, Partition version: 8
Apr 19 07:19:27 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:19:27 kernel: [ 95.969048] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:19:27 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:27 kernel: [ 96.047692] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:19:27 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:19:29 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:19:29 kernel: [ 98.011035] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:19:29 kernel: [ 98.054664] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:19:29 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:19:29 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 07:19:29 kernel: [ 98.108908] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:19:29 kernel: [ 98.121245] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:19:29 install.cgi: ninstaller.c:511 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Apr 19 07:19:29 install.cgi: util_junior.c:353 Models are not the same. [synology_broadwellnk_3622xs+, synology_apollolake_918+]
Apr 19 07:19:29 install.cgi: ninstaller.c:881 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf]
Apr 19 07:19:29 install.cgi: ninstaller.c:1307 SYSTEM_NORMAL, [Recoverable=0]
Apr 19 07:19:29 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 07:19:30 install.cgi: ninstaller.c:1222(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Apr 19 07:19:30 install.cgi: ninstaller.c:1223(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Apr 19 07:19:30 install.cgi: ninstaller.c:1331 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Apr 19 07:19:30 install.cgi: synoupgrade.c:785 system status = 1
Apr 19 07:19:30 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpData
Apr 19 07:19:30 kernel: [ 98.422000] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 07:19:30 kernel: [ 98.442368] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 07:19:30 install.cgi: ninstaller.c:1390 FreeSize = 406921216 bytes
Apr 19 07:19:30 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:34 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:37 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 07:19:37 install.cgi: synoupgrade.c:1043 fail to perform curl, CURLcode returns 23
Apr 19 07:19:37 install.cgi: install.c:496 Upgrade for migration by the download patch fail.
Apr 19 07:19:37 install.cgi: install.c:785 Upgrade by download patch fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:169 umount partition /tmpData
Jan 1 00:00:03 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Jan 1 00:00:06 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Jan 1 00:00:09 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Jan 1 00:00:09 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Jan 1 00:00:09 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Jan 1 00:00:09 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
저한테는 안보이던 내용이
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 07:18:41 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
아래와 같이 디스크와 관련한 시리얼정보 확인사항 같은데요.
이 로그내용 받으시기 전에 혹시 로더 다시한번 빌드하신적 없으시죠?
이와 관련된 사항을 제가 헤놀로지 포럼에 리포팅한적이 있었네요.
https://xpenology.com/forum/topic/53817-tinycore-redpill-loader-tcrp/?do=findComment&comment=449275
hdd db 정보가 기록이 누락되서 매칭을 못하는 상황 같아보입니다.
어제 관련되 hdddb addon 을 최신버전으로 현행화를 했습니다.
위와 같이 펌웨어 누락된 정보가 없도록 다시한번 로더 빌드해 보실수 있나요?
로더 빌드하신 이후에 hdddb addon 이 잘 들어가 있는지 확인하는 방법은 4번째 창에서 아래처럼 커맨드 해보시고 폴더 리스트중이 보이시는지 확인 부탁드립니다.
ll *load/c*/e*
정말이네요
리빌드 전에 이렇게 떴던게
리빌드 후 이렇게 리스트가 떠주네요
DSM설치 진행 후 실패하면 로그 한번더 가져오겠습니다
DSM 설치에 실패했고 시간도 2000년으로 돌아가네요
3622xsDSM 자동 다운로드 설치
Apr 19 14:10:21 install.cgi: install.c:571 Unknown param localinstallreq=false
Apr 19 14:10:21 install.cgi: install.c:571 Unknown param _dc=1713535838697
Apr 19 14:10:21 install.cgi: ninstaller.c:699 Dev: sda, DiskPath: /dev/sda, Partition version: 8
Apr 19 14:10:21 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 14:10:21 kernel: [ 309.349462] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 14:10:21 kernel: [ 309.428494] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 14:10:21 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 14:10:22 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:10:23 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 14:10:23 kernel: [ 311.518829] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 14:10:23 kernel: [ 311.560157] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 14:10:23 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 14:10:23 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 14:10:23 kernel: [ 311.614319] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 14:10:23 kernel: [ 311.627232] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 14:10:23 install.cgi: ninstaller.c:511 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Apr 19 14:10:23 install.cgi: util_junior.c:353 Models are not the same. [synology_broadwellnk_3622xs+, synology_apollolake_918+]
Apr 19 14:10:23 install.cgi: ninstaller.c:881 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf]
Apr 19 14:10:23 install.cgi: ninstaller.c:1307 SYSTEM_NORMAL, [Recoverable=0]
Apr 19 14:10:23 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 14:10:23 install.cgi: ninstaller.c:1222(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Apr 19 14:10:23 install.cgi: ninstaller.c:1223(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Apr 19 14:10:23 install.cgi: ninstaller.c:1331 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Apr 19 14:10:23 install.cgi: synoupgrade.c:785 system status = 1
Apr 19 14:10:23 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpData
Apr 19 14:10:23 kernel: [ 311.922853] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 14:10:23 kernel: [ 311.938206] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 14:10:23 install.cgi: ninstaller.c:1390 FreeSize = 406925312 bytes
Apr 19 14:10:25 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:10:28 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:10:31 install.cgi: synoupgrade.c:1043 fail to perform curl, CURLcode returns 23
Apr 19 14:10:31 install.cgi: install.c:496 Upgrade for migration by the download patch fail.
Apr 19 14:10:31 install.cgi: install.c:785 Upgrade by download patch fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:169 umount partition /tmpData
Jan 1 00:00:00 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Jan 1 00:00:03 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Jan 1 00:00:06 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Jan 1 00:00:08 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Jan 1 00:00:08 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Jan 1 00:00:08 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Jan 1 00:00:08 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
Jan 1 00:00:09 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Jan 1 00:00:13 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
3622xs DSM 수동 업로드 설치
Apr 19 14:14:11 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 14:14:11 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 14:14:11 kernel: [ 480.265061] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 14:14:11 kernel: [ 480.278285] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 14:14:11 install.cgi: ninstaller.c:511 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Apr 19 14:14:11 install.cgi: util_junior.c:353 Models are not the same. [synology_broadwellnk_3622xs+, synology_apollolake_918+]
Apr 19 14:14:11 install.cgi: ninstaller.c:881 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf]
Apr 19 14:14:11 install.cgi: ninstaller.c:1307 SYSTEM_NORMAL, [Recoverable=0]
Apr 19 14:14:11 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 14:14:11 install.cgi: ninstaller.c:1222(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Apr 19 14:14:11 install.cgi: ninstaller.c:1223(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Apr 19 14:14:11 install.cgi: ninstaller.c:1331 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Apr 19 14:14:11 install.cgi: synoupgrade.c:785 system status = 1
Apr 19 14:14:11 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpData
Apr 19 14:14:11 kernel: [ 480.557669] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 14:14:11 kernel: [ 480.578123] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 14:14:11 install.cgi: ninstaller.c:1390 FreeSize = 406925312 bytes
Apr 19 14:14:13 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:14:15 install.cgi: synoupload.c:609 failed to write file /tmpData/@autoupdate/upload_tmp.166400, read size=2048, write size=189, errno=No such file or directory(2)
Apr 19 14:14:16 install.cgi: synoupload.c:776 failed to read file. 390141932/415857803
Apr 19 14:14:16 install.cgi: install.c:603 Failed to Load CGI param
Apr 19 14:14:16 install.cgi: install.c:748 Upload patch fail
Apr 19 14:14:16 install.cgi: ninstaller.c:169 umount partition /tmpData
Apr 19 14:14:17 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:14:20 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:14:23 scemd: oob/oob_reg_read.c:46 Read OOB reg 316 failed, ret=-1
Apr 19 14:14:23 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 14:14:23 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 14:14:23 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 14:14:23 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD40EFZX-68AWUN0 81.00B81 69057.0
혹시몰라 918+로도 진행 해봤습니다.
3622xs에서는 DSM 설치시 네트워크 오류메시지만 떴었는데
918+는 파일이 손상된거 같다는 메시지로 바뀌네요
수동 업로드만 진행했고 로그도 좀 바뀌긴 했습니다.
918+ DSM 수동 업로드 설치
pr 19 15:04:03 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 15:04:03 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 15:04:03 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 15:04:04 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 15:04:04 kernel: [ 223.562620] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 15:04:04 kernel: [ 223.601019] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 15:04:04 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 15:04:04 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpRoot
Apr 19 15:04:04 kernel: [ 223.655211] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 15:04:04 kernel: [ 223.671895] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 15:04:04 install.cgi: ninstaller.c:511 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Apr 19 15:04:04 install.cgi: ninstaller.c:892 flash version is newer than disk version
Apr 19 15:04:04 install.cgi: ninstaller.c:1307 SYSTEM_NORMAL, [Recoverable=0]
Apr 19 15:04:04 install.cgi: ninstaller.c:169 umount partition /tmpRoot
Apr 19 15:04:04 install.cgi: ninstaller.c:1222(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Apr 19 15:04:04 install.cgi: ninstaller.c:1223(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Apr 19 15:04:04 install.cgi: ninstaller.c:1331 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Apr 19 15:04:04 install.cgi: synoupgrade.c:785 system status = 1
Apr 19 15:04:04 install.cgi: ninstaller.c:140 Mount partion /dev/md0 /tmpData
Apr 19 15:04:04 kernel: [ 223.889024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Apr 19 15:04:04 kernel: [ 223.934313] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Apr 19 15:04:04 install.cgi: ninstaller.c:1390 FreeSize = 406925312 bytes
Apr 19 15:04:10 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Apr 19 15:04:10 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Apr 19 15:04:10 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 15:04:11 install.cgi: generic_hash.c:80 Generic hash: /tmpData/@autoupdate/upload.pat: 5c9f58f4532c49cd577831977de0c3a051f4a92c80d55499a37e78a8479fcc49
Apr 19 15:04:11 install.cgi: synoupgrade.c:1366 Extracting VERSION from Old Patch Format [/tmpData/@autoupdate/upload.pat][/tmpData/@autoupdate]
Apr 19 15:04:11 install.cgi: synoupgrade.c:1372 Extracting VERSION from SynoArchive
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:440 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][OPEN] Type: System
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:84 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][INIT] [/tmpData/@autoupdate]
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:92 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][OPEN] Start
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:102 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][OPEN] End: [Success][3688618971][0.408s]
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:288 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][EXTRACT_ONE][VERSION] Start
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:305 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][EXTRACT_ONE][VERSION] End: [Success][3688618971][0.000s]
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:229 synoinstall: synoarchive: [/tmpData/@autoupdate/upload.pat][FREE]
Apr 19 15:04:11 install.cgi: Remove /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Apr 19 15:04:11 install.cgi: Create /tmpData/upd@te...cmd=[/bin/mkdir -p /tmpData/upd@te > /dev/null 2>&1]
Apr 19 15:04:11 install.cgi: ninstaller.c:1443 Extracting SynoArchive [/tmpData/upd@te.pat][/tmpData/upd@te]
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:440 synoinstall: synoarchive: [/tmpData/upd@te.pat][OPEN] Type: System
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:84 synoinstall: synoarchive: [/tmpData/upd@te.pat][INIT] [/tmpData/upd@te]
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:92 synoinstall: synoarchive: [/tmpData/upd@te.pat][OPEN] Start
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:102 synoinstall: synoarchive: [/tmpData/upd@te.pat][OPEN] End: [Success][3688618971][0.443s]
Apr 19 15:04:11 install.cgi: lib/synoarchive.c:286 synoinstall: synoarchive: [/tmpData/upd@te.pat][EXTRACT_ALL] Start
Apr 19 15:04:15 install.cgi: ardchive_write_data_block failed. [Write failed]
Apr 19 15:04:15 install.cgi: Unknown Error: [28]
Apr 19 15:04:15 install.cgi: copy_data failed. extract filename: [/tmpData/upd@te/hda1.tgz]
Apr 19 15:04:15 install.cgi: lib/synoarchive.c:299 synoinstall: synoarchive: [/tmpData/upd@te.pat][EXTRACT_ALL] End: [Fail][24][3.832s]
Apr 19 15:04:15 install.cgi: lib/synoarchive.c:314 Extract failed [/tmpData/upd@te.pat]
Apr 19 15:04:15 install.cgi: lib/synoarchive.c:229 synoinstall: synoarchive: [/tmpData/upd@te.pat][FREE]
Apr 19 15:04:15 install.cgi: ninstaller.c:1465 Failed to extract patch due to unknown format.
Apr 19 15:04:15 install.cgi: ninstaller.c:1493 Extraction failed [/tmpData/upd@te.pat][/tmpData/upd@te]
Apr 19 15:04:15 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Apr 19 15:04:15 install.cgi: ninstaller.c:1588 set error code [-13]
Apr 19 15:04:17 install.cgi: ninstaller.c:2059(ErrFHOSTDoUpgrade) err=[-1]
Apr 19 15:04:17 install.cgi: ninstaller.c:2063(ErrFHOSTDoUpgrade) retv=[-13]
Apr 19 15:04:17 install.cgi: install.c:458 Upgrade by the manual patch fail.
Apr 19 15:04:17 install.cgi: install.c:780 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:169 umount partition /tmpData
Jan 1 00:00:00 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on DT01ACA200 MX4OABB0 69057.0
Jan 1 00:00:00 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WDC WUH721414ALE604 LDAZW110 69057.0
Jan 1 00:00:00 synodiskport: disk/disk_rule_junior.c:109 Failed to get target on WD80EZAZ-11TDBA0 83.H0A83 69057.0
Apr 19 15:04:15 install.cgi: ardchive_write_data_block failed. [Write failed]
이부분에서 ardchive_write 에 d가 의미하는게 있어 붙은건지 모르겠네요...
해당 에러코드들 구글링 해봤지만 딱히 나오는 답이 없네요
업데이트 파일을 압축해제하는 과정에서 오류가 뜨는거 같긴한데
더 자세하게는 모르겠습니다 ㅠㅠ
지난번 이 문의를 했었다고 생각했는데, 제가 머리속으로만 생각하고 질문을 안드렸었네요.
하드의 시리얼번호를 계속 찾는건 원래 RAID 구성에 S.M.A.R.T 정보를 기반으로한 이 시리얼번호 정보가 중요하게 사용되기 때문으로 알고 있습니다.
RAID 가 풀리는 경우나 RAID 를 재구성해야 하는경우 시리얼번호 기준으로 원래 디스크들의 위치를 찾아가는데요.
SHR 등의 RAID 는 아닌가요?
2T / 14T / 8T / 3T
cmt alert
신고
"님의 댓글"
이 댓글을 신고하시겠습니까?
