April 12, 201115 yr Hello, I am brand new to UnRaid. Just set up my first array with UnRaid version: 4.7. I pre-cleared each of my disks, then added them to the array and formatted. I've copied over all my data and everything seems to be working fine, but I'm curious about the output of fdisk -l. Here is my Parity drive: Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 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. and here is one of my data drives: Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 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. but here is my other data drive: Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 243202 1953514552 0 Empty Partition 1 does not end on cylinder boundary. It reports ID 0 and System 'Empty'?? I can see and access all the data that has gone to that drive, so everything appears to be in order. But is that something I need to be worried about? Thanks.
April 12, 201115 yr That last disk is the parity. There is no filesystem on the parity, just a partition. Peter
April 12, 201115 yr Author But in the Web UI, the parity drive is listed as sda: parity device: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD20EARS-22MVWB0_WD-WCAZA4035730
April 12, 201115 yr But in the Web UI, the parity drive is listed as sda: parity device: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD20EARS-22MVWB0_WD-WCAZA4035730 Very interesting indeed. Please attach a system log to this thread. (and a screen shot of the web-UI too if you can) There is an inconsistency in the display, that's for sure. The good news is that unRAID does not use the device name, it uses the PCI ID () in 4.7, and in the 5.0beta6a version, it uses the model/serial number of the disk itself. (The device names can change from one boot to the next based on the initial spinup time of each disk and when it announces it is ready to the OS in the boot sequence)
April 12, 201115 yr One more request... Please post output of these two commands: cat /sys/block/sdb/size dd status=noxfer count=1 if=/dev/sdb | od -Ad -t x1 Then, tell us the history of the second data drive (/dev/sdb). Did you format it yourself? Did unRAID format it? Did you format it in another system and move it to the unRAID server? Did you preclear it? or did you let unRAID clear it? or did you install it before the parity drive was installed and it was never cleared or pre-cleared? Basically there is a single "byte" in the MBR that tells the OS what kind of file-system is on the partition. It is informational, and not needed to access the partition if you know what type is there already. The "0" value is what is throwing fdisk off track. The partition should be marked as "Linux" (a value of 83) The issue is that if you were to attempt an upgrade to the 5.0beta6a release, that disk might be identified as MBR-unknown (or un-formatted). Please send Tom at lime-tech an e-mail/PM and point him to this thread. It is another clue for the resolution of the issues in upgrading from 4.X to 5.0beta6a Joe L.
April 12, 201115 yr Author Disk history is as folllows: This was a brand new HDD. I added it and the parity drive to my array before adding anything else (or reading enough documentation, apparently). I did not pre-clear it, I just added it, then formatted through the Web UI. Afterwards, I realized that this had added it as MBR:unaligned, and that I wanted MBR:4k-aligned. I switched my default setting to MBR:4k-aligned. At that point, I removed it from the array, ran preclear (specifying -A) then dropped it back in the array and formatted through the UI once again. cat /sys/block/sdb/size 3907029168 dd status=noxfer count=1 if=/dev/sdb | od -Ad -t x1 1+0 records in 1+0 records out 0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000448 00 00 00 00 00 00 40 00 00 00 70 88 e0 e8 00 00 0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa 0000512
April 13, 201115 yr Author I sent this thread to [email protected], is that who you were referring to?
Archived
This topic is now archived and is closed to further replies.