Error: <bootdev>: disk read error, sector 0
I have tried to install Solaris x86 8 and 9 on a Dell Poweredge 750. Both OSes install successfully but after CD 1, when the system attempts to boot from the new X86_BOOT partition on the hard disk, it does not get beyond the secondary boot loader. I get a screen stating:
SunOS Secondary Boot version v3.00
WARNING: ACPI tables not in Reclaim Memory
<bootdev>: disk read error, sector 0
After this, the boot drops into the debugger with a "prom_panic: unable to mount filesystem".
The hard disk is an SATA one but is working in PATA compatibility mode fine (has to be; the OS installed, right?)
Also, if I boot into the DCA from CD, do the device probe and then select to boot from the hard disk, Solaris boots fine!
Anyone any ideas why this may be happening and how it might be fixed? It will be a pain to have to always use the DCA to boot this machine.
(Oh, and it definitely isn't a physical problem with the disk - a Linux install worked fine on the same disk).
[1047 byte] By [
OranKelly] at [2007-11-25 22:55:12]
# 1
well im only guessing here , but its obviously something wrong with the boot loader installation.
Linux boots diffeerently to solaris, it boots a ramdisk version of itself first, starts up the device drivers, and then remounts itself on the disk.
the bootloader needs to setup the hardware correctly before starting up.
now this acpi error could be the issue, or it could be that old plug and play issue that i keep going on about.
if you can try disabling acpi in the bios.
but as an alternative see if the plug and play OS installed = yes option has been set and change it to NO.
solaris canot sort out all the hardware like windoze can, it expects the bios to do this.
these are the two things i would try first, if not then move on.
regards peter
# 2
you might want to email this guy, from this recent nntp/news artical, as he says hes got it working.
regards peter
<a href="http://groups.google.co.uk/group/comp.unix.solaris/browse_thread/thread/e 5f6fc5181f7bf85/c756d29ef231e66b?q=Dell+Poweredge+750+solaris+x86&rnum=1 &hl=en#c756d29ef231e66b" target="_blank"> http://groups.google.co.uk/group/comp.unix.solaris/browse_th read/thread/e5f6fc5181f7bf85/c756d29ef231e66b?q=Dell+Powered ge+750+solaris+x86&rnum=1&hl=en#c756d29ef231e66b</a>
# 3
I'm in agreement regarding it being "something" with plug-and-play / bus configuration...my guess is that the DCA device probe does some configuration or initialisation which neither the primary nor secondary boot loader does, meaning the hard disks are not properly accessible at boot time.
Another possiblity that just struck me; in Linux, the CD drive (which is ATAPI) is assigned hda and the hard disk hdc - I guess the system gives priority to the ATA interface over SATA. I might try disabling the ATA interface in the BIOS - perhaps Solaris doesn't like the hard disk not coming first...?
It would also be interesting to try the newer boot loader (4.02 vs. 3.00) from S10 to boot up S8, see if the version change made a difference (straw clutching? Moi?) but my searches thus far have not turned up any useful information on whether this might be possible or not. Anyone know of anyone that tried this?
(Regarding BIOS settings; the system does not have a setting to disable ACPI, and "Plug and play OS" went out with the square wheel, didn't it? :) Anyway, no such setting either)
oran
# 5
Hello Mr Oran!
We have such problem on Intel server mainboard.
But the "warning" message is not shown.
We try to apply some patches but problem still exist.
Booting from floppy or CD ok!
Note: the running of "Configuration Assistant" from floppy or CD takes few minutes.
When server try to boot from HDD the bulb on HDD blinks intensively few minutes before error messages shown.
I think that the problem is with HDD. If you have some ideas please answer me!
Thans, Sergey Bogomolov
