Windows / BIOS denies ubuntu installer access to /dev/sda1

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I just bought a Dell Optiplex 990 with Windows 7 installed on the only hard drive in the machine. When I live booted and tried to install Ubuntu 18.04, I only got to the part where the installer was going to erase the hard drive. It then displayed this error:



ERROR fysyncing/closing /dev/sda1: input/output error



I could go no farther. It just booted into Ubuntu.



I downloaded gparted and gparted did not recognize the hard drive. All it saw was the CD-ROM drive.



Windows still runs - meaning the hard drive works...



Please help...







share|improve this question




















  • I tried many things from the forums. Ultimately, I created a Windows Repair disk, booted to it and formatted the drive. Worked like a charm.
    – Dave
    May 10 at 12:37










  • Consider writing the solution as "Your Answer" in the box below. Then after the wait period, mark your answer as accepted by the green check mark next to it. This will help others in the future.
    – user68186
    May 10 at 12:39














up vote
0
down vote

favorite












I just bought a Dell Optiplex 990 with Windows 7 installed on the only hard drive in the machine. When I live booted and tried to install Ubuntu 18.04, I only got to the part where the installer was going to erase the hard drive. It then displayed this error:



ERROR fysyncing/closing /dev/sda1: input/output error



I could go no farther. It just booted into Ubuntu.



I downloaded gparted and gparted did not recognize the hard drive. All it saw was the CD-ROM drive.



Windows still runs - meaning the hard drive works...



Please help...







share|improve this question




















  • I tried many things from the forums. Ultimately, I created a Windows Repair disk, booted to it and formatted the drive. Worked like a charm.
    – Dave
    May 10 at 12:37










  • Consider writing the solution as "Your Answer" in the box below. Then after the wait period, mark your answer as accepted by the green check mark next to it. This will help others in the future.
    – user68186
    May 10 at 12:39












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I just bought a Dell Optiplex 990 with Windows 7 installed on the only hard drive in the machine. When I live booted and tried to install Ubuntu 18.04, I only got to the part where the installer was going to erase the hard drive. It then displayed this error:



ERROR fysyncing/closing /dev/sda1: input/output error



I could go no farther. It just booted into Ubuntu.



I downloaded gparted and gparted did not recognize the hard drive. All it saw was the CD-ROM drive.



Windows still runs - meaning the hard drive works...



Please help...







share|improve this question












I just bought a Dell Optiplex 990 with Windows 7 installed on the only hard drive in the machine. When I live booted and tried to install Ubuntu 18.04, I only got to the part where the installer was going to erase the hard drive. It then displayed this error:



ERROR fysyncing/closing /dev/sda1: input/output error



I could go no farther. It just booted into Ubuntu.



I downloaded gparted and gparted did not recognize the hard drive. All it saw was the CD-ROM drive.



Windows still runs - meaning the hard drive works...



Please help...









share|improve this question











share|improve this question




share|improve this question










asked May 8 at 19:35









Dave

1




1











  • I tried many things from the forums. Ultimately, I created a Windows Repair disk, booted to it and formatted the drive. Worked like a charm.
    – Dave
    May 10 at 12:37










  • Consider writing the solution as "Your Answer" in the box below. Then after the wait period, mark your answer as accepted by the green check mark next to it. This will help others in the future.
    – user68186
    May 10 at 12:39
















  • I tried many things from the forums. Ultimately, I created a Windows Repair disk, booted to it and formatted the drive. Worked like a charm.
    – Dave
    May 10 at 12:37










  • Consider writing the solution as "Your Answer" in the box below. Then after the wait period, mark your answer as accepted by the green check mark next to it. This will help others in the future.
    – user68186
    May 10 at 12:39















I tried many things from the forums. Ultimately, I created a Windows Repair disk, booted to it and formatted the drive. Worked like a charm.
– Dave
May 10 at 12:37




I tried many things from the forums. Ultimately, I created a Windows Repair disk, booted to it and formatted the drive. Worked like a charm.
– Dave
May 10 at 12:37












Consider writing the solution as "Your Answer" in the box below. Then after the wait period, mark your answer as accepted by the green check mark next to it. This will help others in the future.
– user68186
May 10 at 12:39




Consider writing the solution as "Your Answer" in the box below. Then after the wait period, mark your answer as accepted by the green check mark next to it. This will help others in the future.
– user68186
May 10 at 12:39















active

oldest

votes











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1033729%2fwindows-bios-denies-ubuntu-installer-access-to-dev-sda1%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1033729%2fwindows-bios-denies-ubuntu-installer-access-to-dev-sda1%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491