February 18, 201115 yr I threw in an old 250gb WD IDE drive to use as a cache disk. It's mainly to run sabnzbd, but the added write performance will be nice too. At one point it was mounted and part of the array, but then I ran through some of the steps to install sabnzbd which were ultimately unsuccessful. I was back tracing my steps, and realized I had not formatted that IDE disk from its old NTFS format. I tried some commands I found on a page about Linux, but now the array will not start. When I click Start, the disks show as Mounting, but a refresh just a couple seconds later will show the Mounting progress is gone. As of now, I have removed that IDE disk and the unRAID main is the same as below, except the cache disk is not listed. If I remove the IDE drive using the Devices page, then Start the array again, same result. I found a thread that had a similar syslog error to what I can see in mine: I ran the commands Joe L. recommended and got this: Tower login: root Linux 2.6.32.9-unRAID. root@Tower:~# dd if=/dev/hda count=1 | od -x -A d 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000432 0000 0000 0000 0000 0000 0000 0000 fe00 0000448 ffff feee ffff 0001 0000 596f 1d1c 0000 0000464 0000 0000 0000 0000 0000 0000 0000 0000 * 0000496 0000 0000 0000 0000 0000 0000 0000 aa55 1+0 records in 1+0 records out 512 bytes (512 B) copied, 0.0258951 s, 19.8 kB/s 0000512 root@Tower:~# fdisk -l /dev/hda WARNING: GPT (GUID Partition Table) detected on '/dev/hda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/hda1 1 30402 244198583+ ee EFI GPT root@Tower:~# hdparm -N /dev/hda /dev/hda: The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device. READ_NATIVE_MAX_ADDRESS_EXT failed: Invalid argument root@Tower:~# The GNU Parted thing looks promising. In the syslog, this one is what I'm concerned about: Feb 18 00:21:25 Tower kernel: md: do_run: lock_rdev error: -6 syslog.txt
February 18, 201115 yr From your description it appears as if you might have overwritten the MBR on the wrong disk. The syslog does not indicate which of the disks it is, but you can run the fdisk -l -u /dev/sdX on each of your disks in turn to see which no longer contains a single partition starting on sector 63. Then, you'll need to fix it. Easiest way is probably to fake its failure (by un-assigning it and starting the array without it) and then stopping the array once more and re-assigning it.) Joe L.
February 18, 201115 yr Author root@Tower:~# fdisk -l -u /dev/sda Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xb1e1f954 Device Boot Start End Blocks Id System root@Tower:~# fdisk -l -u /dev/sdb Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 63 3907029167 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -l -u /dev/sdc Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -l -u /dev/sdc Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -l -u /dev/sdd Disk /dev/sdd: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -l -u /dev/sde Disk /dev/sde: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 63 3907029167 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -l -u /dev/sdf Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdf1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary.
February 18, 201115 yr Author What started this was the thinking that I needed to format the new IDE disk. Is that actually correct? And if so, how can I do that?
February 18, 201115 yr What started this was the thinking that I needed to format the new IDE disk. Is that actually correct? And if so, how can I do that? No, you NEVER need to format any disk in unRAID unless it will have nothing to do with the array itself. It appears as if /dev/sda has no partition defined.
February 18, 201115 yr Author Alright, I'll follow the steps from above. Will a parity check or whatever it's called be required?
February 18, 201115 yr What started this was the thinking that I needed to format the new IDE disk. Is that actually correct? And if so, how can I do that? No, you NEVER need to format any disk in unRAID unless it will have nothing to do with the array itself. It appears as if /dev/sda has no partition defined. I think that is your parity disk. You somehow managed to delete the partition. You can un-assign the parity drive on the devices page Then start the array without it being assigned (this will cause unrAID to forget its model/serial number) IT should start. Then stop the array Then re-assign the parity drive. (This should re-create the partition) The start the array and let it re-write parity to the parity disk (It will basically be re-writing what is already there, but I have no idea what else you might have done, so let it continue to completion) Joe L.
February 18, 201115 yr Author I looked at the fdisk results for a solid five minutes, but didn't understand the differences between them. Thanks for the assist. Parity-Sync in progress at 57,083 KB/sec.
February 18, 201115 yr I looked at the fdisk results for a solid five minutes, but didn't understand the differences between them. Thanks for the assist. Parity-Sync in progress at 57,083 KB/sec. fdisk on dev/sda did not show a partition defined starting on sector 63 or 64. Joe L.
February 18, 201115 yr Author I looked at the fdisk results for a solid five minutes, but didn't understand the differences between them. Thanks for the assist. Parity-Sync in progress at 57,083 KB/sec. fdisk on dev/sda did not show a partition defined starting on sector 63 or 64. Joe L. Oh, right there under Device Boot. There is nothing there...
February 19, 201115 yr Author Feb 18 18:45:42 Tower kernel: md: sync done. time=34731sec rate=56246K/sec No sync errors. Thanks Joe. Now, what to do with this IDE disk? /dev/hda WDC_WD2500JB-00EVA0_WD-WMAEH2459413 /dev/hda1 WDC_WD2500JB-00EVA0_WD-WMAEH2459413 reiserfs /dev/hda2 WDC_WD2500JB-00EVA0_WD-WMAEH2459413-part2 hfsplus reiserfs and hfsplus are the indicated file systems. I've pretty much wasted ten hours trying to make something happen without a better understanding of the consequences. So what should I do to that drive?
Archived
This topic is now archived and is closed to further replies.