Problem with Adaptec AIC7902 SCSI
-
Worst case scneario, break the raid 1 in hardware and use our new raid 1 support that is included in the installer.
-
Worst case scneario, break the raid 1 in hardware and use our new raid 1 support that is included in the installer.
Looks like FreeBSD don`t support the Adaptec AIC7902 as a raid, just as Scsi device >:(
The solution is then to by the ServeRaid extension to my server :-\Where to find some info about the raid 1 support as SW?
Thanx for helping!
-
When the installer detects more than 1 drive it installs a menu item in the installer menu called Create GEOM mirror. Follow those prompts then the new mirror will show up as a install target during installation.
-
When the installer detects more than 1 drive it installs a menu item in the installer menu called Create GEOM mirror. Follow those prompts then the new mirror will show up as a install target during installation.
One more question here :)
I got problems when trying to use this GEON mirror
Cancelled
Execution of the command
/sbin/bsdlabel -B -r -w mirror/pfSenseMirrors1 auto
FAILED with a return code of 136
???
What is this??
-
Not sure, I would need to see the contents of /tmp/installer.log after the failure.
-
Not sure, I would need to see the contents of /tmp/installer.log after the failure.
This is the end of the log file:
,-<<< Executing
/sbin/fdisk -v -f /tmp/new.fdisk mirror/pfSenseMirror' | ******* Working on device /dev/mirror/pfSenseMirror ******* | fdisk: WARNING line 1: number of cylinders (8924) may be out-of-range | (must be within 1-1024 for normal BIOS operation, unless the entire disk | is dedicated to FreeBSD) | parameters extracted from in-core disklabel are: | cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) | | Figures below won't work with BIOS for partitions not in cyl 1 | parameters to be used for BIOS calculations are: | cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) | | Information from DOS bootblock is: | 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) | start 63, size 143363997 (70001 Meg), flag 80 (active) | beg: cyl 0/ head 1/ sector 1; | end: cyl 731/ head 254/ sector 63 | 2: <unused>| 3: <unused>| 4: <unused>| fdisk: Geom not found: "pfSenseMirror"->>> Exit status: 0
,-<<< Executing/sbin/fdisk mirror/pfSenseMirror' | ******* Working on device /dev/mirror/pfSenseMirror ******* | parameters extracted from in-core disklabel are: | cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) | | Figures below won't work with BIOS for partitions not in cyl 1 | parameters to be used for BIOS calculations are: | cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) | | Media sector size is 512 | Warning: BIOS sector numbering starts with sector 1 | Information from DOS bootblock is: | The data for partition 1 is: | sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) | start 63, size 143363997 (70001 Meg), flag 80 (active) | beg: cyl 0/ head 1/ sector 1; | end: cyl 731/ head 254/ sector 63 | The data for partition 2 is: | <unused>| The data for partition 3 is: | <unused>| The data for partition 4 is: | <unused>->>> Exit status: 0
,-<<< Executing/sbin/bsdlabel -B -r -w mirror/pfSenseMirrors1 auto' | Floating point exception (core dumped)->>> Exit status: 136</unused></unused></unused></unused></unused></unused> -
Really need to see the entire file.
-
Really need to see the entire file.
ok
u can find the file here: http://www.advanticom.no/logfile.txt
-
Are you sure you picked the mirror drive during installation? Its using the primary drive instead of the mirror AFTER its been allocated to GEOM. It then complains about this.
-
Are you sure you picked the mirror drive during installation? Its using the primary drive instead of the mirror AFTER its been allocated to GEOM. It then complains about this.
yeah.. I picked the right mirror…... Just testet one more time.. And then change main disk and sec disk...
Same problem....
-
Then I am not too sure at the moment. I'll have to do a test install with Vmware shortly.
-
Then I am not too sure at the moment. I'll have to do a test install with Vmware shortly.
Just made the partition smaler.. then It works ???
Thanks for helping anyway :)