Well, the bad day has come... My primary server won't boot. I have
backups of databases and user directories, but I need to try to get
this server back up again.
During the boot sequence, it freezes at the statement:
Trying to mount root from ufs:/dev/mfid0s1a
I tried booting into single use
> Try downloading and booting the livefs environment (I think you need cd1
> and the livefs cd or just the DVD) and see if you can mount it from
> that, if not it could be a controller issue. If you can then its
> probably your OS/kernel but at least you now have access to your
> data/configs etc e
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ery experienced FreeBSD admin, close to lower Manhattan, please
contact me off list at identry(at)gmail.com.
Thanks: John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any m
> Identry wrote:
>>
>> During the boot sequence, it freezes at the statement:
>>
>> Trying to mount root from ufs:/dev/mfid0s1a
>>
> Try downloading and booting the livefs environment (I think you need cd1
> and the livefs cd or just the DVD) and see if
I've got a server in lower manhattan (at NYI.net datacenter) that
hangs when trying to mount the root partition. I'm working on it right
now, but have a feeling this may be beyond my limited admin skills,
and I really need this server back online ASAP.
Might be time to hire a professional.
Can an
> Try downloading and booting the livefs environment (I think you need cd1
> and the livefs cd or just the DVD) and see if you can mount it from
> that, if not it could be a controller issue. If you can then its
> probably your OS/kernel but at least you now have access to your
> data/configs etc e
is an 'upgrade' option on the install menu (I'm burning some 7.2
CDs right now to double check.)
Or would it be safer to try to bring up the machine on it's own with a
6.2 generic kernel, first?
-- John
--
<><><><><><><><>&l
>Are you using the GENERIC kernel
After more research, I think the answer to this is no. There is a
directory called /boot/kernel.old. From my reading, I believe this is
the original generic kernel?
> if not have you tried it?
Not yet. Section "24.2.3 Major and Minor Upgrades" of the Handbook
sa
> Try this:
>
> # strings /boot/kernel/kernel | grep ':/usr/obj/usr/src/sys/'
> # strings /boot/kernel.old/kernel | grep ':/usr/obj/usr/src/sys/'
$ strings kernel/kernel |grep ':/usr/obj/usr/src/sys'
r...@on.identry.com:/usr/obj/usr/src/sys/INET_ON
$ strings kernel.old/kernel |grep ':/usr
> If you did not touch the kernel, there is no need to boot GENERIC! Plus you
> have said that this box is running PF, which is not in the GENERIC kernel!
> Personally, I am interested in knowing why the system does not mount the
> root partition on its own when you can do it by hand and it does no
>> So I guess the question now is, if I can mount it manually, why
>> doesn't it mount during the boot process?
>>
> I'd give it an fsck or two (more than one has been needed once or
> twice)
So I've been thinking about how to run fsck...
At the moment, I have to boot from an install cd, go into
> Realize that if you upgrade to 7.x, you'll have to remove and reinstall
> all ports because the version number of shared system libraries will
> have changed.
Yes, I've decided this is way too complicated.
>> Or would it be safer to try to bring up the machine on it's own with a
>> 6.2 generic
> fsck is run when all file systems are unmounted!
>
> If you can, choose single use mode, press enter when it says something like
> "/bin/sh" (I don't remember the wordings) and then on the subsequent
> prompt,,
> # fsck -y [Press enter here]
>
> That is all you need. Once it completes, it will br
>> Should I use any flags? Should I mount the filesystems read write or read
>> only?
>
> You should never fsck a filesystem when its mounted!
Ah... glad I asked.
> I think you should start by reading the manual pages for fsck and
> fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'
>> > I think you should start by reading the manual pages for fsck and
>> > fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'.
Okay, back in the data center. I ran fsck_ffs -fp on my root file
system and it returned with no errors. It just printed some
information about number of fil
> Non-printable-character (NPC)
>
> NPCs may be a culprit for a file that used to work, now doesn't. Or a
> inode oddity.
>
> I've been following this thread but haven't chipped in because of
> timing (you driving to the datacenter).
>
> Here's what I'd consider:
> # mv /etc/fstab /etc/old-fstab
> Okay, back in the data center. I ran fsck_ffs -fp on my root file
> system and it returned with no errors. It just printed some
> information about number of files, used, free space, etc., ending with
> the interesting fact of .3% fragmentation.
>
> Then I reran it without the -fp and it printed
> Well, something got worse. After running fsck_ffs with no errors, I
> tried to boot the machine. It got to the point where it printed:
>
>
> Booting from BIOS Partition 0
> PS2 keyboard detected
> PS2 mouse detected
>
> and it just hangs at that point.
Worse and worse... The machine won't boot
>> Looks like your hardware is dying/dead.
>
> Sadly, I agree.
>
> Reset BIOS CMOS data (hardware jumper on motherboard)
> Enter RAID controller BIOS, (re)set your "boot drive"
>
> But it looks like a fundamental BIOS control issue is malfunctioning.
>
> Do you have a PCI Diagnostics card? One lik
> I'd get to the point of swapping hardware one at a time until it
> fixes, or until you exhaust your options. Have any kind of support
> contract with the OEM?
I do have a support contract and I'm going to dump this right in their
lap. Two machines we bought from them -- pretty expensive ones --
As part of my server recovery operation, I want to split off my mail
server onto it's own server. I've never built a mail server before, so
I'm debating how to go about it.
The old mail server was built with a toaster, and frankly, I knew how
to use it, but never understood how it worked. I'm in a
Frack... qmail is impossible. I've been hacking at this for 14 hours
and it's just not working. I must be stupid.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "
Where are user crontab files stored in the file system?
I used to create user crontab files and then load them with 'crontab
name-of-cronfile', but then I got clever and discovered 'crontab -e'.
The problem is, that doesn't give me the 'backup' of having a text
crontab file.
The system must store
> there is a great guide for installing qmail:
> http://www.lifewithqmail.org/
> Of course, it just explains the technical steps for installing qmail,
> not mailserver setups in general (nevertheless there are some links
> about relaying etc.)
That's one of the docs that I was working from
25 matches
Mail list logo
