Can 18.04.1 be installed without access to internal hd?
I'm trying to install 18.04.1 on a laptop with an MMC harddrive, using USB Live on a thumb drive. The ultimate goal is to dual boot from an external drive, or perhaps a micro SD card.
The live image won't load, apparently due to errors in initializing the MMC and reading/writing? to the MMC. (the MMC works fine with Windows 10).
Is there a parameter which could be added to the grub entry which would exclude the MMC from access by the installer?
For reference, here are the error messages which first occur when selecting the "try Ubuntu" entry in the USB stick menu:
mmc_select_hs400 failed, error -84
error -84 whilst initializing MMC card
error -110...
and similar errors later addressing "mmcblk0"
Update Sept 9, 2018
This is relevant background only:
It appears that you cannot reliably run the live USB in 18.04.1 if your "main" disk is not accessible. I've tried several approaches -- and captured the dmesg log twice. Even when you have two USB drives, both discovered -- one the Live USB, and the other as the installation target -- it appears that if you have errors or access issues on the main disk (in my case an MMC), the install attempt will probably fail. One form of failure is an infinite loop attempting to access the MMC, the other form is the MMC not accessible, the live USB still getting to the point of recognizing all the other hardware, and then finishing with
(initramfs) Unable to find a medium containing a live file system
BTW, once I managed (by luck) to install 18.04.1 on an SD card, the installation had no trouble accessing the main drive (MMC). Additionally, Windows 10 has been completely happy with the MMC through all my attempts.
boot system-installation 18.04 live-usb
|
show 1 more comment
I'm trying to install 18.04.1 on a laptop with an MMC harddrive, using USB Live on a thumb drive. The ultimate goal is to dual boot from an external drive, or perhaps a micro SD card.
The live image won't load, apparently due to errors in initializing the MMC and reading/writing? to the MMC. (the MMC works fine with Windows 10).
Is there a parameter which could be added to the grub entry which would exclude the MMC from access by the installer?
For reference, here are the error messages which first occur when selecting the "try Ubuntu" entry in the USB stick menu:
mmc_select_hs400 failed, error -84
error -84 whilst initializing MMC card
error -110...
and similar errors later addressing "mmcblk0"
Update Sept 9, 2018
This is relevant background only:
It appears that you cannot reliably run the live USB in 18.04.1 if your "main" disk is not accessible. I've tried several approaches -- and captured the dmesg log twice. Even when you have two USB drives, both discovered -- one the Live USB, and the other as the installation target -- it appears that if you have errors or access issues on the main disk (in my case an MMC), the install attempt will probably fail. One form of failure is an infinite loop attempting to access the MMC, the other form is the MMC not accessible, the live USB still getting to the point of recognizing all the other hardware, and then finishing with
(initramfs) Unable to find a medium containing a live file system
BTW, once I managed (by luck) to install 18.04.1 on an SD card, the installation had no trouble accessing the main drive (MMC). Additionally, Windows 10 has been completely happy with the MMC through all my attempts.
boot system-installation 18.04 live-usb
Try disabling fast boot in Windows 10.
– user68186
Sep 7 '18 at 20:09
Thanks, I tried that -- but still had problems. Since I wrote this question, I tried just to capture the errors, and I found that itermittingly, couldl get all the way to live screen.
– CliffC
Sep 7 '18 at 22:47
From there I managed to put Ubuntu on an micro SD, and am now typing this in Ubuntu. Here is what I did on the SD -- I used the whole thing, and put boot records on the SD itself. So, now, I can boot the machine just using the SD, by using the boot menu in the BIOS. (the MMC did not even appear in the list of available drives)
– CliffC
Sep 7 '18 at 22:55
There are other possibilities. A. The MMC is formatted as a dynamic partition by Windows. B. The MMC is defined as a RAID drive in UEFI.
– user68186
Sep 7 '18 at 23:02
so in fact your problem is now solved?
– Tomáš Pospíšek
Sep 9 '18 at 20:46
|
show 1 more comment
I'm trying to install 18.04.1 on a laptop with an MMC harddrive, using USB Live on a thumb drive. The ultimate goal is to dual boot from an external drive, or perhaps a micro SD card.
The live image won't load, apparently due to errors in initializing the MMC and reading/writing? to the MMC. (the MMC works fine with Windows 10).
Is there a parameter which could be added to the grub entry which would exclude the MMC from access by the installer?
For reference, here are the error messages which first occur when selecting the "try Ubuntu" entry in the USB stick menu:
mmc_select_hs400 failed, error -84
error -84 whilst initializing MMC card
error -110...
and similar errors later addressing "mmcblk0"
Update Sept 9, 2018
This is relevant background only:
It appears that you cannot reliably run the live USB in 18.04.1 if your "main" disk is not accessible. I've tried several approaches -- and captured the dmesg log twice. Even when you have two USB drives, both discovered -- one the Live USB, and the other as the installation target -- it appears that if you have errors or access issues on the main disk (in my case an MMC), the install attempt will probably fail. One form of failure is an infinite loop attempting to access the MMC, the other form is the MMC not accessible, the live USB still getting to the point of recognizing all the other hardware, and then finishing with
(initramfs) Unable to find a medium containing a live file system
BTW, once I managed (by luck) to install 18.04.1 on an SD card, the installation had no trouble accessing the main drive (MMC). Additionally, Windows 10 has been completely happy with the MMC through all my attempts.
boot system-installation 18.04 live-usb
I'm trying to install 18.04.1 on a laptop with an MMC harddrive, using USB Live on a thumb drive. The ultimate goal is to dual boot from an external drive, or perhaps a micro SD card.
The live image won't load, apparently due to errors in initializing the MMC and reading/writing? to the MMC. (the MMC works fine with Windows 10).
Is there a parameter which could be added to the grub entry which would exclude the MMC from access by the installer?
For reference, here are the error messages which first occur when selecting the "try Ubuntu" entry in the USB stick menu:
mmc_select_hs400 failed, error -84
error -84 whilst initializing MMC card
error -110...
and similar errors later addressing "mmcblk0"
Update Sept 9, 2018
This is relevant background only:
It appears that you cannot reliably run the live USB in 18.04.1 if your "main" disk is not accessible. I've tried several approaches -- and captured the dmesg log twice. Even when you have two USB drives, both discovered -- one the Live USB, and the other as the installation target -- it appears that if you have errors or access issues on the main disk (in my case an MMC), the install attempt will probably fail. One form of failure is an infinite loop attempting to access the MMC, the other form is the MMC not accessible, the live USB still getting to the point of recognizing all the other hardware, and then finishing with
(initramfs) Unable to find a medium containing a live file system
BTW, once I managed (by luck) to install 18.04.1 on an SD card, the installation had no trouble accessing the main drive (MMC). Additionally, Windows 10 has been completely happy with the MMC through all my attempts.
boot system-installation 18.04 live-usb
boot system-installation 18.04 live-usb
edited Sep 9 '18 at 19:45
CliffC
asked Sep 7 '18 at 18:52
CliffCCliffC
513
513
Try disabling fast boot in Windows 10.
– user68186
Sep 7 '18 at 20:09
Thanks, I tried that -- but still had problems. Since I wrote this question, I tried just to capture the errors, and I found that itermittingly, couldl get all the way to live screen.
– CliffC
Sep 7 '18 at 22:47
From there I managed to put Ubuntu on an micro SD, and am now typing this in Ubuntu. Here is what I did on the SD -- I used the whole thing, and put boot records on the SD itself. So, now, I can boot the machine just using the SD, by using the boot menu in the BIOS. (the MMC did not even appear in the list of available drives)
– CliffC
Sep 7 '18 at 22:55
There are other possibilities. A. The MMC is formatted as a dynamic partition by Windows. B. The MMC is defined as a RAID drive in UEFI.
– user68186
Sep 7 '18 at 23:02
so in fact your problem is now solved?
– Tomáš Pospíšek
Sep 9 '18 at 20:46
|
show 1 more comment
Try disabling fast boot in Windows 10.
– user68186
Sep 7 '18 at 20:09
Thanks, I tried that -- but still had problems. Since I wrote this question, I tried just to capture the errors, and I found that itermittingly, couldl get all the way to live screen.
– CliffC
Sep 7 '18 at 22:47
From there I managed to put Ubuntu on an micro SD, and am now typing this in Ubuntu. Here is what I did on the SD -- I used the whole thing, and put boot records on the SD itself. So, now, I can boot the machine just using the SD, by using the boot menu in the BIOS. (the MMC did not even appear in the list of available drives)
– CliffC
Sep 7 '18 at 22:55
There are other possibilities. A. The MMC is formatted as a dynamic partition by Windows. B. The MMC is defined as a RAID drive in UEFI.
– user68186
Sep 7 '18 at 23:02
so in fact your problem is now solved?
– Tomáš Pospíšek
Sep 9 '18 at 20:46
Try disabling fast boot in Windows 10.
– user68186
Sep 7 '18 at 20:09
Try disabling fast boot in Windows 10.
– user68186
Sep 7 '18 at 20:09
Thanks, I tried that -- but still had problems. Since I wrote this question, I tried just to capture the errors, and I found that itermittingly, couldl get all the way to live screen.
– CliffC
Sep 7 '18 at 22:47
Thanks, I tried that -- but still had problems. Since I wrote this question, I tried just to capture the errors, and I found that itermittingly, couldl get all the way to live screen.
– CliffC
Sep 7 '18 at 22:47
From there I managed to put Ubuntu on an micro SD, and am now typing this in Ubuntu. Here is what I did on the SD -- I used the whole thing, and put boot records on the SD itself. So, now, I can boot the machine just using the SD, by using the boot menu in the BIOS. (the MMC did not even appear in the list of available drives)
– CliffC
Sep 7 '18 at 22:55
From there I managed to put Ubuntu on an micro SD, and am now typing this in Ubuntu. Here is what I did on the SD -- I used the whole thing, and put boot records on the SD itself. So, now, I can boot the machine just using the SD, by using the boot menu in the BIOS. (the MMC did not even appear in the list of available drives)
– CliffC
Sep 7 '18 at 22:55
There are other possibilities. A. The MMC is formatted as a dynamic partition by Windows. B. The MMC is defined as a RAID drive in UEFI.
– user68186
Sep 7 '18 at 23:02
There are other possibilities. A. The MMC is formatted as a dynamic partition by Windows. B. The MMC is defined as a RAID drive in UEFI.
– user68186
Sep 7 '18 at 23:02
so in fact your problem is now solved?
– Tomáš Pospíšek
Sep 9 '18 at 20:46
so in fact your problem is now solved?
– Tomáš Pospíšek
Sep 9 '18 at 20:46
|
show 1 more comment
1 Answer
1
active
oldest
votes
I have a similar problem (Installing Ubuntu on lenovo 130s / trouble eMMC) and in my case Ubuntu in live mode finally comes up!
It takes for a long time (~50minutes) with emmc error messages from time to time - but boots up finally.
I can't install ubuntu on the eMMC, but that's not what you intend anyway if I get your question correctly.
So just allow it long enough to finish the boot process. hope that helps
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1073189%2fcan-18-04-1-be-installed-without-access-to-internal-hd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have a similar problem (Installing Ubuntu on lenovo 130s / trouble eMMC) and in my case Ubuntu in live mode finally comes up!
It takes for a long time (~50minutes) with emmc error messages from time to time - but boots up finally.
I can't install ubuntu on the eMMC, but that's not what you intend anyway if I get your question correctly.
So just allow it long enough to finish the boot process. hope that helps
add a comment |
I have a similar problem (Installing Ubuntu on lenovo 130s / trouble eMMC) and in my case Ubuntu in live mode finally comes up!
It takes for a long time (~50minutes) with emmc error messages from time to time - but boots up finally.
I can't install ubuntu on the eMMC, but that's not what you intend anyway if I get your question correctly.
So just allow it long enough to finish the boot process. hope that helps
add a comment |
I have a similar problem (Installing Ubuntu on lenovo 130s / trouble eMMC) and in my case Ubuntu in live mode finally comes up!
It takes for a long time (~50minutes) with emmc error messages from time to time - but boots up finally.
I can't install ubuntu on the eMMC, but that's not what you intend anyway if I get your question correctly.
So just allow it long enough to finish the boot process. hope that helps
I have a similar problem (Installing Ubuntu on lenovo 130s / trouble eMMC) and in my case Ubuntu in live mode finally comes up!
It takes for a long time (~50minutes) with emmc error messages from time to time - but boots up finally.
I can't install ubuntu on the eMMC, but that's not what you intend anyway if I get your question correctly.
So just allow it long enough to finish the boot process. hope that helps
answered Mar 14 at 8:13
R ZaRR ZaR
113
113
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1073189%2fcan-18-04-1-be-installed-without-access-to-internal-hd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try disabling fast boot in Windows 10.
– user68186
Sep 7 '18 at 20:09
Thanks, I tried that -- but still had problems. Since I wrote this question, I tried just to capture the errors, and I found that itermittingly, couldl get all the way to live screen.
– CliffC
Sep 7 '18 at 22:47
From there I managed to put Ubuntu on an micro SD, and am now typing this in Ubuntu. Here is what I did on the SD -- I used the whole thing, and put boot records on the SD itself. So, now, I can boot the machine just using the SD, by using the boot menu in the BIOS. (the MMC did not even appear in the list of available drives)
– CliffC
Sep 7 '18 at 22:55
There are other possibilities. A. The MMC is formatted as a dynamic partition by Windows. B. The MMC is defined as a RAID drive in UEFI.
– user68186
Sep 7 '18 at 23:02
so in fact your problem is now solved?
– Tomáš Pospíšek
Sep 9 '18 at 20:46