Mount Root error on transferred hard disk
-
I forgot the screen dump. Below please.
mountroot> ?
List of GEOM mamanged disk devices:
ufsid/50d7c12294b75762 ad4s1b ad4s1a ad4s1 ad4
Loader variables:
vfa.root.mountfrom=ufs:/dev/ad6s1a
vfs.root.mountfrom.options=rwManual root filesystem specification:
<fstype>: <device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a
eg. cd9660:/dev/acd0
This is equivqlent to: mount -t cd9660 /dev/acd0 /about your question, what mobo info do you need? the one that broke down of the new one?</fstype></device></device></fstype>
-
CURRENT MOBO:
Intel(R) Core(TM)2 Duo E7500 @2.93GHz
MSI
MS-7592I am gona be using the onboard NIC plus another LAN Card.
This HD is one of the pf that I have installed directly to the HD (not VM).
-
Since all the managed devices are ad4 I'll assume that's where the HD is connected.
Start by trying at the mountroot> prompt:ufs:/dev/ad4s1a
If it boots successfully with that then edit the fstab to point at the correct locations once it's booted.
Steve
-
it rebooted but it encountered an error:
ad4: FAILURE - READ_DMA48 status=51 <ready, dsc,="" error="">error= <uncorrectable>LBA=100748… and alot of nubers.
does this mean it's a physical hard disk failure?</uncorrectable></ready,>
-
Not necessarily. It probably means it's trying to access the disk using some DMA mode but the disk or controller doesn't support it.
What disk/controller hardware are you using? Which pfSense install type? 32 or 64bit?
Steve
-
am using a SATA HDD.
-
OK, and what pfSense version and install type is on that disk?
Steve
-
2.0.3
Installed via USB -
Ah, sorry, by install type I meant is it a full install, standard kernel maybe a full install, embedded kernel or is it a NanoBSD image? Also is it 32 or 64bit? That's probably not relevant but it's good to get all the details so other users can spot things.
Steve
-
32bit
usbstick
standard kernel -
Ok.
Here's a thread describing a very similar (maybe identical) problem: http://forums.freebsd.org/showthread.php?t=18463
Not really a useful outcome though.I would try changing the HDD mode in the bios. If the SATA mode is set to AHCI try legacy or IDE compatible.
It could just be dead drive. Could be a bad cable or cable not inserted fully.
Steve