You are not logged in.
Pages: 1
I just finished the install on my laptop. Everything seemed to go as expected, no errors that I saw. So I rebooted and I get an error I really did not expect
"Non-System disk or disk error
replace and strike any key when ready"
Oh fudge, says I (or words to that affect) and I insert the cd and hit any key.
The cd spins up and I get to the Arch Linux boot menu. I had not seen the "Boot existing OS" choice before so I try it. And then I get the boot boot menu I was expecting (the simple blue and white one that syslinux created during the install. It boots the way I expect it too and now I'm at a command prompt.
This is really odd. Did I miss a step somewhere?
I'm not familiar with cgdisk, was there something I was supposed to do to make the partition bootable?
for /dev/sda I have
1007.0 KiB free space
1 465.8 GiB Linux filesystem Linux filesystem
That seems right to me, but I'm clearly not an expert.
Thanks in advance.
Last edited by dlbarron28 (2014-04-24 11:06:43)
Offline
What's the free space? Is this UEFI or BIOS booting? If BIOS (or whatever the proper name for non-UEFI is) then the partition does need to be marked as bootable - if it isn't, that would lead to the symptoms you describe.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
It could be a incorrect boot order in bios settings. Did you check that your primary hdd is the first in boot order ?
Offline
What's the free space? Is this UEFI or BIOS booting? If BIOS (or whatever the proper name for non-UEFI is) then the partition does need to be marked as bootable - if it isn't, that would lead to the symptoms you describe.
It is BIOS. There is 435Gig free on the disk
Last edited by dlbarron28 (2014-04-23 17:53:16)
Offline
It could be a incorrect boot order in bios settings. Did you check that your primary hdd is the first in boot order ?
I assume it is first, Windows was on this machine before and it booted without a problem.
Offline
For the free space, I was asking about the 1007KB free space (unpartitioned) listed in your output. But much more important is the boot flag - I suspect that is the issue.
Last edited by Trilby (2014-04-23 18:10:54)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
For the free space, I was asking about the 1007KB free space (unpartitioned) listed in your output. But much more important is the boot flag - I suspect that is the issue.
How do I set the boot flag?
Offline
There are various ways. Paritioning tools often can, but if you followed the Beginner's guide, the steps in setting up the boot loader would have included this. This then depends on which bootloader you chose.
You indicated that you installed syslinux - so generally the `syslinux-install_update -i -a -m` command would take care of this (that's the job of the -a flag).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
There are various ways. Paritioning tools often can, but if you followed the Beginner's guide, the steps in setting up the boot loader would have included this. This then depends on which bootloader you chose.
You indicated that you installed syslinux - so generally the `syslinux-install_update -i -a -m` command would take care of this (that's the job of the -a flag).
I did follow the beginners guide and I did that step. Should I do it again? Will it cause a problem if I run it a second time?
Offline
Trilby wrote:There are various ways. Paritioning tools often can, but if you followed the Beginner's guide, the steps in setting up the boot loader would have included this. This then depends on which bootloader you chose.
You indicated that you installed syslinux - so generally the `syslinux-install_update -i -a -m` command would take care of this (that's the job of the -a flag).
I did follow the beginners guide and I did that step. Should I do it again? Will it cause a problem if I run it a second time?
I tried the command again I am still getting the same issue.
Offline
Well, life keeps getting stranger. I went through the install again, I used fdisk to create the partition and made it bootable, ran through all of the steps again only this time I chose Grub for the bootloader. Installed perfectly, booted correctly.
Looks like it's working fine now, I just need to figure out how to issue the "rfkill unblock all" command automatically now.
Offline
This is another issue, wich have been discussed a lot
If i understand correctly, you problem is gone.
You should mark this thread as solved.
I am trying to but the process isn't apparent. Can someone explain how it's done?
Offline
by editing your first post.
Offline
Pages: 1