FN 8.3.1 Install boot won't finish 'enter: panic'

[Paul5]

Hi, I'll try to make this as concise as possible: unable to get beyond the install message below. Please see under it all for the things I have tried and still get pretty much the same faults. It's much appreciated, if someone could tell me how to rectify this. I'm assuming the fault is in there somewhere.

Sorry for the lack of occasional capitals and in general the first letter or letters on the left are missing. I don't see them on my screen.O' and I'm completely new, never installed it before.

****I'm assuming the problems start around here>

gen1.3: <generic> at usbus1
mass1: <bulk-in bulk-out, interface> on usbus1
probe0:umass-sim1:1:0:0)test unit ready. cdb:000000
probe0:umass-sim1:1:0:0)cam status: scsi status error
probe0:umass-sim1:1:0:0)scsi status: check condition
probe0:umass-sim1:1:0:0)scsi sense: not ready asc:3a,0 (medium not present)
probe0:umass-sim1:1:0:0)test unit ready. cdb: 0 20 0000
probe0:umass-sim1:1:0:0)cam status: scsi status error
probe0:umass-sim1:1:0:0)scsi status: check condition
probe0:umass-sim1:1:0:0)scsi sense: not ready asc:3a,0 (medium not present)
probe0:umass-sim1:1:0:0)test unit ready. cdb: 0 40 0000
probe0:umass-sim1:1:0:0)cam status: scsi status error
probe0:umass-sim1:1:0:0)scsi status: check condition
probe0:umass-sim1:1:0:0)scsi sense: not ready asc:3a,0 (medium not present)
probe0:umass-sim1:1:0:0)test unit ready. cdb: 0 60 0000
probe0:umass-sim1:1:0:0)cam status: scsi status error
probe0:umass-sim1:1:0:0)scsi status: check condition
probe0:umass-sim1:1:0:0)scsi sense: not ready asc:3a,0 (medium not present)
da0 at ata2 bus 0 scbus3 target 0 lun 0
da0: <hitachi hcs5c1050cla382 jc20a39c> ata-8 sata 2.X device
da0: 300.000mb/s transfers (sata 2.x, udma5, pio 8192bytes
da0: 476940MB (976773168 512 byte sectors: 16H 63s/t 16383C)
a0 at umass-sim0 bus 0 scbus7 target 0 lun 0
a0: <Sandisk cruzer pop 1.26> removable direct access scsi-5 device
a0: 40.000mb/s transfers
a0: 7633MB (15633408 512 byte sectors: 255H 63s/t 973c)
a1 at umass-sim1 bus 1 scbus8 target 0 lun 0
a1: <generic- compact flasch 1.00> removable direct access scsi-0 device
a1: 40.000mb/s transfers
a1: attempt to query device size failed: not ready, medium not present
a2 at umass-sim1 bus 1 scbus8 target 0 lun 0
a2: 40.000mb/s transfers
a2: attempt to query device size failed: not ready, medium not present
d0 <tsscorp cddvdw ts-h653n 0208> removable cd-rom scsi-0 device
d0: 150.000MB/s transfers (sata1.x udma2 atapi 12bytes, pio 8192 bytes)
d0: attempt to query device size failed: not ready, medium not present- tray c osed
a3: at umass-sim1 bus1 scbus8 target 0 lun 2
a3: <generic- sd/mmc 1.00> removable direct access scsi-0 device
a3: 40.000mb/s transfers
a3: attempt to query device size failed: not ready, medium not present
a4: at umass-sim1 bus 1 scbus8 target 0 lun3
a4: <generic- MS/MS-Pro 1.00> removable direct access scsi-0 device
a4: 40.000mb/s transfers
MP: AP cpu #1 launched!
a4: attempt to query divice size failed: not ready, medium not present
E)M: da0s1: geometry does not match label (16h,63s !=255h,63s).
trying to mount root from ufs:/dev/ufs/freeNASs1a
xec /sbin/init: error8
exec / rescue/init: error 8
nit: not found in path /sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stan/sysinstall
Panic: no init
puid = 1
DB: enter: panic
thread pid 1 tid 100002 ]
stopped at kdb_enter+0x3a mov1 $0,kdb_why
b>

Any ideas?

If I then type 'reset' it will reboot.

**************************************************
On a side note: if I boot up with the install on a hdd this is the error I get after an
a3: attempt to query device size failed : not ready, medium not present
loader variables:
fs.root.mountfrom:
fs.root.mountfrom.options=

anual root filesystem specification:
<fstype>:<device> mount <device> using filesystem <fstype>
eg. ufs:/dev/da0s1a
eg. cd9660:/dev/acd0
this is equivalent to:mount -t cd9660 /dev/acd0/
? list valid disk boot devices
<empty line abort manual input
ountroot>

I don't know how to reeboot from this one so I have to turn off the computer.

****************************************************

What I have tried:
1 different hdds also install into hard drive instead of usb stick
2 dirrernt usb flash drives
3 disconnecting what I could from the computer
4 tried FreeNas X32 (my system) FreeNas 64 and Nas4free. Same results
5 many hours looking through freenas helps including vids
6 I've also done checksums on the downloads and are correct.

Thanks.
P.S I really loved typing all that out.

 

[pttymuth]

I am having a similar experience. Using the methods outlined on the FreeNAS wiki, I've created a 8.3.1 x64 bootable flashdisk. Each time I attempt to boot, I get errors about being unable to mount the root filesystem. Furthermore, when I do mount said filesystem from the prompt you painstakingly typed out, I'm dropped down into an endless loop of the following:

init: _secure_path: cannot stat /etc/login.conf: Not a directory
init: login_getclass: unknown class 'daemon'
init: _secure_path: cannot stat /etc/login.conf: Not a directory
init: can't exec /bin/sh for /etc/rc: Not a directory
Enter full pathname of shell or RETURN for /bin/sh:

Hoping to find a resolution to this one. FreeNAS is way cool and I'd love to start using it on this expensive hardware I've got sitting around.

 

[survive]

Hi guys,

It would be helpful if you told us something about the hareware you are trying to run FreeNAS on.

-Will

 

[pttymuth]

I did some research and was able to fix the problem, boot successfully. I can't speak on behalf of the original poster, but in my case the flash drive wasn't formatted properly. I suppose that flash drive file systems are being sold in at least a few variations now, with the advent of Windows 8. Particularly, my flash drive must have come with a GPT parition table. As soon as I got the drive I dd'd the FreeNAS image directly to it. The MBR partition table on the FreeNAS image and the GPT partition table that came with the drive must have been incompatible. I read a post on here describing how to clear a GPT partition table from a flash drive by writing zeros to the first two and last two sectors of the drive. After doing this and rewriting the FreeNAS image to the drive, I was golden.

For most 'write and image using dd and boot from it' scenarios, I don't believe its common to have trouble in this area. Maybe the fact that I found the solution to the problem here on the FreeNAS forums speaks to that. I have some thoughts on it, but they might not be relevant at all here: Doesn't it seem obvious that if a GPT partition table is wiped out at the front of the flash drive and replaced with an MBR, the GPT data at the last sectors of the flash drive becomes 'as-good-as' zeroed? I also noticed that the FreeNAS image started partitions at sector 63 on my flash drive (when I got it working, I used bs=512.) Is there a reason why the FreeNAS partitions are located all the way back at sector 63? Why not at the beginning of the flash drive?

 

[pttymuth]

Unless anyone has any objections, I'll go ahead an make an edit to the Troubleshooting section on this Wiki page: http://doc.freenas.org/index.php/Burning_an_IMG_File