Very Computer

Now when I start this computer, I get a prompt:

mountroot>

I typed ufs:/dev/ad0s1a

and then I get a bunch of error messages as follow:

Warning:  / was not properly dismounted
swapon:  /dev/ad4s1b: Device not configured
...
Can't opeen /dev/ad4s1a: Device not configured
/dev/ad4s1a: Can't check file system
/dev/ad4s1a: UNEXPETED INCONSISTENCY:  RUN fsck Manually
Automatic file system check failed .. help!
Enter full path name of shell or return for /bin/sh

As you can see unlike the past I've not been given the username and
password.

Any help will be appreciated.

MotorMan

Good luck,

Dang Huynh

Quote:> The computer that I was running my FreeBSD went belly up so I took its IDE
> harddisk(the only disk) and put it in a differnt computer.

> Now when I start this computer, I get a prompt:

> mountroot>

> I typed ufs:/dev/ad0s1a

> and then I get a bunch of error messages as follow:

> Warning:  / was not properly dismounted
> swapon:  /dev/ad4s1b: Device not configured
> ...
> Can't opeen /dev/ad4s1a: Device not configured
> /dev/ad4s1a: Can't check file system
> /dev/ad4s1a: UNEXPETED INCONSISTENCY:  RUN fsck Manually
> Automatic file system check failed .. help!
> Enter full path name of shell or return for /bin/sh

> As you can see unlike the past I've not been given the username and
> password.

> Any help will be appreciated.

> MotorMan

I'm no expert, but it would seem that your old computer thought your hard
drive was the fifth drive. Your file /etc/fstab is referring to all of
these as this disk (ad4).

(all actual experts feel free to correct all mistakes in the following)

I think the proper route is to hit enter at the prompt for the shell and
mount the / directory manually using:

mount -rw /dev/ad0s1a /

Try ls to see if you see the directory. Once you have / mounted, you will
need to edit the fstab file. The editor you will have to use is probably
vi.

If you know how to edit with vi, change each instance of 4 to 0 and then
type mount -a and see if you can see your file system.

If you don't know how to edit with vi, reply to the NG and you may get some
pointers.

Hope that is of some assistance

JE

If you have a bootable live filesystem cd, I suggest you boot the cd,
    mount the disk's various file systems, and look about. If you've
    other space somewhere (another hard drive, for example) back up
    any essential data from the old drive, before trying to fix it.

Possibly there is nothing wrong with the fs itself, and possibly when
    your old machine went belly up it crashed with some pending soft
    updates. You should fsck each file system before trying to fix the
    references to /dev/ad4s1b and such, just in case.

Back to the device naming inconsistency. Everything on your drive that
    uses device names will be using the old names, and need to be
    changed. I think this is only a few things:

    (a) /etc/fstab

        Read 'man fstab' before starting.

        Probably you can fix /etc/fstab in a text editor, by changing
        every occurance of 'ad4' to 'ad0'. You should see something
        like this:

        # Device                Mountpoint      FStype  Options         Dump    Pass#
        /dev/ad4s1b             none            swap    sw              0       0
        /dev/ad4s1a             /               ufs     rw              1       1
        /dev/ad4s1g             /home           ufs     rw              2       2
        /dev/ad4s1d             /tmp            ufs     rw              2       2
        /dev/ad4s1e             /usr            ufs     rw              2       2
        /dev/acd0               /cdrom          cd9660  ro,noauto       0       0

        and you want it to end up something like this:

        # Device                Mountpoint      FStype  Options         Dump    Pass#
        /dev/ad0s1b             none            swap    sw              0       0
        /dev/ad0s1a             /               ufs     rw              1       1
        /dev/ad0s1g             /home           ufs     rw              2       2
        /dev/ad0s1d             /tmp            ufs     rw              2       2
        /dev/ad0s1e             /usr            ufs     rw              2       2
        /dev/acd0               /cdrom          cd9660  ro,noauto       0       0

    (b) Others? I think you can specify the root fs in boot.config or
        loader.conf, but I don't have such lines in mine.

Quote:> ...
> Can't opeen /dev/ad4s1a: Device not configured
> /dev/ad4s1a: Can't check file system
> /dev/ad4s1a: UNEXPETED INCONSISTENCY:  RUN fsck Manually
> Automatic file system check failed .. help!
> Enter full path name of shell or return for /bin/sh

> As you can see unlike the past I've not been given the username and
> password.

no, but you probably got a shell prompt after pressing enter. However
    if you have a live filesystem fixit cd you should probably just
    reboot and use the cd for fixing.

I have some 1RU servers that I upgarded to Promise 133 controllers.
There is ONE HD in them.  It is identfied at ad4 with
boot on ad4s1a.

The first two on board IDE controllers get the first four numbers.

I suspect he may have had an add-in controller on the machine from
which he remove the drive.

Bill

--