Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
946 Views

SS4000-E Shares Not Ready

have already Googled for 2 days now and haven't find a solution for this.

I have a NAS INTEL SS4000-E, with 3 Disks RAID 5 the poblem is... I lost access to my RAID 5 array... after 2 rebuilds (successful ones) I cant mount the array... One disk stopped working in one day, made the rebuild, ok, in the day after a second disk stopped, new rebuild, to a new disk... now i cant access my shared folders... I have tried to update the firm ware to the last version, from 9 to 10 after the rebuild because the web page was acting strange, not showing logos and images... now this is what I have....

Code:# fdisk -l   Disk /dev/sda: 16 heads, 63 sectors, 1938021 cylinders Units = cylinders of 1008 * 512 bytes    Device Boot Start End Blocks Id System /dev/sda1 1 522 263087+ 83 Linux /dev/sda2 523 783 131544 82 Linux swap /dev/sda3 784 1938022 976367952+ 89 Unknown   Disk /dev/sdb: 16 heads, 63 sectors, 969021 cylinders Units = cylinders of 1008 * 512 bytes    Device Boot Start End Blocks Id System /dev/sdb1 1 522 263087+ 83 Linux /dev/sdb2 523 783 131544 82 Linux swap /dev/sdb3 784 969022 487991952+ 89 Unknown   Disk /dev/sdc: 16 heads, 63 sectors, 969021 cylinders Units = cylinders of 1008 * 512 bytes    Device Boot Start End Blocks Id System /dev/sdc1 1 522 263087+ 83 Linux /dev/sdc2 523 783 131544 82 Linux swap /dev/sdc3 784 969022 487991952+ 89 Unknown   Disk /dev/sdd: 255 heads, 63 sectors, 121504 cylinders Units = cylinders of 16065 * 512 bytes   Disk /dev/sdd doesn't contain a valid partition table 

Code:# mdadm --examine /dev/md1 mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got 00000000) # mdadm --examine /dev/md0 mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got e5933000) 

I'm really lost here... My data is supposed to be in sda3, sdb3, sdc3, but it it showing has unknown... Can anyone help me please?; ra

Tags (2)
0 Kudos
1 Reply
Highlighted
Community Manager
29 Views

Nuno,

In a four drive configurations the disks are designated as /dev/sda3, /dev/sdb3, /dev/sdc3 and /dev/sdd3. To see the status of a disk, run the following command:

mdadm –examine /dev/sdX3 (note two dashes before examine) (where X is the specific disk you want to see: a, b, c or d).

A typical response from a rebuilding system is:

/dev/sda1:

Magic : a92b4efc

Version : 00.90.00

UUID : deb59104:76824796:23cdfde1:5cc09783 <- UUID significance explained below

Creation Time : Wed Feb 10 15:04:08 2010

Raid Level : raid5

Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)

Array Size : 2930279808 (2794.53 GiB 3000.61 GB)

Raid Devices : 4

Total Devices : 4

Preferred Minor : 1

Note: Check if all working disks have identical UUID after issuing this command on all disks.

I believe that your disks will not have identical UUIDs indicating a failed array.

The operating system partition is md0. Data is on md1. See the Intel® Entry Storage System SS4000-E — http://www.intel.com/support/motherboards/server/ss4000-e/sb/CS-029880.htm System partition, volume and file system information.

0 Kudos