I tried installing both FreeBSD and PC-BSD, same error with both.
The PC is a desktop AMD64 a few years old (non-EFI bios). I have two hard drives: One SATA and one ATA. The SATA drive has Linux on it. The ATA drive also has Linux on it, but with plenty of free space to spare.
So I am trying to install onto the ATA drive, but using MBR partitioning to preserve the Linux.
It seems to partition OK with a slice containing /, swap and so on, and I tried defaults and custom arrangements. The partitioning stage seems OK. But after that, looks like during the file copying stage, something is wrong. I get these:
"Input/Output error". "Couldn't create directory /dist: read-only file system."
"error mounting /dev/cd0 on /dist"
Why is / not writable?
I tried everything I could. Even running sysinstall instead of the newer bsdinstall and examining and trying various the install options. The 'source' option says CDROM and the 'install path' option says / Partitioning also installs a brain-dead boot screen listing the available boots: Pressing any key simply results in '#' characters as in "Boot: ############" and weirdly, the '#' characters are appearing by themselves randomly about once every few seconds. The random characters suggest that it is receiving input from some place other than the keyboard, like my modem or mouse.
I'm glad I have my main Linux disk attached as well because its boot loader is still working. However as I mentioned I have a Linux partition on the BSD drive
as well, and when I choose to boot it hangs shortly after, and I discovered that I have to delete the BSD partition in order to be able to boot that Linux partition.
In fact the PC-BSD CD, and possibly FreeBSD, actually freeze up right at the beginning when the spinning "\" appears if a BSD partition already exists - I have to delete it in order to boot up the install CD/DVDs.
Does BSD not like MBR partitioning schemes? Does it not play well with Linux partitions and bootloaders? I will see what drive I can completely wipe and try BSD's own partitioning scheme.
Any help appreciated. Thanks.
Tim.
The PC is a desktop AMD64 a few years old (non-EFI bios). I have two hard drives: One SATA and one ATA. The SATA drive has Linux on it. The ATA drive also has Linux on it, but with plenty of free space to spare.
So I am trying to install onto the ATA drive, but using MBR partitioning to preserve the Linux.
It seems to partition OK with a slice containing /, swap and so on, and I tried defaults and custom arrangements. The partitioning stage seems OK. But after that, looks like during the file copying stage, something is wrong. I get these:
"Input/Output error". "Couldn't create directory /dist: read-only file system."
"error mounting /dev/cd0 on /dist"
Why is / not writable?
I tried everything I could. Even running sysinstall instead of the newer bsdinstall and examining and trying various the install options. The 'source' option says CDROM and the 'install path' option says / Partitioning also installs a brain-dead boot screen listing the available boots: Pressing any key simply results in '#' characters as in "Boot: ############" and weirdly, the '#' characters are appearing by themselves randomly about once every few seconds. The random characters suggest that it is receiving input from some place other than the keyboard, like my modem or mouse.
I'm glad I have my main Linux disk attached as well because its boot loader is still working. However as I mentioned I have a Linux partition on the BSD drive
as well, and when I choose to boot it hangs shortly after, and I discovered that I have to delete the BSD partition in order to be able to boot that Linux partition.
In fact the PC-BSD CD, and possibly FreeBSD, actually freeze up right at the beginning when the spinning "\" appears if a BSD partition already exists - I have to delete it in order to boot up the install CD/DVDs.
Does BSD not like MBR partitioning schemes? Does it not play well with Linux partitions and bootloaders? I will see what drive I can completely wipe and try BSD's own partitioning scheme.
Any help appreciated. Thanks.
Tim.