What in a specifc disk volume can stop DSM7 to boot?

[kaku]

I posted this is ARPL thread, but i think i should post here.

 

I am trying to upgrade my hardware and shift my drives to it. its a B660 chipset board with i5 12400 CPU. 

I used the SAME SN and mac as before (DS3622xs+) as old HW on (TCRP DSM 7.1 4661 )

It has 2 Volumes 

Volume 1 main (RAID 5  with all packages, 3 Disk)

Volume 2 (1 DISK )

I have successfully Loaded  the latest ARPL.

 

Issue is if I Connect Volume 2 (1 DISK to system ) . it boots ok. But if Both volumes are connected (3 + 1 disk ), I get no boot ( no IP).

I have connected Vol2 (1 Disk) to all SATA ports one-by-one to check if any port issues, but they all are ok.

 

Something in main Volume1 is giving boot issues. 

 

If i HOTPLUG the volume1 disk while DSM is running, the volume gets detected and i can assemble them, and "rapair" all packages.

 

I dont know, where to start to solve this issue. how can certain packages force a No BOOT?

 

Sent from my SM-G998B using Tapatalk

 

 

[kaku]

Ok so reinstalling DSM also didnt work. Data is intact but still volume1 disks will not let me boot if plugged in!

Sent from my SM-G998B using Tapatalk

[Peter Suh]

Are you able to boot with only Volume 1?

 

Was Volume 1 the first volume you installed Synology DSM on?

 

If so, the package is probably installed in Volume 1.

 

I don't know why the main system partition used to operate around Volume 1, but it seems to have moved to Volume 2.

 

Volume 2 became the main system partition

 

If Volume 1 is added in the process, system partition synchronization will be induced through Volume 2 and recovery.

 

In this process, all packages of Volume 1 are expected to be initialized.

 

If all my scenarios are correct,

 

I recommend that you try to restore the system partition and packages using only Volume 1, excluding Volume 2, which was added later.

[kaku]

Yes, volume1 had all the packages abd was the first pool.

DSM dont boot if Using only volume1 disk . No IP but led blinks.

Using ONLY Volume2, DSM boots.

Now if i connect disks of volime1 while DSM IS running then all packages are displayed and are marked to repair. I do all the package repair, and then reboot. Then again DSM FAILS TO boot (no ip) led blinks


Volume1 cannot be in system at boot.


Also I did a reinstall of DSM ON BOTH volumes by adding all drives(vol1 &vol2) AFTER the dsm booted and showed no drives error. It went ok . But on reboot again no IP.







Sent from my SM-G998B using Tapatalk

[kaku]

Now I went back to TCRP and using fresh serial. Now atleast DSM boots.

But now i am in a recoverable loop. Any idea how to get out of it?

Sent from my SM-G998B using Tapatalk