Volsnap error 16 #149
Comments
|
Hello @Lior97, Can you give some details on There might be an issue related to https://cloudbase-init.readthedocs.io/en/1.1.6/plugins.html#san-policy-config-main, but I need more information on how to reproduce the issue. Thank you, |
|
In the config file of the cloudbase there's a line that enables the
metadata, when i comment it the shadow copies doesn't disappear afer reboot.
Also when we disable the cloudbase service we manage to keep the copies.
בתאריך יום ב׳, 5 באוג׳ 2024, 11:02, מאת Adrian Vladu <
***@***.***>:
… Hello @Lior97 <https://github.com/Lior97>,
Can you give some details on the comment the line of the metadata in the
config file ? Also, if you can give more details on how to reproduce the
issue.
There might be an issue related to
https://cloudbase-init.readthedocs.io/en/1.1.6/plugins.html#san-policy-config-main,
but I need more information on how to reproduce the issue.
Thank you,
Adrian Vladu
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4JQEHON34RYQRT7PGQDV3ZP4WSJAVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGQZDMMJVGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
metadata_services=cloudbaseinit.metadata.services.configdrive.ConfigDriveService,
בתאריך יום ב׳, 5 באוג׳ 2024, 11:17, מאת LioR ***@***.***>:
… In the config file of the cloudbase there's a line that enables the
metadata, when i comment it the shadow copies doesn't disappear afer reboot.
Also when we disable the cloudbase service we manage to keep the copies.
בתאריך יום ב׳, 5 באוג׳ 2024, 11:02, מאת Adrian Vladu <
***@***.***>:
> Hello @Lior97 <https://github.com/Lior97>,
>
> Can you give some details on the comment the line of the metadata in the
> config file ? Also, if you can give more details on how to reproduce the
> issue.
>
> There might be an issue related to
> https://cloudbase-init.readthedocs.io/en/1.1.6/plugins.html#san-policy-config-main,
> but I need more information on how to reproduce the issue.
>
> Thank you,
> Adrian Vladu
>
> —
> Reply to this email directly, view it on GitHub
> <#149 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AR4JQEHON34RYQRT7PGQDV3ZP4WSJAVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGQZDMMJVGQ>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
Can you also share the cloudbase-init configuration files and logs when the issue appears? Also, if you can share how the shadow copied were created, to try to reproduce the issue. |
|
Conf file :
[DEFAULT]
metadata_file=meta_data.json
userdata_file=user_data
username="NT AUTHORITY\SYSTEM"
groups=Administrators
first_logon_behaviour=no
check_latest_version=false
enable_automatic_updates=false
stop_service_on_exit=false
cdrom=true
bsdtar_path=C:\Program Files\Cloudbase
Solutions\Cloudbase-Init\bin\bsdtar.exe
mtools_path=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\bin\
verbose=true
debug=true
log_dir=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log\
log_file=cloudbase-init.log
default_log_levels=comtypes=INFO,suds=INFO,iso8601=WARN,requests=WARN
userdata_save_path=C:\Windows\Temp\CloudBaseData
metadata_services=cloudbaseinit.metadata.services.configdrive.ConfigDriveService,cloudbaseinit.metadata.services.base.EmptyMetadataService
plugins=cloudbaseinit.plugins.common.userdata.UserDataPlugin
the cloudbase log i`ll send later, my co-worker working on another thing
right now and he cant focus on that atm.
…On Mon, 5 Aug 2024 at 11:46, Adrian Vladu ***@***.***> wrote:
Can you also share the cloudbase-init configuration files and logs when
the issue appears? Also, if you can share how the shadow copied were
created, to try to reproduce the issue.
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4JQEHB6RTQNOG67VMZ2NTZP43VRAVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGUYDQOBSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks. I have tried to reproduce the issue, but could not so far, all the extra volumes I added were showing the shadow copies fine after cloudbase-init run and a reboot. |
|
which os version do you using?
…On Mon, 5 Aug 2024 at 13:38, Adrian Vladu ***@***.***> wrote:
Thanks. I have tried to reproduce the issue, but could not so far, all the
extra volumes I added were showing the shadow copies fine after
cloudbase-init run and a reboot.
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4JQEEIZEGH7WXXSY2YQDLZP5I2PAVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYG42TINRVHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I ran a small test with the 10.0.20348 Windows Server 2022 Datacenter trial version. To continue the debug, please provide the following:
Once we have the full information, I can try to better reproduce it. |
|
OS Version : 10.0.20348
Disk info : Thin/Thick (Didn`t work with both), Virtualized, qcow2 , GPT (also tried both MBR and GPT)
Windows image: cloudbase, vm-tools , qemu-agent installations + sysprep
(also tried shadow copy without sysprep and didnt work)
The error message that I see in the event viewer after restart is this :
Volsnap 16: “The shadow copies of volume D: were aborted because D: which
contains storage for this shadow copy was force dismounted”
This problem happens in every boot, if i disable cloudbase service/comment
the metadata in the config file it doesn't happen.
P.S The deletion of the shadow copies effect only for new added disks
(doesn't happen on C), after reboot I cant see the copy but I can see it
takes place on the disk.
…On Mon, 5 Aug 2024 at 15:39, Adrian Vladu ***@***.***> wrote:
which os version do you using?
… <#m_5028423060229492875_>
On Mon, 5 Aug 2024 at 13:38, Adrian Vladu *@*.*> wrote: Thanks. I have
tried to reproduce the issue, but could not so far, all the extra volumes I
added were showing the shadow copies fine after cloudbase-init run and a
reboot. — Reply to this email directly, view it on GitHub <#149 (comment)
<#149 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR4JQEEIZEGH7WXXSY2YQDLZP5I2PAVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYG42TINRVHA
<https://github.com/notifications/unsubscribe-auth/AR4JQEEIZEGH7WXXSY2YQDLZP5I2PAVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYG42TINRVHA>
. You are receiving this because you were mentioned.Message ID: @.*>
I ran a small test with the 10.0.20348 Windows Server 2022 Datacenter
trial version. To continue the debug, please provide the following:
- OS version (systeminfo.exe)
- disk information (get-diskdrive) + details on what the disk type is,
how the disks are attached or detached during boot / after boot. Also, any
details if your environment is baremetal or virtualized (disk types,
virtualization type, etc). More, the better.
- how the Windows image has been created and if there is any special
customization related the SAN policy(diskpart> san).
- cloudbase-init logs
- any other information that you consider to be relevant to be able to
reproduce the environment and the issue
- what is the error message (or printscreen) and what is the desired
outcome
- is the issue happening at every boot or just happens in certain
conditions?
Once we have the full information,
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4JQEHWQW7UEWJD3LMIFC3ZP5XA3AVCNFSM6AAAAABLTT4ACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYHE3TQMRXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
The cloudbase-init service should not do in any way a force dismount of the disk. One possibility, from the config file you shared, is that the only enabled plugin might do something: Also, is it possible to share the userdata script that is being run? |
|
conf: og: packages\cloudbaseinit\metadata\services\osconfigdrive\windows.py:204 the cloudbase-init purpse for my goals is to run the powershell script that is in the user_data file and it's modules in the /openstack/content. |
|
Hello, From the logs that you shared, I do not see any possible causes for the force dismount of the Also, This key-value - Creating a working Windows image can get quite tedious at times, I might suggest using this tool https://github.com/cloudbase/windows-imaging-tools, as it automates the whole process of creating an image. Thanks. |
|
Thank you for the time you take for this. This is a fresh STD 22 OS with Cloudbase 1.1.6 updated conf file: |
When Im using cloudbase and create a shadow copy , when i restart my machine I get this error which tells me the disks I added getting force dismount which cause the deletion of the shadow copies I made.
When I comment the line of the metadata in the config file the shadow copies doesnt get deleted.
Any idea of what can fix it?
The text was updated successfully, but these errors were encountered: