After DL update zip file 3.1.4, I unzipped and saved to folder. The contents were copied to a flash drive . The only folder not copied were the PDF folder with multilingual pdfs.
Flashdrive inserted to the K2, going to global, the update option was selected.
The files on the stick were seen. Display read that 3
1.4 was being updated.
Then: error message : checksum error ... turn off.
So I removed the stick thinking the file was corrupt. Powered of then powered on and it booted to 3.1.2
What now... your thoughts...
Error update 3.1.2 to 3.1.4
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Error update 3.1.2 to 3.1.4
Kronos 2 88
M3 61 expanded
Triton Extreme 88 & 61
Triton PRO X 88
Trinity V3 61
O1WFD 61
T3 61
M1 61
03R
M3 61 expanded
Triton Extreme 88 & 61
Triton PRO X 88
Trinity V3 61
O1WFD 61
T3 61
M1 61
03R
-
AntonySharmman
- Approved Merchant
- Posts: 3733
- Joined: Sat Oct 16, 2010 2:24 pm
- Location: Hellas
- Contact:
Re: Error update 3.1.2 to 3.1.4
Do the following and will work :
- Place your Flashdrive in USB port of Kronos USB
- Format it via Kronos and place it back in your computer slot
- Open uncompressed folder of OS Update select all contained files there and copy them
in root of USB drive.
- Now you can safely Update Kronos
Your mistake is that installation PDF manual says
Hope this helps
- Place your Flashdrive in USB port of Kronos USB
- Format it via Kronos and place it back in your computer slot
- Open uncompressed folder of OS Update select all contained files there and copy them
in root of USB drive.
- Now you can safely Update Kronos
Your mistake is that installation PDF manual says
copy the update files and
sub-folder(s) to the root level of a FAT32-formatted
USB storage device, such as a USB flash drive
Hope this helps
Music Conductor - Sound Engineer & Developer - Automotive SMPS/RF R&D - Electronics Engineer
Keyboards : Steinway-D, Kronos X, Pa5X 76, Pa4X 76, Montage M7 , Roland-XV88, Emu3,Emax II, Synclavier II , Yamaha DX Series, ΟΒ-8V
wavesΑrt official webpage - KorgPa.gr
DEMO's Playlist - WavesArt Facebook
Keyboards : Steinway-D, Kronos X, Pa5X 76, Pa4X 76, Montage M7 , Roland-XV88, Emu3,Emax II, Synclavier II , Yamaha DX Series, ΟΒ-8V
wavesΑrt official webpage - KorgPa.gr
DEMO's Playlist - WavesArt Facebook
Re: Error update 3.1.2 to 3.1.4
For updating the OS, the files that should be visible in the root directory of the thumb drive used for the update, should look like this:
Manuals (dir)
mnt (dir)
bc
DisplayUpdaterMessage
install.info
KRONOS_Update_3_1_4.csum
KRONOS_Update_3_1_4.tar.gz
md5sum
posttar.sh
pretar.sh
.
Manuals (dir)
mnt (dir)
bc
DisplayUpdaterMessage
install.info
KRONOS_Update_3_1_4.csum
KRONOS_Update_3_1_4.tar.gz
md5sum
posttar.sh
pretar.sh
.
Re: Error update 3.1.2 to 3.1.4
My thanks go out to both of you!!! Update successful.
In DISK mode I formatted the USB stick in Fat32, then copied the entire unzipped update files and folders to its root directory first.
My thoughts were that either the KRONOS did not like PC formatted fat 32 disk or the fact that the PDF documents were missing from the collection, which caused the checksum error message.
THis reminds me of when My older KORG 01WFD preferred its own DS/DD DISKs formatted for SMF , rather than PC formatted 720K floppies.
In DISK mode I formatted the USB stick in Fat32, then copied the entire unzipped update files and folders to its root directory first.
My thoughts were that either the KRONOS did not like PC formatted fat 32 disk or the fact that the PDF documents were missing from the collection, which caused the checksum error message.
THis reminds me of when My older KORG 01WFD preferred its own DS/DD DISKs formatted for SMF , rather than PC formatted 720K floppies.
Kronos 2 88
M3 61 expanded
Triton Extreme 88 & 61
Triton PRO X 88
Trinity V3 61
O1WFD 61
T3 61
M1 61
03R
M3 61 expanded
Triton Extreme 88 & 61
Triton PRO X 88
Trinity V3 61
O1WFD 61
T3 61
M1 61
03R
Re: Error update 3.1.2 to 3.1.4
I completed the OS update from 3.1.2 to 3.1.4 .
However, all the uncompressed files were loaded into the root directory of the FAT32 formatted USB stick. The stick was loaded into K2 and the software update appeared to complete. The OS currently reported is 3.1.4.
IN my case the tar.gz file was included on that stick along with the rest.
Why does KORG request Tar.gz remain compressed , as seen on their video below?
https://www.youtube.com/watch?v=FYfGR8g ... z-&index=8
However, all the uncompressed files were loaded into the root directory of the FAT32 formatted USB stick. The stick was loaded into K2 and the software update appeared to complete. The OS currently reported is 3.1.4.
IN my case the tar.gz file was included on that stick along with the rest.
Why does KORG request Tar.gz remain compressed , as seen on their video below?
https://www.youtube.com/watch?v=FYfGR8g ... z-&index=8
Kronos 2 88
M3 61 expanded
Triton Extreme 88 & 61
Triton PRO X 88
Trinity V3 61
O1WFD 61
T3 61
M1 61
03R
M3 61 expanded
Triton Extreme 88 & 61
Triton PRO X 88
Trinity V3 61
O1WFD 61
T3 61
M1 61
03R
Re: Error update 3.1.2 to 3.1.4
Tarballs are archives of files and directories, and a .tar.gz file contains the archive compressed using gzip. These are commonly used in Linux/Unix software distributions, so Korg are simply using a standard method for updating the operating system which, in the case of the Kronos, is a customised version of Linux. The chances are that the software updates to your internet router, and mobile phone, are also sent as a single .tar.gz file, together with a checksum, or checksums, to verify that there is no corruption.
If a number of different users were to extract a particular tarball archive, there is a chance that the end result may produce slight differences in the resulting files, from one system to another. For example, the differences may lie in the way the file termination characters are implemented, but there have also historically been differences in files that are compiled binaries, causing subsequent problems when those binaries are executed. So the safest way to distribute and install a system update, is to send the package as a compressed tarball, and to use Linux's native tar command in the Kronos to perform the necessary file extraction required for a successful OS update.
.
If a number of different users were to extract a particular tarball archive, there is a chance that the end result may produce slight differences in the resulting files, from one system to another. For example, the differences may lie in the way the file termination characters are implemented, but there have also historically been differences in files that are compiled binaries, causing subsequent problems when those binaries are executed. So the safest way to distribute and install a system update, is to send the package as a compressed tarball, and to use Linux's native tar command in the Kronos to perform the necessary file extraction required for a successful OS update.
.