I get through the whole process of the install and when I’m on the last step my SD card just randomly removed itself and came back then the OSMC install said the dumb logs
What?
1 Like
Log file
I’m sorry but you don’t appear to be explaining clearly what the problem is.
This doesn’t make any sense.
Which OS are you running the install from?
I’m using the OSMC installer on my windows 10 laptop and when I get ready to fully install it my sad card all of a sudden acts as if it was removed and put back in. Then the OSMC installer says an error has occurred while writing the Image please consult log file. SOMEONE HELP PLEASE
Please create a single thread n future. Creating multiple threads slows down resolution.
Try another card.
Check the card makes a good connection with your PC.
Also, make sure you are running the installer as administrator.
I have the same problem as the Anthony_Jarvis with the 2017.12 version. The osmc installer is executed with administrator privileges as I have used it so many times, but in the last step where the SD card is selected it does not appear, when refreshing the screen appears but the installation fails… please consult log file.
This same process with the 2017.10 version works perfectly, so it seems the installer’s problem.
Tested on 2 different cards
Thank you,
What does the log file show?
Where would I find the log file
C:\User\$userfolder
It’s a long one and I can’t post all of it
I deleted the log file and clean the registred of windows. Now the install is ok
the log file now:
vi. 12. ene. 21:27:48 2018 OSMC Installer running on Windows
vi. 12. ene. 21:27:48 2018 Detected locale as es_ES
vi. 12. ene. 21:27:48 2018 Attempting to load translation for locale es_ES
vi. 12. ene. 21:27:48 2018 Could not load translation!
vi. 12. ene. 21:27:48 2018 Resolving a mirror
vi. 12. ene. 21:27:48 2018 Resolved mirror to http://mirrors.tuna.tsinghua.edu.cn/osmc/osmc/download/
vi. 12. ene. 21:27:48 2018 Enumerating supported devices
vi. 12. ene. 21:27:48 2018 Added the following devices
vi. 12. ene. 21:27:48 2018 Vero 4K
vi. 12. ene. 21:27:48 2018 Vero 2
vi. 12. ene. 21:27:48 2018 Vero
vi. 12. ene. 21:27:49 2018 Raspberry Pi 1 / Zero
vi. 12. ene. 21:27:49 2018 Raspberry Pi 2 / 3
vi. 12. ene. 21:27:49 2018 Apple TV
vi. 12. ene. 21:27:49 2018 Checking for updates
vi. 12. ene. 21:27:49 2018 Checking for updates by downloading http://mirrors.tuna.tsinghua.edu.cn/osmc/osmc/download//installers/latest_windows
vi. 12. ene. 21:27:51 2018 Acquired mirror file
vi. 12. ene. 21:27:51 2018 No new update is available
vi. 12. ene. 21:28:00 2018 The user has selected English as their language
vi. 12. ene. 21:28:00 2018 The user has selected Raspberry Pi 2 / 3 as their device
vi. 12. ene. 21:28:00 2018 Attempting to download device versions file http://mirrors.tuna.tsinghua.edu.cn/osmc/osmc/download/installers/versions_RBP2
vi. 12. ene. 21:28:01 2018 Found a build called 2017.12-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.10-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.08-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.07-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.06-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.05-2
vi. 12. ene. 21:28:01 2018 Found a build called 2017.04-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.03-1
vi. 12. ene. 21:28:01 2018 Found a build called 2017.02-2
vi. 12. ene. 21:28:01 2018 Found a build called 2017.01-1
vi. 12. ene. 21:28:06 2018 The user has selected an online image for Raspberry Pi 2 / 3 with build URL : http://mirrors.tuna.tsinghua.edu.cn/osmc/osmc/download/installers/diskimages/OSMC_TGT_rbp2_20180109.img.gz
vi. 12. ene. 21:28:06 2018 Disabling internal install for device Raspberry Pi 2 / 3 as it does not support it
vi. 12. ene. 21:28:09 2018 USB installation selected
vi. 12. ene. 21:28:10 2018 Installing usbit32 imaging binary to temporary path
vi. 12. ene. 21:28:10 2018 Installing empty boot sector to temporary path
vi. 12. ene. 21:28:10 2018 Installation was successful
vi. 12. ene. 21:28:10 2018 Enumerating imageable devices for Windows
vi. 12. ene. 21:28:10 2018 New disk device entry created with entry point F:, 7600MB free space and label
vi. 12. ene. 21:28:14 2018 Device selected: 2 F:\ 7600MB
vi. 12. ene. 21:28:17 2018 EULA has been accepted
vi. 12. ene. 21:28:17 2018 Downloading http://mirrors.tuna.tsinghua.edu.cn/osmc/osmc/download/installers/diskimages/OSMC_TGT_rbp2_20180109.img.gz
vi. 12. ene. 21:28:22 2018 Extracting C:/Users/Fran/OSMC_TGT_rbp2_20180109.img.gz
vi. 12. ene. 21:28:25 2018 Finished extraction. Going to write image
vi. 12. ene. 21:28:25 2018 Requesting confirmation from user
vi. 12. ene. 21:28:27 2018 User confirmed
vi. 12. ene. 21:28:27 2018 Workaround Windows 10 card protection
vi. 12. ene. 21:28:27 2018 Writing 512 bytes to erase MBR
vi. 12. ene. 21:28:30 2018 MBR is trashed. Now beginning imaging process.
vi. 12. ene. 21:29:04 2018 Image successfully written to device
vi. 12. ene. 21:29:04 2018 Deleting the uncompressed image to save space
vi. 12. ene. 21:29:04 2018 Creating preseeder
vi. 12. ene. 21:29:04 2018 Adding preseed stringd-i target/storage string usb
vi. 12. ene. 21:29:04 2018 Adding preseed stringd-i network/interface string eth
vi. 12. ene. 21:29:04 2018 Adding preseed stringd-i network/auto boolean true
vi. 12. ene. 21:29:04 2018 Writing preseeder
vi. 12. ene. 21:29:04 2018 ying to find device with id
vi. 12. ene. 21:29:04 2018 Enumerating imageable devices for Windows
vi. 12. ene. 21:29:04 2018 New disk device entry created with entry point F:, 7600MB free space and label
vi. 12. ene. 21:29:04 2018 Matched device to entry point F:
vi. 12. ene. 21:29:04 2018 Writing the preseeder to filesystem
vi. 12. ene. 21:29:05 2018 Finished.
So do I just copy this and replace the old log text with this one
this is my log
you, only delete log, the image, clean the registry of windows, and format the sd card in fat32.
then repeat the process