Win32DiskImager on Windows 10 and upgrading from 3.0.94

Howdy,

I'm currently running OMV version 3.0.94 and figure it's about time to upgrade.

I have 2 x 32GB SanDisk USB Thumb drives I use as a boot drive and backup and have used Win32DiskImager in the past to clone one to the other. However, I recently upgraded to Windows 10 and Win32DiskImager seems to want to present the USB Thumb drive as two partitions.

I've seen reference to this elsewhere and the instructions were to ignore the 2nd partition, point to the 1st partition and Win32DiskImager will figure capture the entire drive to an image.

Has anyone run into this? Been successful in using Win32DiskImager on Windows 10 as described without issues?

Edit: It took 2 hours to write a 32GB USB Thumb drive with Win32DiskImager, is there anything faster?

Any issues, prep, recommended procedures upgrading from 3.0.94 to the current stable release?

Note: I am also behind on any updates that might be available for 3.0.94. Update then upgrade?

Thanks,

daveinTN formerly daveinfla (can I change my username, if so, how will it affect my postings?)

Zitat von tkaiser

Why do you think the software would be to blame? Which write speeds did h2testw report when you tested the drives for fake capacity?

It must be Windows 10, it never took 2 hours on Windows 7 and it's the same thumb drive.

Zitat von macom

You can also use Clonezilla. But you have to boot clonezilla live.

Is Clonezilla faster then Win32DiskImager?

Zitat von KM0201

There might be some plugins in 3.0 that are no longer available in 4.0... so I'd verify your plugin compatibility..

I would update and then upgrade, but the end result will likely be the same either way.

How do you confirm compatibility?

I'm running the following plugins, will they automatically upgrade?

openmediavault-flashmemory 3.5

openmediavault-zfs 3.0.18

openmediavault-nut 3.2.12

openmediavault-omvextrasorg 3.4.29

Can someone point me to the process of kicking off an upgrade from OMV 3.0.99 to the latest version?

Thanks,

Zitat von macom

All of the ones you listed are available for OMV4.

If there all listed does it mean they'll auto upgrade or do I have to re-activate/install them under OMV4?

I'm running zfs, poking around the forums it appears there's an issue with zfs under OMV4?

Or has that been corrected?

The update to 3.0.99 didn't go so well, I've receiving the following e-mail notifications a couple times a day...

I'm also receiving a dump while trying to check for updates, that output follows the e-mail below...

CRON-APT RUN [/etc/cron-apt/config]: Sat Apr 6 07:35:15 EDT 2019
CRON-APT SLEEP: 3173, Sat Apr 6 08:28:08 EDT 2019
CRON-APT ACTION: 0-update
CRON-APT LINE: /usr/bin/apt-get -oAcquire::http::Dl-Limit=25 update -o quiet=2
W: Failed to fetch https://nam01.safelinks.protec…2NbE4bMeEh0%3D&reserved=0 Unable to find expected entry'main/source/Sources' in Release file (Wrong sources.list entry or malformedfile)

W: Failed to fetch https://nam01.safelinks.protec…pu%2Bh56Ww8%3D&reserved=0 404 Not Found

W: Failed to fetch https://nam01.safelinks.protec…FE5goA1UwiI%3D&reserved=0 404 Not Found

W: Failed to fetch https://nam01.safelinks.protec…2MFgV69A6qU%3D&reserved=0 404 Not Found

E: Some index files failed to download. They have beenignored, or old ones used instead.

