Falcon

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by Falcon

  1. I have replaced my parity disk from 2TB to 3TB and I have used the Preclear_disk script version 1.12beta to clear the disk with -A as 64k alignment. When I am replacing the disk and start rebuilding i see these messages: root@Fileserver:~# fdisk -lu /dev/sdk WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdk: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdk1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. and from the mymain meny i see this line: What should I do, is this normal ? or should I stop rebuilding the parity disk and do something with it ?
  2. Now I have done some testing and I have also updated to Version 5.Beta 9. and have still total freeze on the system, but I think I have found the reason: I have a motherboard from ASUS P7P55D-E http://www.asus.com/Motherboards/Intel_Socket_1156/P7P55DE/ on this board it is 9 SATA ports and 2 ATA ports. it is separated like this: Intel® P55 Express Chipset built-in 6 xSATA 3.0 Gb/s ports Intel Matrix Storage Technology Support RAID 0,1,5,10 JMicron® JMB363 PATA and SATA controller 1 xUltraDMA 133/100/66 for up to 2 PATA devices 1 xExternal SATA 3Gb/s port 1 xSATA 3Gb/s port (black) and Marvell® SATA 6Gb/s controller: - 2 x SATA 6.0 Gb/s ports (gray) Normaly I have connected the Cache drive to port 6 on the Intel® P55 Express Chipset built-in ports on the motherboard. I have just got an new 3TB WD drive and disconnected the cache drive so I can connect the new drive on that port and run the preclear script on the disk before i put it into the raid. Thats means that the preclear script is running and reading data from the disk on port 6 when I tested this the first time. If I try to write any of the other drives which is connected to the SAME controller but another port 1-5 on (Intel® P55 Express Chipset built-in ports on the motherboard) \\10.10.10.10\disk1 or \disk2 ..... the write is freezing and the write operation is not working. If I try to read from the drives it works as it should. If I try to write to any other drives I have on the other interfaces the write is working as it should. After the preclear was finished, I tried to read a file with 4.5 GB size from one drive on port on the controller and write to another disk on another port on the same controller and the same freeze problem was reproduced. My hardware is: I have a motherboard from ASUS P7P55D-E http://www.asus.com/Motherboards/Intel_Socket_1156/P7P55DE/ All drive active 10 GB Memory Dual Core 2.8 Ghz Drives: SATA 2T WDC_WD20EARS-00MVWB0 Paritet 500G 6G ST3500630AS Disk1 1T 15G WDC_WD10EACS-00C7B0 Disk2 1T 26G WDC_WD10EACS-00C7B0 Disk3 1T 32G WDC_WD10EACS-00ZJB0 Disk4 500G 3G SAMSUNG_HD501LJ Disk5 1T 51G WDC_WD10EACS-00C7B0 Disk6 200G 7G ST3200822AS Disk7 320G 18G ST9320423AS Disk14 ATA 300G 8G Maxtor_6B300R0 Disk8 300G 17G Maxtor_6B300R0 Disk9 320G 34G ST3320620A Disk10 320G 16G ST3320620A Disk11 It is very easy to find when you disconnect the cache drive, if any other with the same controller want to test and see if they have the same freeze. syslog.txt
  3. I will try to reproduce and publish the logs.
  4. Yes I am also after the same answer and don't see this as a problem. I think the reason for the freeze is an combination of sleeping drives and the design with one fixed parity disk.
  5. I have the same problem with freezing if I have several file jobs at the system. I thought the unraid filesystem is like this. I have not checked if this is only on write operations. It is not always freezing but sometimes.
  6. I have also problems with memory after I have installed Crashplan. It become worse after a selected a lot of new files. I have 2 GB Memory and found this in my syslog As you can see it kills tasks to free memory, but it kills itself too...
  7. I got the same problem with this motherboard, but with another cheap ATA interface card to use my old 300 GB ATA disks. The problem with this motherboard is that you can not have more than 12 devices in the harddisk boot list, if you have 12 devices harddisk devices the USB device will be pushed out of the list. So it is very important to buy additional Sata card that have the possibilty to disable boot. !! The reason is: The board have 9 SATA Controlleres and 2 ATA controllers and 2 of 6 GB SATA controlleres can be disabled from boot. You then have 7 Sata disk in the device list, if you buy a card without the possibility to disable boot, then you can only use 4 more devices before the usb device is of the boot list. !! So my next step is to buy the Supermicro AOC-SASLP-MV8 and disable the boot, and add additional disks