6.4 - Array Starting - Starting Services (Stuck?)

[zleef]

Thanks @ljm42, that fixed it!!!

 

- i restored /boot to its previous state, and restarted to confirm the original issue was present at startup (it was). 

- i updated /boot/config/domain.cfg per comment from @ljm42 and restarted. 

 

I didn't have any isos in /mnt/user/isos, so i left the VIRTIOISO blank.

 

 

[ljm42]

excellent!

[JonathanM]

This sounds like a bug that @limetech needs to squash in the next release.

 

Probably should start the array normally, and alert the user with a notification that VM's are enabled but a path is missing so they won't start until corrected in settings, VM Manager.

[sunflashx]

On 1/19/2018 at 6:35 PM, zleef said:

Thanks @ljm42, that fixed it!!!

 

- i restored /boot to its previous state, and restarted to confirm the original issue was present at startup (it was). 

- i updated /boot/config/domain.cfg per comment from @ljm42 and restarted. 

 

I didn't have any isos in /mnt/user/isos, so i left the VIRTIOISO blank.

 

 

 

 

I followed the same steps and was saved from disaster.

 

 

[ti6462]

On 1/19/2018 at 8:05 PM, ljm42 said:

Following a hint from @bakes82, I think I see the problem.  Your /boot/config/domain.cfg file looks like this:

SERVICE="enable"
IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img"
IMAGE_SIZE="1"
DEBUG="no"
DOMAINDIR="/mnt/user/domains/"
MEDIADIR=""
VIRTIOISO=""
BRNAME="virbr0"
VMSTORAGEMODE="auto"

Note that the MEDIADIR setting is empty.  I just verified on my system that that is required for the array to start.  Here is the default:

MEDIADIR="/mnt/user/isos/"

I'm not sure if VIRTIOISO is required, but here is what I have:

VIRTIOISO="/mnt/user/isos/virtio-win-0.1.118-2.iso"

 

Fingers crossed this does it!
 

 

This solved the issue for me as well. 

 

Out of curiosity I checked /boot/config/domain.cfg on 6.3.5 before I attempted another upgrade and the MEDIADIR was empty with no problems.

 

Anyways thanks for solving this!

[wmkuipers]

On 20/01/2018 at 2:05 AM, ljm42 said:

Following a hint from @bakes82, I think I see the problem.  Your /boot/config/domain.cfg file looks like this:

SERVICE="enable"
IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img"
IMAGE_SIZE="1"
DEBUG="no"
DOMAINDIR="/mnt/user/domains/"
MEDIADIR=""
VIRTIOISO=""
BRNAME="virbr0"
VMSTORAGEMODE="auto"

Note that the MEDIADIR setting is empty.  I just verified on my system that that is required for the array to start.  Here is the default:

MEDIADIR="/mnt/user/isos/"

I'm not sure if VIRTIOISO is required, but here is what I have:

VIRTIOISO="/mnt/user/isos/virtio-win-0.1.118-2.iso"

 

Fingers crossed this does it!
 

 

yes, happened to be the fix for me as well

[Bahndit]

On 1/19/2018 at 6:05 PM, ljm42 said:

Following a hint from @bakes82, I think I see the problem.  Your /boot/config/domain.cfg file looks like this:

SERVICE="enable"
IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img"
IMAGE_SIZE="1"
DEBUG="no"
DOMAINDIR="/mnt/user/domains/"
MEDIADIR=""
VIRTIOISO=""
BRNAME="virbr0"
VMSTORAGEMODE="auto"

Note that the MEDIADIR setting is empty.  I just verified on my system that that is required for the array to start.  Here is the default:

MEDIADIR="/mnt/user/isos/"

I'm not sure if VIRTIOISO is required, but here is what I have:

VIRTIOISO="/mnt/user/isos/virtio-win-0.1.118-2.iso"

 

Fingers crossed this does it!
 

This solved the problem I had where UNRAID was stuck on "Starting Services"

[itsdandandan]

This also fixed it for me, thanks!

[strend]

Replace entire domain.cfg with default. and it looks like its up and running again ! Thanks !

[fct]

Hi guys. My ver. 6.10.3 got stucked in "Array Started - Starting services..."

When I look at log I can see some errors:

 

Aug 16 17:56:29 Tower kernel: XFS (md3): metadata I/O error in "xfs_btree_read_buf_block.constprop.0+0x7a/0xc6 [xfs]" at daddr 0x17ffffff8 len 8 error 74
Aug 16 17:56:29 Tower kernel: XFS (md3): Metadata CRC error detected at xfs_allocbt_read_verify+0x12/0x56 [xfs], xfs_cntbt block 0x1fffffff0 
Aug 16 17:56:29 Tower kernel: XFS (md3): Unmount and run xfs_repair
Aug 16 17:56:29 Tower kernel: XFS (md3): First 128 bytes of corrupted metadata buffer:
Aug 16 17:56:29 Tower kernel: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Aug 16 17:56:29 Tower kernel: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Aug 16 17:56:29 Tower kernel: 00000020: 8b e3 8a 45 5d 02 01 90 07 0b 2e 21 59 9e f2 06  ...E]......!Y...
Aug 16 17:56:29 Tower kernel: 00000030: 00 00 00 00 67 65 c9 b5 00 00 00 00 00 00 00 00  ....ge..........
Aug 16 17:56:29 Tower kernel: 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Aug 16 17:56:29 Tower kernel: 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Aug 16 17:56:29 Tower kernel: 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Aug 16 17:56:29 Tower kernel: 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

 

Is this related to Disk3 from array?

 

edit: I found "Starting services..." appears when I try to add SHARE (with no success).

Edited August 16, 2022 by fct

[trurl]

attach diagnostics to your NEXT post in this thread