Jump to content
XPEnology Community
  • 0

Failed to install DSM-failed to format drives


REDTRONGUY
 Share

Question

I got my pc to display the web portal, and everything looks fine. I have a serial number it's showing that 7.1.0 is currently installed, and the model number is displayed correctly. however whenever I try to install dsm either the update or full os it fails at 0% and states that it failed to format drives

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0
Posted (edited)

 

There is too little information for analysis.

 

What Synology platform or model are you installing on?
And, the model name of the motherboard, the number of hard drives, whether an external SATA controller is used, etc.
Please let me know.

 

If you can access the DSM installation request screen with ttyd as below,

Then send me the log with the command you see.

 

http://<youripaddr>:7681/

id : root / pw : ( no password )

 

cat /var/log/*rc*

 

ls -l /sys/block

 

ls -la /sys/class/ata_device

 

ls -l /dev/syno*

Edited by Peter Suh
Link to comment
Share on other sites

  • 0

Hardware

  Motherboard-Asus B85M-E (4x sata-6, 2x sata-3)

  CPU-i5 4460

  Drives-2xHDD 1xSDD

  Controller-N/A

Platform

  ds920+

  geminilake-7.1.0-42661

 

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
'/etc.defaults/model.dtb' -> '/var/run/model.dtb'
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "mii.ko" for pocopico.r8169 (args: )
Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-r8169.sh" for pocopico.r8169->on_boot
Loading module r8169 -> Module r8169 loaded succesfully
Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-dtb-static->on_boot
'model_ds920p.dtb' -> '/etc.defaults/model.dtb'
'model_ds920p.dtb' -> '/var/run/model.dtb'
Ran "install_rd.sh" for redpill-dtb-static->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
Assemble args:
Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode...
Sun Jul 31 00:19:52 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0
SynologyNAS> 
SynologyNAS> 
SynologyNAS> 
SynologyNAS> ls -l /sys/block
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 Jul 31 00:19 sata1 -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sata1
lrwxrwxrwx    1 root     root             0 Jul 31 00:19 sata2 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sata2
lrwxrwxrwx    1 root     root             0 Jul 31 00:19 sata3 -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sata3
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 synoboot -> ../devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/host6/target6:0:0/6:0:0:0/block/synoboot
SynologyNAS> 
SynologyNAS> 
SynologyNAS> 
SynologyNAS> ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 Jul 31 01:38 .
drwxr-xr-x   46 root     root             0 Jul 31 00:20 ..
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 dev1.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 dev2.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 dev3.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 dev4.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 dev5.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 Jul 31 01:38 dev6.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata6/link6/dev6.0/ata_device/dev6.0
SynologyNAS> 
SynologyNAS> 
SynologyNAS> 
SynologyNAS> ls -l /dev/syno*
crw-r--r--    1 root     root      201,   0 Jul 31 00:19 /dev/synobios
brw-------    1 root     root      135, 240 Jul 31 00:19 /dev/synoboot
brw-------    1 root     root      135, 241 Jul 31 00:19 /dev/synoboot1
brw-------    1 root     root      135, 242 Jul 31 00:19 /dev/synoboot2
brw-------    1 root     root      135, 243 Jul 31 00:19 /dev/synoboot3
SynologyNAS> 
SynologyNAS> 
SynologyNAS> 
SynologyNAS> 

Link to comment
Share on other sites

  • 0
Posted (edited)

In the case of DS920+, Device Tree (DT) is used.
Several different methods have been tried so far to map this DT.
If you use the image of the current pocopico 0.8.0.0 master repo,

 

It use the old-fashioned static dtb patch,
Currently, dynamic dtb patches are more efficient for mapping and finding disks.
If you want to use dynamic dtb patch, you have the hassle of replacing it with 0.9 from TCRP linux image.

 

So, I will share an easier way to build with the m shell for TCRP I developed.

Download my.sh with the command below and execute as below for build.

 

curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O; tar -zxvf my.sh.gz;

./my.sh DS920+J noconfig noclean

 

For the first installation, jun mode is more advantageous and easier, so I use the J option.
You can install the latest version of DSM 7.1 directly through jun mode.

 

Edited by Peter Suh
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...