Solved System no loner boots completely

userxbw

userxbw

this is what I did, I removed Linux on my extended side keeping windows and FreeBSD on the primary,
Using what partitions I had on the extended side, I used the first two partitions to installed a Linux on it then repositioned my partitions on that side to rid myself of two other Linux distros, leaving the primary side alone.

then I set up my grub 40_custom like its suppose to be, updated grub, booted into FreeBSD to see if it works, which it did, it going into the first boot screen, hit enter it boots then it gets to the USB ports part finding them then sits there, hit enter then it takes me to a # root prompt.

whoami
root
and I have no idea what to do from there because it is not completely booting as usual.

I'd like to fix it in lue of reinstalling the system. Any ideas or more need information on this let me know and I will provide what I can.
 
Some error during boot is putting you into single user mode. In that mode, root is automatically logged in (that's why you have a "#" prompt, and whoami says that you are root). The reason you got into single user is that boot can not proceed. Usually, that's because file systems are missing.

What is your file system situation? What file systems did you have before you changed things? When you are in single user mode, can you say "mount" and see what is mounted? Do you know your partition table, and are all necessary partitions still being found?

Most importantly: the system doesn't drop you into single user mode for no reason, it gives an error message. What are the error messages you get before the prompt? You may have to scroll back in the console buffer.
 
Everything in one slice that it partitioned out for swap and / with /home attached, not a split system.

I did not touch that side of the PCIe ssd card . it is the primary side of it. I just took the extended side and used what partitions I already had and re-installed a distro and removed the others by reszing them on that die of the partitions.

6967


after I turned off my sdcard and boot it I got this message. init 5623 can't exec ...

6968
 
userxbw said:
I just took the extended side and used what partitions I already had and re-installed a distro and removed the others by formatting the partitions
Click to expand...
I'm betting the numbers shifted and your /etc/fstab is still referring to the 'old' partition numbers.
 
SirDice said:
I'm betting the numbers shifted and your /etc/fstab is still referring to the 'old' partition numbers.
Click to expand...
That is why I did not delete the partitions to keep the numbering in sync. It goes read only and I am not knowing how to mount that again as rw to edit fstab .. but let me reboot this and go into FBSD and see if I can cat the fstab file. and ls /dev/ to see what I see. brb
 
mount -u /
mount -a -t ufs
swapon -a

That's assuming you have an UFS system. For ZFS:
zfs set readonly=off zroot/ROOT/default
zfs mount -a
swapon -a
 
SirDice said:
mount -u /
mount -a -t ufs
swapon -a

That's assuming you have an UFS system. For ZFS:
zfs set readonly=off zroot/ROOT/default
zfs mount -a
swapon -a
Click to expand...
thanks, that looks to be the issue, I removed all of the mount points except / and /home in linux fstab's before playing around and changing things, and I completely forgot about FBSD and that ext4 partition on the very end I had mounted as storage.
that is the one that the number got changed.

let me write these command down and edit that fstab file, brb..

thanks.
 
You must log in or register to reply here.
Back
Top