June 11, 201115 yr root@The-Vault:~# cat /proc/partitions major minor #blocks name 8 0 2015232 sda 8 1 2013184 sda1 3 0 19938240 hda 3 1 19938208 hda1 8 16 1953514584 sdb 8 17 1953514552 sdb1 8 48 1953514584 sdd 8 49 1953514552 sdd1 8 32 1953514584 sdc 8 33 1953514552 sdc1 8 64 1953514584 sde 8 65 1953514552 sde1 9 1 1953514552 md1 9 2 1953514552 md2 9 3 1953514552 md3 Cheers.
June 11, 201115 yr Author root@The-Vault:~# cat /proc/partitions major minor #blocks name 8 0 2015232 sda 8 1 2013184 sda1 3 0 19938240 hda 3 1 19938208 hda1 8 16 1953514584 sdb 8 17 1953514552 sdb1 8 48 1953514584 sdd 8 49 1953514552 sdd1 8 32 1953514584 sdc 8 33 1953514552 sdc1 8 64 1953514584 sde 8 65 1953514552 sde1 9 1 1953514552 md1 9 2 1953514552 md2 9 3 1953514552 md3 Cheers. Why do you say they were converted to GPT?
June 11, 201115 yr Author Well, the fdisk output I posted here seems to think they are. Cheers. The output from that post does not match the partition list you just posted.
June 11, 201115 yr Since I posted that fdisk ouptput, I've added a drive, /dev/hda, which is NOT part of the array. I needed a disk for Plex stuff, and I don't have a cache drive. Here's the fdisk, that matches the command I just posted: root@The-Vault:~# fdisk -l Disk /dev/sda: 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/sda1 * 1 251 2013184 6 FAT16 Partition 1 has different physical/logical endings: phys=(249, 254, 63) logical=(250, 162, 40) Disk /dev/hda: 20.4 GB, 20416757760 bytes 16 heads, 63 sectors/track, 39560 cylinders Units = cylinders of 1008 * 512 = 516096 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/hda1 1 39560 19938208+ 83 Linux WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 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/sdb1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. 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. Cheers.
June 11, 201115 yr Author Since I posted that fdisk ouptput, I've added a drive, /dev/hda, which is NOT part of the array. I needed a disk for Plex stuff, and I don't have a cache drive. Here's the fdisk, that matches the command I just posted: root@The-Vault:~# fdisk -l Disk /dev/sda: 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/sda1 * 1 251 2013184 6 FAT16 Partition 1 has different physical/logical endings: phys=(249, 254, 63) logical=(250, 162, 40) Disk /dev/hda: 20.4 GB, 20416757760 bytes 16 heads, 63 sectors/track, 39560 cylinders Units = cylinders of 1008 * 512 = 516096 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/hda1 1 39560 19938208+ 83 Linux WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 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/sdb1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. 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. Cheers. Before upgrading to -beta7, was your array operating normally with valid parity? After upgrading to -beta7, did all your drives appear "normal" with green indicators?
June 11, 201115 yr Author Yes, and yes. Cheers. Everything in your listings look completely normal except for this message: WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted. So let's take a different approach. Let's use the 'fdisk' command in an interactive fashion, capture the output of your telnet session and post. First type: fdisk -v Then fdisk /dev/sdb This will start up fdisk in interactive mode. Next you will type this series of single-character commands: p x p d q The last command, 'q', quits fdisk. Please post all output generated. Thanks!
June 11, 201115 yr I upgraded from 4.7 to 5.0 beta 7 and everything is working fine. Ran a parity check and it is fine with no errors. Only problem is the Main Unraid link in unmenu doesn't work but Joe L knows about that and it doesn't affect 5.0 beta 7 Great job
June 11, 201115 yr I have noticed one thing though, not sure if its a bug or me not doing something right. I am using AFP and it seems to be working fine, however SMB is also showing up, how do I only get AFP to show up in Finder on the Mac?
June 11, 201115 yr root@The-Vault:~# fdisk -v fdisk (util-linux-ng 2.17.2) root@The-Vault:~# fdisk /dev/sdb WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): p Disk /dev/sdb: 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/sdb1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Command (m for help): x Expert command (m for help): p Disk /dev/sdb: 1 heads, 63 sectors, 62016336 cylinders Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID 1 00 0 0 0 0 0 0 64 3907029104 83 Partition 1 does not end on cylinder boundary. 2 00 0 0 0 0 0 0 0 0 00 3 00 0 0 0 0 0 0 0 0 00 4 00 0 0 0 0 0 0 0 0 00 Expert command (m for help): d Device: /dev/sdb 0x000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1C0: 00 00 83 00 00 00 40 00 00 00 70 88 E0 E8 00 00 0x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA Expert command (m for help): q It seems strange that fdisk complains that GPT is not supported, but still carries on. Everything looks like a valid MBR to me. Perhaps there's a rouge "flag" somewhere that's making fdisk think it's GPT, when it's really not. Cheers.
June 11, 201115 yr Author root@The-Vault:~# fdisk -v fdisk (util-linux-ng 2.17.2) root@The-Vault:~# fdisk /dev/sdb WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): p Disk /dev/sdb: 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/sdb1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Command (m for help): x Expert command (m for help): p Disk /dev/sdb: 1 heads, 63 sectors, 62016336 cylinders Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID 1 00 0 0 0 0 0 0 64 3907029104 83 Partition 1 does not end on cylinder boundary. 2 00 0 0 0 0 0 0 0 0 00 3 00 0 0 0 0 0 0 0 0 00 4 00 0 0 0 0 0 0 0 0 00 Expert command (m for help): d Device: /dev/sdb 0x000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1C0: 00 00 83 00 00 00 40 00 00 00 70 88 E0 E8 00 00 0x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA Expert command (m for help): q It seems strange that fdisk complains that GPT is not supported, but still carries on. Everything looks like a valid MBR to me. Perhaps there's a rouge "flag" somewhere that's making fdisk think it's GPT, when it's really not. Cheers. Is it possible that sometime in the past history of these drives a GPT might have been written to them? In looking at the code for the 'fdisk' program, all it does is look for this value: 0x5452415020494645 (which is ascii for "EFI PART") in the first 8 bytes of LBA 1 (which is location of the GPT header for GPT-partitioned disks) and/or the first 8 bytes of the last physical LBA on the disk (which is the location of the backup GPT header with GPT-partitioned disks). If it sees this signature in either place, it outputs that warning message. I guess you could verify it by doing a hex dump of sector 1: dd if=/dev/sdc count=1 skip=1 of=junk hexdump -C junk If not there, could look in the last sector. Bottom line is this is a bogus message being output by fdisk. EDIT: I should add, when unRaid writes a MBR partition table, it does not touch the sectors between the MBR and the start of partition 1 - it leaves them as-is, so if sometime in the past a GPT was written to the disk, that GPT header will still exist in sector 1. Ditto when writing a GPT - the sectors between the end of the GPT partition table and the start of partition 1 are not written. EDIT 2: To add to what I added - even if there is a remnant GPT header in sector 1, but the MBR is "valid", then the rest of linux OS does the right thing: interprets the MBR partition table. In order for linux to interpret a GPT, the MBR must be in the format of a so-called "protective MBR" as documented in the wikipedia article.
June 11, 201115 yr root@The-Vault:~# dd if=/dev/sdc count=1 skip=1 of=junk 1+0 records in 1+0 records out 512 bytes (512 B) copied, 3.9666e-05 s, 12.9 MB/s root@The-Vault:~# hexdump -C junk 00000000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...| 00000010 b4 37 50 65 00 00 00 00 01 00 00 00 00 00 00 00 |.7Pe............| 00000020 af 88 e0 e8 00 00 00 00 22 00 00 00 00 00 00 00 |........".......| 00000030 8e 88 e0 e8 00 00 00 00 af 2b 46 e6 30 83 e0 11 |.........+F.0...| 00000040 b3 c6 00 e0 81 41 ae ca 02 00 00 00 00 00 00 00 |.....A..........| 00000050 80 00 00 00 80 00 00 00 6a d2 c3 64 00 00 00 00 |........j..d....| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 Spot on. Previously these disks were part of an ZFS array in NexentaStor and I don't know what kind of disk label that would write, but it sure looks like it uses GPT. Maybe I should zap those sectors with zeros, to "clean" them up. Cheers, and Thanks.
June 11, 201115 yr Author root@The-Vault:~# dd if=/dev/sdc count=1 skip=1 of=junk 1+0 records in 1+0 records out 512 bytes (512 B) copied, 3.9666e-05 s, 12.9 MB/s root@The-Vault:~# hexdump -C junk 00000000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...| 00000010 b4 37 50 65 00 00 00 00 01 00 00 00 00 00 00 00 |.7Pe............| 00000020 af 88 e0 e8 00 00 00 00 22 00 00 00 00 00 00 00 |........".......| 00000030 8e 88 e0 e8 00 00 00 00 af 2b 46 e6 30 83 e0 11 |.........+F.0...| 00000040 b3 c6 00 e0 81 41 ae ca 02 00 00 00 00 00 00 00 |.....A..........| 00000050 80 00 00 00 80 00 00 00 6a d2 c3 64 00 00 00 00 |........j..d....| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 Spot on. Previously these disks were part of an ZFS array in NexentaStor and I don't know what kind of disk label that would write, but it sure looks like it uses GPT. Maybe I should zap those sectors with zeros, to "clean" them up. Cheers, and Thanks. Ok, mystery solved! In unRaid that remnant GPT is harmless; it's up to you if you want to zap it. Probably I would just leave it be
June 11, 201115 yr Author Perhaps unRAID could zap this to prevent future confusion? The bug is in fdisk and I really resist putting in 'hacks' to work around bugs in other components unless absolutely necessary. A better solution might be to delete the fdisk program
June 11, 201115 yr Hi! 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! No problem. Sorry for bothering you again....but are you aware of the LOGROTATE error which occurs at 4.40 every night? Jun 9 13:51:32 Tower kernel: mdcmd (201): spindown 6 Jun 9 14:05:35 Tower kernel: mdcmd (202): spindown 2 Jun 9 14:38:54 Tower kernel: mdcmd (203): spindown 7 Jun 9 18:30:14 Tower kernel: mdcmd (204): spindown 0 Jun 9 18:30:14 Tower kernel: mdcmd (205): spindown 1 Jun 9 18:30:15 Tower kernel: mdcmd (206): spindown 3 Jun 9 18:30:16 Tower kernel: mdcmd (207): spindown 4 Jun 10 01:08:52 Tower kernel: mdcmd (208): spindown 3 Jun 10 01:11:34 Tower kernel: mdcmd (209): spindown 0 Jun 10 01:20:16 Tower kernel: mdcmd (210): spindown 1 Jun 10 01:26:48 Tower kernel: mdcmd (211): spindown 4 Jun 10 04:40:01 Tower logrotate: ALERT - exited abnormally. Jun 10 15:52:59 Tower kernel: mdcmd (212): spindown 6 Jun 10 19:08:01 Tower kernel: mdcmd (213): spindown 1 Jun 10 19:08:03 Tower kernel: mdcmd (214): spindown 2 Jun 10 19:08:04 Tower kernel: mdcmd (215): spindown 5 Jun 10 19:08:04 Tower kernel: mdcmd (216): spindown 7 Jun 10 20:18:48 Tower kernel: mdcmd (217): spindown 6 Jun 10 20:26:30 Tower kernel: mdcmd (218): spindown 4 Jun 10 20:53:16 Tower kernel: mdcmd (219): spindown 0 Jun 10 20:53:16 Tower kernel: mdcmd (220): spindown 3 Jun 10 22:30:05 Tower kernel: mdcmd (221): spindown 3 Jun 11 01:40:31 Tower kernel: mdcmd (222): spindown 0 Jun 11 01:40:31 Tower kernel: mdcmd (223): spindown 3 Jun 11 01:40:32 Tower kernel: mdcmd (224): spindown 4 Thanks Tom! Bye.
June 11, 201115 yr Wow, how awesome and unexpected the 3TB support. To the folks who have already tried 3TB drives successfully with 5.0-beta7, are you using any old Unraid-compatible motherboards or have you had to upgrade? My other question (and, yes, I hate being *that* guy): when should we expect the v5 official release? I'd love to upgrade, but I would like to wait until it's out of beta. Thanks!
June 12, 201115 yr Wow, how awesome and unexpected the 3TB support. To the folks who have already tried 3TB drives successfully with 5.0-beta7, are you using any old Unraid-compatible motherboards or have you had to upgrade? My other question (and, yes, I hate being *that* guy): when should we expect the v5 official release? I'd love to upgrade, but I would like to wait until it's out of beta. Thanks! as far as i know, only one person has done anything with a 3TB drive. I do not think that proves it is stable... but it is a start
June 12, 201115 yr Linux supports GPT drives. This is not "beta". UnRaid support includes - properly initializing new disks - maintaining parity - successfully rebuilding (and upsizing if appropriate) including from MBR to larger GPT disks In my testing, this version does all these functions successfully (except for the bug I reported earlier). Whether your particular MB / controllers support >2T drives is a different topic. My prior testing (see HERE) showed that even older MBs (at least those I tested which were for Intel CPUs) and most add on controllers (except the BR10i in my testing) DO support the larger disks. There is currently no preclear for 3T drives. Although the current preclear will work and run the disk through its paces, it does not leave it with a valid preclear signature for rapid add to the array.
June 12, 201115 yr Author In my testing, this version does all these functions successfully (except for the bug I reported earlier). Which post are you referring to?
June 12, 201115 yr Does the beta7 release still consider an MBR in use under 4.7 as described in this post as unknown?
June 12, 201115 yr this "bug" is still being reported, although it probably does not affect the data in the unRAID array unless the syslog fills all available memory. Jun 8 04:40:01 Tower logrotate: ALERT - exited abnormally.
June 12, 201115 yr Hi! this "bug" is still being reported, although it probably does not affect the data in the unRAID array unless the syslog fills all available memory. Jun 8 04:40:01 Tower logrotate: ALERT - exited abnormally. Yeah...I know. Hoping to see this fixed anyway.:-) Bye.
June 12, 201115 yr In my testing, this version does all these functions successfully (except for the bug I reported earlier). Which post are you referring to? Read this post that explains the steps leading up to the bug: Prior Post And this post that explains the bug (sync errors after rebuild of MBR to GPT): Bug described here
Archived
This topic is now archived and is closed to further replies.