[Solved] 2.2.4 i386: cant boot into fresh install
-
Hello,
i can't boot a fresh installed system (quick install)
uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 8 ports with 8 removable, self powered ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: <toshiba mk1032gsx="" as021g="">ATA-6 SATA 1.x device ada0: Serial Number 863I9210T ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) ada0: 0MB (0 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ufsid/55c47aec1d3cffbb [rw]... mountroot: waiting for device /dev/ufsid/55c47aec1d3cffbb ... Mounting from ufs:/dev/ufsid/55c47aec1d3cffbb failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ufsid/55c47aec1d3cffbb vfs.root.mountfrom.options=rw Manual root filesystem specification: <fstype>: <device>[options] Mount <device>using filesystem <fstype>and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) <empty line="">Abort manual input mountroot> ? List of GEOM managed disk devices: ada0 mountroot> ufs:/dev/ada0s1a Trying to mount root from ufs:/dev/ada0s1a []... mountroot: waiting for device /dev/ada0s1a ... Mounting from ufs:/dev/ada0s1a failed with error 19. mountroot> ufs:/dev/ada0s1b Trying to mount root from ufs:/dev/ada0s1b []... mountroot: waiting for device /dev/ada0s1b ... Mounting from ufs:/dev/ada0s1b failed with error 19. mountroot> ufs:/dev/ada0s1 Trying to mount root from ufs:/dev/ada0s1 []... mountroot: waiting for device /dev/ada0s1 ... Mounting from ufs:/dev/ada0s1 failed with error 19. mountroot></empty></fstype></device></device></fstype></toshiba>any ideas?
-
oh no, it seems that 2.2.4 doesn't output Error Messages to the console
this is what i get with 2.1.5:
ad0: 0MB <toshiba mk1032gsx="" as021g="">at ata0-master UDMA100 SATA ugen4.1: <intel>at usbus4 uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4 uhub0: 2 ports with 2 removable, self powered ad0: FAILURE - READ_DMA48 status=51 <ready,dsc,error>error=10 <nid_not_found>LBA =18446744073709551613 uhub1: 2 ports with 2 removable, self powered ad0: FAILURE - READ_DMA status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=1 8446744073709551599 uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered ad0: FAILURE - READ_DMA status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=1 8446744073709551612 ad0: FAILURE - READ_DMA status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=1 8446744073709551615 ad0: FAILURE - READ_DMA status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=1 8446744073709551615 ad0: FAILURE - READ_DMA48 status=51 <ready,dsc,error>error=10 <nid_not_found>LBA =18446744073709551553 uhub4: 8 ports with 8 removable, self powered SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad0s1a ROOT MOUNT ERROR:</nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></intel></intel></toshiba>the hdd controller is faulty :-)
-
the hdd controller is faulty :-)
Is this a SSD? Were you setting up the AHCI mode in the BIOS?
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.