Search results

Solved. After a week of effort, we did it. The critical point was clearing the metadata from ada0. Thanks.

Thanks for your help and advice. Here is the output from the clearing of the metadata: # gpart destroy -F ada1 ada1 destroyed # gpart destroy -F ada0 gpart: Device busy # gmirror clear ada0 Can't clear metadata on ada0: Operation not permitted. gmirror: Not fully done. And after creating a...

I installed the OS anew, disabled soft updates journaling and again repeated the whole procedure word by word from the manual. And again I received # gmirror status Name Status Components mirror/gm0 DEGRADED ada0 (ACTIVE) ada1 is not existing. In few words - I am totally lost.

I succeeded in destroying the metadata only on ada1. I repeated the whole procedure from a scratch, leaving even more space at the end of the disk. And again I had the same error. This time I recorded the status before issuing the directive. Here are the outputs: # gmirror status Name Status...

I haven't swapped the disks. Any suggestions how to troubleshoot it? The only thing which comes to my mind is to starts again from a scratch.

Now I got over the creating of the array and even succeeded to boot from the second drive. I have one more (final) hurdle to overcome. When I tried to synchronize both disks and I got the following error: # df -h Filesystem Size Used Avail Capacity Mounted on...

Thanks! The mirror disk has some partitions from the previous attempts when skipping the error message. Tomorrow I will go on with your suggestion.

I did exactly as it is advised there, but of no avail. Here is the output of gpart: # gpart show ada0 => 63 1953525105 ada0 MBR (932G) 63 1953525042 1 freebsd [active] (932G) 1953525105 63 - free - (32K) # cat table.ada0s1 BSD 8 1 freebsd-ufs 0 8388608 2...

I installed a clean new system with MBR and BSD slice. The same problem persists. Moreover, there is no gm0s1 file in the /dev/mirror/ directory. The content of this directory is: crw-r----- 1 root operator 0xa5 Nov 18 15:54 gm0 crw-r----- 1 root operator 0xa6 Nov 18 15:54 gm0a crw-r-----...

Thanks, I"ll try it tonight.

The partitioning is BSD.

I am trying to create a RAID1 with two new disks on IBM x3250 M5 (10.0-RELEASE does not have a driver for the existing RAID controller) with no success. There are errors which I don't know how to deal with. And this is critical. So please help. The steps I have done so far as described in the...

Such problem exists only in 9.0 release version. Any other version from 5 through 8.2 does not exhibit such behavior. I can state for sure the problem lays in the internals of 9.0 release.

In my firewall the directive is: ipfw add allow udp from any to any 123 via any and it works perfectly. Try it. Also, if you have ntpd running, kill it for testing purposes and issue at the command prompt: ntpdate pool.ntp.org to check the result.

I don't understand your question. Please be more specific. All the values you see through "sysctl -a" are hardcoded in the kernel. I experimented with nearly every possible and even impossible combination for the last week without avail. The only thing which jumped against my eyes was that 9.0...

It was the same also with the generic kernel. I have to use 32bit version for various reasons (shared memory in 64bit version and linux 32bit apps is catastrophe) and I don't intend to use more than 4GB.

I have configured on FreeBSD (release 9.0 32bit with 4GB) shared memory as follows: kern.ipc.shm_allow_removed: 0 kern.ipc.shm_use_phys: 0 kern.ipc.shmall: 1048576 kern.ipc.shmseg: 256 kern.ipc.shmmni: 1024 kern.ipc.shmmin: 2 kern.ipc.shmmax: 2147479553 kern.features.sysv_shm: 1...

The BIOS does detect 4GB. It is seen in dmesg, but only 2 of them are available. I'll check the BIOS for other settings. The VGA card has no more than 32MB.

I bought for a customer an IBM server model x3200 M3 with 4GB memory. I installed FreeBSD 9.0 release 32bit (this release is the only one that can detect the disks). For my great surprise and disappointment the system see available only 2GB. Here is the quote from dmesg.today: FreeBSD...

If I understand you correctly, the internal IP of the router is 169.254.0.101, right? So, your defaultrouter should be 169.254.0.101 (private network) and not the public IP assigned to you by your ISP. Your bge0 adapter connected to the router should be in that range, for example 169.254.0.102...