Disk operation failed Error code: (21)

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
gklpnd
Posts: 14
Joined: Wed Mar 04, 2020 2:38 pm

Mon Apr 05, 2021 3:36 pm

Hello,

After failure of enclosure we started saw this messages in log:

Code: Select all

4/5 17:43:53.229625 2384 IMG: *** ImageFile_IoCompleted: Disk operation failed. Disk path: Y:\starwind\vbr01-sw244\vbr01-sw244.img. Error code: (21).
Enclosure was rebooted and in starwind host disk is working properly ( files are creating and deleting :D )

This is standalone flat disk with cachemode=none.

On client this disk connected via iscsi but not initialized (DiskPart has encountered an error: Data error (cyclic redundancy check).
See the System Event Log for more information.)

What mean code 21?

Thanks!
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Mon Apr 05, 2021 5:23 pm

Hi,

That error code means that StarWind Service could not reach to the IMG for some time. Now, as disks are available the issue must be gone.
Was that the only event causing the concern OR is there something else?
gklpnd
Posts: 14
Joined: Wed Mar 04, 2020 2:38 pm

Tue Apr 06, 2021 9:38 am

No more errors in logs, just this one. It repeating when i trying to mount this storage on client side.

I restarted starwind service, storage mounted without errors and all data exists :)

Thanks.
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Tue Apr 06, 2021 10:25 am

Glad to know that it is working. Thanks for letting me know.
Does it occur when you mount the StarWind HA device to the client side? Does it ultimately connect?
gklpnd
Posts: 14
Joined: Wed Mar 04, 2020 2:38 pm

Tue Apr 06, 2021 10:44 am

On that enclouser was just one flat device (for backup of backups).
HA devices located on hdds that connected directly in server, they worked and working without errors.
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Tue Apr 06, 2021 11:08 am

Correct me if I'm wrong.
That image file is on a separate piece of hardware. When that hardware is restarted you get this alert. Once the server is up you need to restart the StarWind VSAN service and everything is working fine again.
If that's the case, that is expected as img file and headers "disappear" and StarWind VSAN is to be restarted to "see" them again.

If that is an enclosure in the same server and an issue occurs on the host restart, please check storage health with the hardware vendor and set the timeout for StarWind VSAN start (2 mins should be fine).
gklpnd
Posts: 14
Joined: Wed Mar 04, 2020 2:38 pm

Wed Apr 07, 2021 10:52 am

That image file is on a separate piece of hardware. When that hardware is restarted you get this alert.
Yes, you are right.
If that is an enclosure in the same server and an issue occurs on the host restart, please check storage health with the hardware vendor and set the timeout for StarWind VSAN start (2 mins should be fine).
Timout not necessary, because separate enclosure detected by raid controller at BIOS stage.
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Wed Apr 07, 2021 11:07 am

Thanks for the update.
Let me know if there is anything I can help you with.
Post Reply