Nanograv notes -- 2014-07-16 Nanograv Purchase Date: 2009-10-26 vendor : Varsity Desc : Intel storage server motherBd : Intel SSE212MC2RBRNA storage : 12 1 TB disks confugured as RAIF 5 MemTotal: 16326084 kB CPU info: Intel(R) Xeon(R) CPU E5405 @ 2.00GHz (4 cores) eth0 Link encap:Ethernet HWaddr 00:15:17:9A:FA:EC ==> nanograv eth1 Link encap:Ethernet HWaddr 00:15:17:9A:FA:ED ==> unused 2014-07-15:17 -- Installed two new 300 Gb disks inside the case -- install Sl6.5 fdisk /dev/sdb sdc is identical Device Boot Start End Blocks Id System /dev/sdb1 * 1 64 512000 fd Linux raid autodetect Partition 1 does not end on cylinder boundary. /dev/sdb2 64 8223 65536000 fd Linux raid autodetect /dev/sdb3 8223 10263 16384000 82 Linux swap / Solaris /dev/sdb4 10263 38914 230138200 5 Extended /dev/sdb5 10263 38914 230136832 83 Linux configued with md0 --- 500 MB /boot md1 --- 64 Gb / /dev/sdb5 205GB /data0 /dev/sdc5 205SB /data1 [root@nanograv etc]# swapon -s Filename Type Size Used Priority /dev/sdb3 partition 16383992 0 -1 /dev/sdc3 partition 16383992 0 -2 Raid Issue ________________________________ system was flashing front panel amber LED & beeping. This apparently was occurring for months. The hardware trouble-shooting guide from the MB manual did not identify the issue. There were no fault lites on any fans, PSU nor front bay drives. Removed the LSI Raid interface -- fault notications stopped -- implied a problem with the RAID Array. Ctrl-G early in boot sequence gets one into the RAID configuration GUI. This indicated Slot 11 have no Physical Drive ( there was a drive in the slot) The drive was marked off-line & removed logically. Physically removed & replaced the drive & the raid look ok. The system did not see a file system on the raid ( /dev/sda) "parted" the drive 00 created partition 1 as all available space. mkfs -f /dev/sda1 mount /dev/sda1 /dstore restore data from nanograv2 backup