DUMP

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; apt-get update 2>&1' with exit code '100': Ign file: InRelease Ign file: Release.gpg Ign file: Release Ign file: Translation-en Ign http://ftp.us.debian.org jessie InRelease Hit http://ftp.us.debian.org jessie-updates InRelease Hit http://ftp.us.debian.org jessie Release.gpg Hit http://ftp.us.debian.org jessie Release Hit http://security.debian.org jessie/updates InRelease Ign http://httpredir.debian.org jessie-backports InRelease Hit http://packages.openmediavault.org erasmus InRelease Hit http://ftp.us.debian.org jessie/main Sources Ign http://httpredir.debian.org jessie-backports Release.gpg Hit http://ftp.us.debian.org jessie/main amd64 Packages Hit http://ftp.us.debian.org jessie/main Translation-en Get:1 http://security.debian.org jessie/updates/main Sources [306 kB] Get:2 http://security.debian.org jessie/updates/contrib Sources [1439 B] Ign http://httpredir.debian.org jessie-backports Release Get:3 http://security.debian.org jessie/updates/non-free Sources [1631 B] Get:4 https://dl.bintray.com jessie InRelease Get:5 http://security.debian.org jessie/updates/main amd64 Packages [664 kB] Get:6 http://security.debian.org jessie/updates/contrib amd64 Packages [2506 B] Hit http://packages.openmediavault.org erasmus/main amd64 Packages Get:7 http://security.debian.org jessie/updates/non-free amd64 Packages [4556 B] Get:8 http://security.debian.org jessie/updates/contrib Translation-en [1211 B] Get:9 http://security.debian.org jessie/updates/main Translation-en [335 kB] Get:10 http://security.debian.org jessie/updates/non-free Translation-en [11.8 kB] Ign http://packages.openmediavault.org erasmus/main Translation-en Err http://httpredir.debian.org jessie-backports/main amd64 Packages 404 Not Found Err http://httpredir.debian.org jessie-backports/contrib amd64 Packages 404 Not Found Err http://httpredir.debian.org jessie-backports/non-free amd64 Packages 404 Not Found Ign http://httpredir.debian.org jessie-backports/contrib Translation-en Ign http://httpredir.debian.org jessie-backports/main Translation-en Ign http://httpredir.debian.org jessie-backports/non-free Translation-en Ign https://dl.bintray.com jessie InRelease Get:11 https://dl.bintray.com jessie InRelease Ign https://dl.bintray.com jessie InRelease Hit https://dl.bintray.com jessie Release.gpg Hit https://dl.bintray.com jessie Release.gpg Hit https://dl.bintray.com jessie Release Hit https://dl.bintray.com jessie Release Get:12 https://dl.bintray.com jessie/main amd64 Packages [36.4 kB] Get:13 https://dl.bintray.com jessie/main Translation-en Get:14 https://dl.bintray.com jessie/main amd64 Packages [19.1 kB] Get:15 https://dl.bintray.com jessie/main Translation-en Get:16 https://dl.bintray.com jessie/main Translation-en Get:17 https://dl.bintray.com jessie/main Translation-en Get:18 https://dl.bintray.com jessie/main Translation-en Get:19 https://dl.bintray.com jessie/main Translation-en Get:20 https://dl.bintray.com jessie/main Translation-en Get:21 https://dl.bintray.com jessie/main Translation-en Get:22 https://dl.bintray.com jessie/main Translation-en Ign https://dl.bintray.com jessie/main Translation-en Get:23 https://dl.bintray.com jessie/main Translation-en Ign https://dl.bintray.com jessie/main Translation-en Fetched 55.5 kB in 9s (5903 B/s) W: Failed to fetch http://ftp.us.debian.org/debia…/jessie-updates/InRelease Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://httpredir.debian.org/de…ain/binary-amd64/Packages 404 Not Found W: Failed to fetch http://httpredir.debian.org/de…rib/binary-amd64/Packages 404 Not Found W: Failed to fetch http://httpredir.debian.org/de…ree/binary-amd64/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead.

Any ideas?

Zitat von macom

There are many threads on this in the Updates/Upgrades section.
One of them:
3.0.99 (Erasmus) Update issues
or
omv-release-upgrade throws errors & stops

I would upgrade to OMV 4 if I had a definitive answers about zfs.

Have the issues with using zfs under OMV 4 been corrected?

Can I simply do a version upgrade?

I followed the steps outlined above to correct the issue with 3.0.99 and completed the upgrade to 4.1.21-1 (Arrakis), my zfs pool is up and my shares are accessible.

However there were two anomalies during the upgrade process.

It paused at one point and as you see from the last line of the following output it had issues related to zfs:

Setting up mawk (1.3.3-17+b3) ...
Setting up groff-base (1.22.3-9) ...
Installing new version of config file /etc/groff/man.local ...
Installing new version of config file /etc/groff/mdoc.local ...
Setting up libpipeline1:amd64 (1.4.1-2) ...
Setting up man-db (2.7.6.1-2) ...
Installing new version of config file /etc/cron.daily/man-db ...
Installing new version of config file /etc/cron.weekly/man-db ...
Installing new version of config file /etc/manpath.config ...
Updating database of manual pages ...
Setting up fuse (2.9.7-1+deb9u2) ...
update-initramfs: deferring update (trigger activated)
Setting up zfs-dkms (0.7.9-2) ...
Loading new zfs-0.7.9 DKMS files...
Building for 4.9.0-0.bpo.5-amd64
Building initial module for 4.9.0-0.bpo.5-amd64
/var/lib/dkms/zfs/0.7.9/build/configure: line 13069: dpkg-architecture: command not found

It then bombed at the end of this section, however it appears to be running. What do I need to do to clean this up?

Processing triggers for resolvconf (1.79) ...
Processing triggers for ca-certificates (20161130+nmu1+deb9u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for openmediavault (4.1.21-1) ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fad54bc3730>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fad54bc3730>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
W: Operation was interrupted before it could finish

Thanks,

Dave