error: unable to read superblock

The log disk format failed. The super block and directories may not have been created (depends on how far along the format was), so they could not be read. Sounds like you have a bad drive in the pack.

Thank for the response... finaly: Could not mount log filesystem, system may not work properly. Formating logdisk ... mount_all:96 Format logdisk error 2012-03-19 21:10:14 >>> set level raid50 EXT3-fs (sda1): error: unable to read superblock EXT4-fs (sda1): unable to read superblock EXT2-fs (sda1): error: unable to read superblock >> The log disk is not mounted. >> Booting in Maintenance mode. FortiAnalyzer-2000A login: admin Password: *********** Welcome! EXT3-fs (sda1): error: unable to read superblock EXT4-fs (sda1): unable to read superblock EXT2-fs (sda1): error: unable to read superblock (MAINT) (READ-ONLY) FortiAnalyz~$ EXT3-fs (sda1): error: unable to read superblock EXT4-fs (sda1): unable to read superblock EXT2-fs (sda1): error: unable to read superblock (MAINT) (READ-ONLY) FortiAnalyz~$ EXT3-fs (sda1): error: unable to read superblock EXT4-fs (sda1): unable to read superblock EXT2-fs (sda1): error: unable to read superblock (MAINT) (READ-ONLY) FortiAnalyz~$ A commande in CLI to change RAID? Before RAID50, in RAID10 no problem for me. Thanks.

(MAINT) (READ-ONLY) FortiAnalyz~$ diagnose raid info Free Disk Space: 0.01GB Total Disk Space: 0.06GB RAID information: RAID level: RAID50 RAID state: Inoperable RAID controller: 9550SXU-8LP Number of disks: 6 Array capacity: 1862.61GB Disk State Size disk01 NotPresent 0.00GB disk02 NotPresent 0.00GB disk03 NotPresent 0.00GB disk04 OK 465.76GB disk05 OK 465.76GB disk06 OK 465.76GB Controller configuration: Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-50 INOPERABLE - - 256K 1862.61 OFF OFF Port Status Unit Size Blocks Serial --------------------------------------------------------------- p0 NOT-PRESENT - - - - p1 NOT-PRESENT - - - - p2 NOT-PRESENT - - - - p3 OK u0 465.76 GB 976773168 9QM7QA2K p4 OK u0 465.76 GB 976773168 9QM8L6K4 p5 OK u0 465.76 GB 976773168 5QM0PNCQ p6 NOT-PRESENT - - - - p7 NOT-PRESENT - - - - Disk layout: Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) ------------------------------------------------------------------------ u0 RAID-50 INOPERABLE - - - - 1862.61 u0-0 RAID-5 INOPERABLE - - - 256K - u0-0-0 DISK DEGRADED - - - - 465.651 u0-0-1 DISK DEGRADED - - - - 465.651 u0-0-2 DISK DEGRADED - - - - 465.651 u0-1 RAID-5 INIT-PAUSED 0% - - 256K - u0-1-0 DISK OK - - p3 - 465.651 u0-1-1 DISK OK - - p4 - 465.651 u0-1-2 DISK OK - - p5 - 465.651 u0/v0 Volume - - - - - 1862.61 Firmware version: FE9X 3.08.00.004 (MAINT) (READ-ONLY) FortiAnalyz~$ (MAINT) (READ-ONLY) FortiAnalyz~$ conf system raid (raid)$ get level : RAID50 Free space: 0.01GB Total space: 0.06GB (raid)$ set level raid0 RAID0 raid5 RAID5 (raid)$ set level raid5 (raid)$ end Rebuilding the RAID array will erase the hard disks. You will lose all log and report data. Device disk quotas may be reduced if the new array is smaller. Do you want to continue? (y/n)y File system not found on /dev/sda1, will use ext3 format. (MAINT) (READ-ONLY) FortiAnalyz~$ The system is going down NOW !! Pausing log daemons... Failed to unmount the storage directory /Storage Failed to unmount the log disk /drive0 Stopping RAID ... done Please stand by while rebooting the system. FLG-2K (10:51-09.22.2006) Ver:04000001 Serial number:FLG-2K3F07000045 RAM activation CPU(00:00000f4a bfebfbff): Do MP initialization CPU(01:00000f4a bfebfbff): Do MP initialization Total RAM: 2048MB Enabling cache...Done. Scanning PCI bus...Done. Allocating PCI resources...Done. Enabling PCI resources...Done. Zeroing IRQ settings...Done. Verifying PIRQ tables...Done. Boot up, boot device capacity: 122MB. Press any key to display configuration menu... ...... Reading boot image 2243476 bytes. Initializing FortiAnalyzer... Creating RAID5 RAID array ... done Creating partition on /dev/sda ... done Formatting log disk (ext3) ...

I lost 3 drive: u0 RAID-50 INOPERABLE - - - - 1862.61 u0-0 RAID-5 INOPERABLE - - - 256K - u0-0-0 DISK DEGRADED - - - - 465.651 u0-0-1 DISK DEGRADED - - - - 465.651 u0-0-2 DISK DEGRADED - - - - 465.651 u0-1 RAID-5 INIT-PAUSED 0% - - 256K - u0-1-0 DISK OK - - p3 - 465.651 u0-1-1 DISK OK - - p4 - 465.651 u0-1-2 DISK OK - - p5 - 465.651 u0/v0 Volume - - - - - 1862.61 Then, i would like to use 3 DISK OK with RAID5... But after reboot... I lost RAID Controler : FLG-2K (10:51-09.22.2006) Ver:04000001 Serial number:FLG-2K3F************* RAM activation CPU(00:00000f4a bfebfbff): Do MP initialization CPU(01:00000f4a bfebfbff): Do MP initialization Total RAM: 2048MB Enabling cache...Done. Scanning PCI bus... Block to step " Scanning PCI bus..." Incompatibility or bug with Faz2000A + v4.3.1 + RAID50 / RAID5 + ext4 ? That is the question...