[Dejwy_k]

Helped making RAID from Panther (10.3) boot CD/DVD and erasing (= formating) created RAID in Tiger.
Tiger RAID hell !!

David

[Dejwy_k]

1/ I tryed create RAID from Tiger boot CD/DVD – without succes.
2/ I tryed create RAID from Panther boot CD/DVD – no problem – RAID was created
But after rebooting into Tiger – RAID say 1.2TB (this is o.k.) – but seems as read-only I cannot write anything on them.

Comand line command – convertRAID (Convert a RAID 1.x (pre-Tiger) to a RAID 2.x (Tiger)) not work:

diskutil convertRAID /Volumes/videoraid2
Starting to convert RAID. Resizing RAID disk to make room for RAID footer.
RAID parent rawSize = 1317571133440 bytes
Usable space for new RAID = 1317571059712 bytes
changing filesystem size on disk ‘disk5’…
Attempting to change filesystem size from 1317571133440 to 1317571059712 bytes
Filesystem grow failed, 1
Disk Management could not shrink the filesystem to fit the new RAID headers
Error converting RAID Invalid request (-9998)

—

/dev/disk3
#: type name size identifier
0: Apple_partition_scheme *613.5 GB disk3
1: Apple_partition_map 30.0 KB disk3s1
2: Apple_Driver_OpenFirmware 512.0 KB disk3s2
3: Apple_Boot_RAID 613.5 GB disk3s3
/dev/disk4
#: type name size identifier
0: Apple_partition_scheme *613.5 GB disk4
1: Apple_partition_map 30.0 KB disk4s1
2: Apple_Driver_OpenFirmware 512.0 KB disk4s2
3: Apple_Boot_RAID 613.5 GB disk4s3
/dev/disk5
#: type name size identifier
0: videoraid2 *1.2 TB disk5

[Dejwy_k]

Yes – disks are the same as worked in Panther.
This is Medea Videoraid FCR2X Fibre Channel. It consist from the same 2 parts (as have Apple XRaid).

Erasing both discs not helped. Erasing end succesfully, but RAID cannot been created

Creating RAID directly from 2 unpartitioned discs come with this message (in console – because Disk Utility stop responding without message):
——————–

Creating RAID
Filesystem: Mac OS Extended
RAID type: Striped RAID Set
RAID set name:

[Dejwy_k]

You are right, backuping is right way,
But make backwards incompatible OS without warning users is not good way.

Uunaccesible drive/raid after upgrade – it is good, because I can connect discs to 10.3.x system and use data.
But destroing data on discs – it is the worse case.

If software RAID version was changed – system must warn users, and dont change anything on discs to prevent data and not destoy data and destroy RAID.

Unaccesible data can be accessed in 10.3.x, but 10.4 dont make data inaccesible, but 10.4 destoy RAID and data cannot be accessed anymore from any (old or new) system..