June 10, 201115 yr I belieive the GPT partitions are only created for drives >2TiB. You can't control which drives are GPT and which are MBR. Well, after upgrading my Beta6a -> Beta7, this is what fdisk reports: root@The-Vault:~# fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Disk /dev/sdb: 2063 MB, 2063597568 bytes 255 heads, 63 sectors/track, 250 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x90909090 Device Boot Start End Blocks Id System /dev/sdb1 * 1 251 2013184 6 FAT16 Partition 1 has different physical/logical endings: phys=(249, 254, 63) logical=(250, 162, 40) WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sde: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Which confirms this: Ah, I thought that If gdisk finds a valid MBR or BSD disklabel but no GPT data, it will attempt to convert the MBR or disklabel into GPT form. from man gdisk, meant that any MBR drive could be converted to GPT. Cheers.
June 10, 201115 yr Were different Realtek LAN drivers added? To correct problems with certain Realtek models...?
June 10, 201115 yr Reverse the process you did to upgrade from 4.7 to 5.0b7. Hopefully you saved a backup of your flash drive with your 4.7 settings on it...
June 10, 201115 yr Author Were different Realtek LAN drivers added? To correct problems with certain Realtek models...? Whatever driver upgrades from linux kernel 2.6.36.2 -> 2.6.37.6 are of course included. That is the primary reason why the linux kernel is updated (in order to pick up driver updates).
June 10, 201115 yr Author I'm sure this was not the intention, Beta7 now spinup/spindown the drives in VMWare ESXi using mapped raw disks, but temperatures still a non go. The tests were done using either LSI Logic SAS controller (mptsas driver) and Paravirtual controller (pvscsi driver with recompiled kernel). If you, Tom, could fix this little temperature bug, we can dramatically improve the usability of unRAID, since the users could consolidate router / PVR / home automation / storage appliances into one physical machine. For one of your drives that don't report temps, note what it's linux device identifier is, e.g., "sdc", and type this command from a telnet session: smartctl -A /dev/sdc <-- replace 'sdc' with correct device identifer Then post the output here.
June 10, 201115 yr Author Tom, Nice to see GPT partitions are supported now. Did not see it mentioned in the release notes... (the release notes for the transition from 5.0-beta6a to 5.0-beta6b is missing ) Did you fix the bug where a cache drive with multiple partitions is considered "unknown" ?? (The bug caused unRAID to re-partition the cache drive to only have one partition, wiping out the other purposely created partitions) Interesting, that feature of recognizing Cache drive with "non-standard" unRaid partition worked by "accident" in previous releases. I'll restore this accidental feature in next beta. BTW where the code base is moving is to have parity generated over the entire physical address space of data disks, not just partition 1. This will let me be able to reconstruct an entire data disk contents, and thus let you plug in disks partitioned and formatted in "foreign" systems. For example, I want to be able to take a large GPT partitioned hard drive from a Windows 7 system with NTFS file system and incorporate into the array as-is. Then, on disk-by-disk basis user can specify which partition of each disk to "export", default being partition 1 (but often, esp. with GPT partitioned drives, partition 1 is not the main data storage partition). Then if that disk dies, unRaid can reproduce the entire disk, including partitions not being used.
June 10, 201115 yr I went ahead and upgraded yesterday to 5.0B7 from 5.0B6a. I ran parity twice. I saw no noticible bad things yet. I did however test the disk spindown issue i had in beta 6a. It looks to have been fixed. Setting my drives back to the master "Default" timeout works as it should now. PS. The 3TB support was a nice supprise and well timed. The egg has HITACHI Deskstar 0S03230 3TB for $119 this week. That's low enough to make me buy a few..
June 10, 201115 yr Hi! I'm sure this was not the intention, Beta7 now spinup/spindown the drives in VMWare ESXi using mapped raw disks, but temperatures still a non go. The tests were done using either LSI Logic SAS controller (mptsas driver) and Paravirtual controller (pvscsi driver with recompiled kernel). If you, Tom, could fix this little temperature bug, we can dramatically improve the usability of unRAID, since the users could consolidate router / PVR / home automation / storage appliances into one physical machine. For one of your drives that don't report temps, note what it's linux device identifier is, e.g., "sdc", and type this command from a telnet session: smartctl -A /dev/sdc <-- replace 'sdc' with correct device identifer Then post the output here. Here my screen dump of a WD20EARS showing no temps... Bye.
June 11, 201115 yr I'm sure this was not the intention, Beta7 now spinup/spindown the drives in VMWare ESXi using mapped raw disks, but temperatures still a non go. The tests were done using either LSI Logic SAS controller (mptsas driver) and Paravirtual controller (pvscsi driver with recompiled kernel). If you, Tom, could fix this little temperature bug, we can dramatically improve the usability of unRAID, since the users could consolidate router / PVR / home automation / storage appliances into one physical machine. For one of your drives that don't report temps, note what it's linux device identifier is, e.g., "sdc", and type this command from a telnet session: smartctl -A /dev/sdc <-- replace 'sdc' with correct device identifer Then post the output here. My dumps: root@Tower:~# smartctl -A /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 234016408 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2771 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 40744490 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6860 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 88 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032834 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 057 045 Old_age Always - 28 (Min/Max 27/29) 194 Temperature_Celsius 0x0022 028 043 000 Old_age Always - 28 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 046 040 000 Old_age Always - 234016408 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 230193067201874 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 290482469 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3868205915 root@Tower:~# smartctl -A /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 165814427 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 440 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3284118 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1627 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 35 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 063 045 Old_age Always - 28 (Min/Max 26/28) 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 050 045 000 Old_age Always - 165814427 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 144392505524929 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1838164866 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2032970711 Loaded modules: root@Tower:~# lsmod Module Size Used by md_mod 44397 0 xor 12961 1 md_mod ata_piix 17455 0 mptsas 29873 0 mptscsih 14072 1 mptsas mptbase 49478 2 mptsas,mptscsih scsi_transport_sas 16613 1 mptsas piix 3524 0 e1000 75710 0
June 11, 201115 yr Well.. i thought i was doing well. After a reboot a drive redballed on me. it is my only gen 1 ears in the array. the array did auto start with the redball. i can also see all the data of i go to \servername\disk5. all drives except disk5 and cache spin. Looks like a driver issue also Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Jun 10 20:02:15 Goliath kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1000000 thousands of lines of this. syslog-20110610-193632.zip
June 11, 201115 yr Upgraded to this one. No problems so far. Started parity check and noticed significant increase in the reported speed in the first few minutes - at least 15-20 MB/s better. Will see the end results tomorrow.
June 11, 201115 yr I belieive the GPT partitions are only created for drives >2TiB. You can't control which drives are GPT and which are MBR. Well, after upgrading my Beta6a -> Beta7, this is what fdisk reports: root@The-Vault:~# fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Disk /dev/sdb: 2063 MB, 2063597568 bytes 255 heads, 63 sectors/track, 250 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x90909090 Device Boot Start End Blocks Id System /dev/sdb1 * 1 251 2013184 6 FAT16 Partition 1 has different physical/logical endings: phys=(249, 254, 63) logical=(250, 162, 40) WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn 't support GPT. Use GNU Parted. Disk /dev/sde: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Which confirms this: Ah, I thought that If gdisk finds a valid MBR or BSD disklabel but no GPT data, it will attempt to convert the MBR or disklabel into GPT form. from man gdisk, meant that any MBR drive could be converted to GPT. Cheers. If this is correct can you go back to 4.7? since it did not use GDP? and is GDP conversion somthing that needs to be run or automatically happens? I want to update but still want to go back to 4.7 if problems arize.
June 11, 201115 yr A GPT partition will ONLY be used on disks > 2TB. Regardless if it is possible to use one on smaller disks, unRAID 5.0beta7 does not. You do not get to choose which type of partitioning. A drive > 2TB will not be recognized in earlier versions of unRAID as being valid. Smaller drives are all handled as they are in all prior versions of unRAID. As long as you do not have drives > 2TB, you can revert to 4.7. (by putting back your old config folder you saved and re-assigning the drives to their respective slots) Joe L.
June 11, 201115 yr I was still having spindown issues with some of my disks. I did some research and found in the disk.cfg file, some of my disks had thie spindown delay set to "" and some had it set to "-1". The ones with the "-1" worked and the ones with the "" didn't. Using the emhttp GUI, I selected each disk and hit the (upper) Apply button, and it has set the spindown delay to "-1" on all disks and all disks are now spinning down properly. (The GUI shows "default" whether the spindown is set to "" or "-1"). Since spindown totally didn't work for me with beta-6a, I expect this was the problem all along. Thought I would post in case someone else experienced something similar.
June 11, 201115 yr I was still having spindown issues with some of my disks. I did some research and found in the disk.cfg file, some of my disks had thie spindown delay set to "" and some had it set to "-1". The ones with the "-1" worked and the ones with the "" didn't. Using the emhttp GUI, I selected each disk and hit the (upper) Apply button, and it has set the spindown delay to "-1" on all disks and all disks are now spinning down properly. (The GUI shows "default" whether the spindown is set to "" or "-1"). Since spindown totally didn't work for me with beta-6a, I expect this was the problem all along. Thought I would post in case someone else experienced something similar. I reported having to manually spin down (possibly I'd also hit 'Apply' on the disk config), before my drives would spin down in beta6.
June 11, 201115 yr . remind you that the old disk NEVER got a red ball Do you still have the disk that did not have a "red" indicator, but was having read errors? Here is what I'm guessing you did. A) You loaded your old disk with data and THEN assigned a parity disk. The initial parity calc occurred after your disks had been loaded with data. (you did this to be faster) or B) did you assign parity and data, then load the data while automatically calculating parity? (loading data would have been slower with parity calcs occurring as the load occurred) Which one was it? "A", or "B" Joe was right on the spot as usual .... i had to run reiserfsck -- rebuild-tree to get the format back ... only lost a few files .... so somehow i corrupted my parity with the bad drive ..... guess i best run a parity check now .. before i replace a 750 gb with a rma'd 1 tb ?
June 11, 201115 yr Well.. i thought i was doing well. After a reboot a drive redballed on me. it is my only gen 1 ears in the array. the array did auto start with the redball. i can also see all the data of i go to \servername\disk5. all drives except disk5 and cache spin. I was not sure what to do, so downgraded back to 5.0 beta6a to see if was the driver. After the drive went back to a green ball and array auto started online as OK. I'm running a smartcheck on the drive now.
June 11, 201115 yr Continued...... Ok... It passed smart. The drive is not perfect, it has a few "issues". It has an excessive number of load counts and a "Multi_Zone_Error_Rate" of 1 It used to be in a WHSv1 server for a while. I'll assume that's what caused the high count rate. it was a known issue. it also has a decent amount of relocated sectors. those have not changed in a while as i recall... Jun 11 10:39:30 Goliath smartctl[30480]: === START OF INFORMATION SECTION === Jun 11 10:39:30 Goliath smartctl[30480]: Model Family: Western Digital Caviar Green (Adv. Format) family Jun 11 10:39:30 Goliath smartctl[30480]: Device Model: WDC WD20EARS-00S8B1 Jun 11 10:39:30 Goliath smartctl[30480]: Serial Number: WD-WCAVY2067763 Jun 11 10:39:30 Goliath smartctl[30480]: Firmware Version: 80.00A80 Jun 11 10:39:30 Goliath smartctl[30480]: User Capacity: 2,000,398,934,016 bytes Jun 11 10:39:30 Goliath smartctl[30480]: Device is: In smartctl database [for details use: -P show] Jun 11 10:39:30 Goliath smartctl[30480]: ATA Version is: 8 Jun 11 10:39:30 Goliath smartctl[30480]: ATA Standard is: Exact ATA specification draft version not indicated Jun 11 10:39:30 Goliath smartctl[30480]: Local Time is: Sat Jun 11 10:39:30 2011 CDT Jun 11 10:39:30 Goliath smartctl[30480]: SMART support is: Available - device has SMART capability. Jun 11 10:39:30 Goliath smartctl[30480]: SMART support is: Enabled Jun 11 10:39:30 Goliath smartctl[30480]: Power mode is: ACTIVE or IDLE Jun 11 10:39:30 Goliath smartctl[30480]: Jun 11 10:39:30 Goliath smartctl[30480]: === START OF READ SMART DATA SECTION === Jun 11 10:39:30 Goliath smartctl[30480]: SMART overall-health self-assessment test result: PASSED Jun 11 10:39:30 Goliath smartctl[30480]: Jun 11 10:39:30 Goliath smartctl[30480]: General SMART Values: Jun 11 10:39:30 Goliath smartctl[30480]: Offline data collection status: (0x85) Offline data collection activity Jun 11 10:39:30 Goliath smartctl[30480]: was aborted by an interrupting command from host. Jun 11 10:39:30 Goliath smartctl[30480]: Auto Offline Data Collection: Enabled. Jun 11 10:39:30 Goliath smartctl[30480]: Self-test execution status: ( 244) Self-test routine in progress... Jun 11 10:39:30 Goliath smartctl[30480]: 40% of test remaining. Jun 11 10:39:30 Goliath smartctl[30480]: Total time to complete Offline Jun 11 10:39:30 Goliath smartctl[30480]: data collection: (39180) seconds. Jun 11 10:39:30 Goliath smartctl[30480]: Offline data collection Jun 11 10:39:30 Goliath smartctl[30480]: capabilities: (0x7b) SMART execute Offline immediate. Jun 11 10:39:30 Goliath smartctl[30480]: Auto Offline data collection on/off support. Jun 11 10:39:30 Goliath smartctl[30480]: Suspend Offline collection upon new Jun 11 10:39:30 Goliath smartctl[30480]: command. Jun 11 10:39:30 Goliath smartctl[30480]: Offline surface scan supported. Jun 11 10:39:30 Goliath smartctl[30480]: Self-test supported. Jun 11 10:39:30 Goliath smartctl[30480]: Conveyance Self-test supported. Jun 11 10:39:30 Goliath smartctl[30480]: Selective Self-test supported. Jun 11 10:39:30 Goliath smartctl[30480]: SMART capabilities: (0x0003) Saves SMART data before entering Jun 11 10:39:30 Goliath smartctl[30480]: power-saving mode. Jun 11 10:39:30 Goliath smartctl[30480]: Supports SMART auto save timer. Jun 11 10:39:30 Goliath smartctl[30480]: Error logging capability: (0x01) Error logging supported. Jun 11 10:39:30 Goliath smartctl[30480]: General Purpose Logging supported. Jun 11 10:39:30 Goliath smartctl[30480]: Short self-test routine Jun 11 10:39:30 Goliath smartctl[30480]: recommended polling time: ( 2) minutes. Jun 11 10:39:30 Goliath smartctl[30480]: Extended self-test routine Jun 11 10:39:30 Goliath smartctl[30480]: recommended polling time: ( 255) minutes. Jun 11 10:39:30 Goliath smartctl[30480]: Conveyance self-test routine Jun 11 10:39:30 Goliath smartctl[30480]: recommended polling time: ( 5) minutes. Jun 11 10:39:30 Goliath smartctl[30480]: SCT capabilities: (0x3031) SCT Status supported. Jun 11 10:39:30 Goliath smartctl[30480]: SCT Feature Control supported. Jun 11 10:39:30 Goliath smartctl[30480]: SCT Data Table supported. Jun 11 10:39:30 Goliath smartctl[30480]: Jun 11 10:39:30 Goliath smartctl[30480]: SMART Attributes Data Structure revision number: 16 Jun 11 10:39:30 Goliath smartctl[30480]: Vendor Specific SMART Attributes with Thresholds: Jun 11 10:39:30 Goliath smartctl[30480]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jun 11 10:39:30 Goliath smartctl[30480]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 3 Spin_Up_Time 0x0027 152 143 021 Pre-fail Always - 9375 Jun 11 10:39:30 Goliath smartctl[30480]: 4 Start_Stop_Count 0x0032 093 093 000 Old_age Always - 7622 Jun 11 10:39:30 Goliath smartctl[30480]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5246 Jun 11 10:39:30 Goliath smartctl[30480]: 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 573 Jun 11 10:39:30 Goliath smartctl[30480]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 194 Jun 11 10:39:30 Goliath smartctl[30480]: 193 Load_Cycle_Count 0x0032 171 171 000 Old_age Always - 87319 Jun 11 10:39:30 Goliath smartctl[30480]: 194 Temperature_Celsius 0x0022 114 095 000 Old_age Always - 38 Jun 11 10:39:30 Goliath smartctl[30480]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jun 11 10:39:30 Goliath smartctl[30480]: 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 Jun 11 10:39:30 Goliath smartctl[30480]: Jun 11 10:39:30 Goliath smartctl[30480]: SMART Error Log Version: 1 Jun 11 10:39:30 Goliath smartctl[30480]: No Errors Logged Jun 11 10:39:30 Goliath smartctl[30480]: Jun 11 10:39:30 Goliath smartctl[30480]: SMART Self-test log structure revision number 1 Jun 11 10:39:30 Goliath smartctl[30480]: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error Jun 11 10:39:30 Goliath smartctl[30480]: # 1 Short offline Completed without error 00% 5246 - Jun 11 10:39:30 Goliath smartctl[30480]: # 2 Short offline Completed without error 00% 5245 - Jun 11 10:39:30 Goliath smartctl[30480]: # 3 Short offline Completed without error 00% 5245 - Jun 11 10:39:30 Goliath smartctl[30480]: # 4 Short offline Completed without error 00% 5245 - Jun 11 10:39:30 Goliath smartctl[30480]: Jun 11 10:39:30 Goliath smartctl[30480]: SMART Selective self-test log data structure revision number 1 Jun 11 10:39:30 Goliath smartctl[30480]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Jun 11 10:39:30 Goliath smartctl[30480]: 1 0 0 Not_testing Jun 11 10:39:30 Goliath smartctl[30480]: 2 0 0 Not_testing Jun 11 10:39:30 Goliath smartctl[30480]: 3 0 0 Not_testing Jun 11 10:39:30 Goliath smartctl[30480]: 4 0 0 Not_testing Jun 11 10:39:30 Goliath smartctl[30480]: 5 0 0 Not_testing Jun 11 10:39:30 Goliath smartctl[30480]: Selective self-test flags (0x0): Jun 11 10:39:30 Goliath smartctl[30480]: After scanning selected spans, do NOT read-scan remainder of disk. Jun 11 10:39:30 Goliath smartctl[30480]: If Selective self-test is pending on power-up, resume after 0 minute delay. Jun 11 10:39:30 Goliath smartctl[30480]: Since it was back to a greenball in Beta 6a, I upgraded to beta 7 again.. still green after 2 reboots. I'll run parity again then reboot and see what it does.
June 11, 201115 yr Author Hi! I'm sure this was not the intention, Beta7 now spinup/spindown the drives in VMWare ESXi using mapped raw disks, but temperatures still a non go. The tests were done using either LSI Logic SAS controller (mptsas driver) and Paravirtual controller (pvscsi driver with recompiled kernel). If you, Tom, could fix this little temperature bug, we can dramatically improve the usability of unRAID, since the users could consolidate router / PVR / home automation / storage appliances into one physical machine. For one of your drives that don't report temps, note what it's linux device identifier is, e.g., "sdc", and type this command from a telnet session: smartctl -A /dev/sdc <-- replace 'sdc' with correct device identifer Then post the output here. Here my screen dump of a WD20EARS showing no temps... Bye. I see the issue here, thanks!
June 11, 201115 yr Author I'm sure this was not the intention, Beta7 now spinup/spindown the drives in VMWare ESXi using mapped raw disks, but temperatures still a non go. The tests were done using either LSI Logic SAS controller (mptsas driver) and Paravirtual controller (pvscsi driver with recompiled kernel). If you, Tom, could fix this little temperature bug, we can dramatically improve the usability of unRAID, since the users could consolidate router / PVR / home automation / storage appliances into one physical machine. For one of your drives that don't report temps, note what it's linux device identifier is, e.g., "sdc", and type this command from a telnet session: smartctl -A /dev/sdc <-- replace 'sdc' with correct device identifer Then post the output here. My dumps: root@Tower:~# smartctl -A /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 234016408 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2771 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 40744490 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6860 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 88 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032834 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 057 045 Old_age Always - 28 (Min/Max 27/29) 194 Temperature_Celsius 0x0022 028 043 000 Old_age Always - 28 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 046 040 000 Old_age Always - 234016408 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 230193067201874 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 290482469 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3868205915 root@Tower:~# smartctl -A /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 165814427 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 440 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3284118 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1627 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 35 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 063 045 Old_age Always - 28 (Min/Max 26/28) 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 050 045 000 Old_age Always - 165814427 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 144392505524929 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1838164866 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2032970711 Loaded modules: root@Tower:~# lsmod Module Size Used by md_mod 44397 0 xor 12961 1 md_mod ata_piix 17455 0 mptsas 29873 0 mptscsih 14072 1 mptsas mptbase 49478 2 mptsas,mptscsih scsi_transport_sas 16613 1 mptsas piix 3524 0 e1000 75710 0 This is not same issue i see with shire's post above. Please type this command instead and post the output: smartcl -n standby -s on -A /dev/sda
June 11, 201115 yr As long as you do not have drives > 2TB, you can revert to 4.7. (by putting back your old config folder you saved and re-assigning the drives to their respective slots) I don't think so. All my disks are 2TB, and were formatted as MBR by Beta6a. Upgrading to Beta7 has converted them all to GPT, which precludes running on anything that only knows about MBRs. Cheers.
June 11, 201115 yr Author At long last, my new WD20EARS has arrived. I presume that there is no reason why I shouldn't use GPT on it in order to start testing the new functionality? I belieive the GPT partitions are only created for drives >2TiB. You can't control which drives are GPT and which are MBR. The wikipedia article on GPT is pretty good (except see note below). In unRaid, any drive with fewer than 0xFFFFFFFF sectors is partitioned using MBR, where partition 1 starts in either sector 63 or 64, and extends to the last sector. Any drive with 0xFFFFFFFF sectors or more is partitioned using GPT. In the GPT scheme: sector 0 = "protective" MBR sector 1 = GPT header sector 2..33 = GPT partition table (16K worth of storage) sector 34 = first possible sector for assignment to a partition, but in unRaid is unused sector 35..63 = also unused sectors in unRaid sector 64 = start of partition 1 In addition, in the GPT scheme, a backup copy of the GPT and GPT partition table (total of 33 sectors) is stored in the last 33 physical sectors of the hard drive. Hence, partition 1 size in sectors = (total number of sectors) - 97 Note: above is assuming the sector size is 512 bytes. The GPT spec actually refers to "blocks", and the wikipedia article generally assumes block size is 512 bytes. What's not clear in the article, but is clear from the spec, is suppose the sector size (or block size) was say 2048 bytes. In this case sector 0 is still the "protective" MBR (and all bytes in the sector beyond 512 must be padded with zeros), sector 1 is still the GPT header (padded with zeros), but the GPT partition table would only consume 8 sectors (or blocks). So the first sector usable by a partition would be sector 10. Confusing? That's what you get when a spec is developed by committee. One other point: unRaid starts partition 1 in sector 64 (instead of sector 34) to avoid the "4K block alignment" issue - learned my lesson on that one Ah, I thought that If gdisk finds a valid MBR or BSD disklabel but no GPT data, it will attempt to convert the MBR or disklabel into GPT form. from man gdisk, meant that any MBR drive could be converted to GPT. Because an existing unRaid drive smaller than 2TB uses MBR, and the size of partition 1 extends to end of disk, it's not "automatic" to convert to GPT because GPT requires 33 sectors at the end of the disk for storage of the backup GPT header and partition table. So if you really wanted to convert a <2TB unRaid disk with MBR to GPT, you would first have to start partition 1 in sector 30 (or 31 - actually to ensure 4K alignment, would probably want to start partition 1 in sector 16), move all the data, then create your GPT. But why? Absolutely no reason to. Now if you have a 3TB drive which you truncated down to 2TB in order to use in previous version of unRaid, you can do something like this: - remove the HPA - create a GPT using this command: sgdisk -o -a 64 -n 1:64:0 (this assumes partition 1 starts in sector 64). This should work but note I have not tried this - use at your own risk!
June 11, 201115 yr Author As long as you do not have drives > 2TB, you can revert to 4.7. (by putting back your old config folder you saved and re-assigning the drives to their respective slots) I don't think so. All my disks are 2TB, and were formatted as MBR by Beta6a. Upgrading to Beta7 has converted them all to GPT, which precludes running on anything that only knows about MBRs. Cheers. This should NOT have happened. Please type this command and post the output: cat /proc/partitions
Archived
This topic is now archived and is closed to further replies.