Problem with writing an UFS2 to iStore Storage System / can't find block in cyl 0 / bad magic number

[Erik Scholtz, ArgonSoft GmbH]

Miroslav,

thanks for your reply. No - I haven't tried this yet and so did this a 
minute ago, but got stucked on the second command:

**********************************************************************************
|# gpart create -s GPT da0
|# fdisk /dev/da0
|******* Working on device /dev/da0 ******* 
 
      |acpi0_check: ram0 attached
|parameters extracted from in-core disklabel are: 
 
                                |acpi0_check: npx0 attached55 
sectors/track=63 (16065 blks/cyl)
|                      acpi0_check: acpi0 attached
|Figures below won't work with BIOS for partitions not in cyl 1
|parameters to be used for BIOS calculations are:
|cylinders=1305 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 238 (0xee),(EFI GPT)
|    start 1, size 20971519 (10239 Meg), flag 0
|	beg: cyl 1023/ head 255/ sector 63;
|	end: cyl 1023/ head 255/ sector 63
|The data for partition 2 is:
|<UNUSED>
|The data for partition 3 is:
|<UNUSED>
|The data for partition 4 is:
|<UNUSED>
|
|# gpart add -b 1 -s 20971519 -t freebsd-ufs -l MyLabel da0
|gpart: start '1': Invalid argument
|
|# gpart add -b 34 -s 20971519 -t freebsd-ufs -l MyLabel da0
|gpart: size '20971519': Invalid argument
|
|# gpart add -b 34 -s 20971485 -t freebsd-ufs -l MyLabel da0
|gpart: size '20971485': Invalid argument
**********************************************************************************

Since gpart set the begin (start) on 1 and not on 34, I changed the -b 
option too. After failing this, I set the begin to 34 as in your 
example, which did not work either. Then I reduced the size (since when 
the start is later, it reduces the size too), which also did not work.

Any further ideas?
Greetings,
Erik

---
My blog: http://blog.elitecoderz.net



Miroslav Lachman wrote:
> Erik Scholtz, ArgonSoft GmbH wrote:
>> Hi,
>>
>> I'm working on the problem I'm describing below since 12/2008. In Dec.
>> 2008 I was trying to connect an iStor iSCSI-Storage-System to my FreeBSD
>> (tested with all releases 6.4, 7.1, 7.2 and 8.0), which did not work.
>>
>> After having many tests and working together with Danny from the iSCSI
>> Development Team, I'm now pretty sure the problem is in the UFS-tools
>> and neither in the SCSI nor in the iSCSI-driver.
>>
>> I come to this conclusion, since I was able to get a filesystem working,
>> after extending my Kernel with ext-3 and using ext-3 as filesystem - so
>> SCSI and iSCSI seem to work properly.
> 
> Did you tried partitioning with gpart and then UFS2 + SoftUpdates on 
> /dev/da0p1?
> I am using it with 7.2-STABLE from January and iscsi_initiator 2.2.4 on 
> Dell MD3000i (2.7TB partition)
> 
> gpart create -s GPT da0
> gpart add -b 34 -s 205520830 -t freebsd-ufs -l MyLabel da0
> newfs -U /dev/da0p1
> 
> Just substitute 205520830 with size of your storage.
> 
> Miroslav Lachman