I messed up yesterday and hosed the MBR on my parity drive when I was trying to get a new IDE cache drive up and running. That's fixed now, but as a result I have three partitions on the cache disk (you can see them in the image), and the one in use is a tiny 209M (hda1). Eek. The other two have sizes of 250G (hda), and zero (hda2).

 

How can I fix this?

 

As soon as the disk is ready, I'll recreate the directory structure from my user shares on the cache drive so the mover script will function correctly.

 

syslog-2011-02-19.txt

hda is the whole disk, not a partition.

hda2 is actually a big unknown since it's not mounted and there is no data.

 

What do you want, a single partition?

 

The command;

 

dd if=/dev/zero count=8 of=/dev/hda

 

will remove the mbr and allow unRAID to format the drive with a single partition for you.

 

Otherwise, you need to format it with 2 partitions yourself if that's what you want. There's a thread in either the Applications or User Customization forum about formatting the cache disk with 2 partitions.

 

Peter

 

 

 

hda is the whole disk, not a partition.

hda2 is actually a big unknown since it's not mounted and there is no data.

 

What do you want, a single partition?

 

The command;

 

dd if=/dev/zero count=8 of=/dev/hda

 

will remove the mbr and allow unRAID to format the drive with a single partition for you.

 

Otherwise, you need to format it with 2 partitions yourself if that's what you want. There's a thread in either the Applications or User Customization forum about formatting the cache disk with 2 partitions.

 

Peter

 

Unfortunately, I don't know exactly what I want, other than a cache drive for speedier transfers and to install SABnzbd. I imagine a single partition is what I want.

Just start with a single partition then. You can put stuff on the cache disk by starting the directory with a period(.) and it won't be moved so it stays there.

 

Peter

 

I'm not sure this command changed anything. The settings page still appears like the image above.

 

Here's the result:

 

Tower login: root
Linux 2.6.32.9-unRAID.
root@Tower:~# dd if=/dev/zero count=8 of=/dev/hda
8+0 records in
8+0 records out
4096 bytes (4.1 kB) copied, 0.0300397 s, 136 kB/s
root@Tower:~#

I'm not sure this command changed anything. The settings page still appears like the image above.

 

Here's the result:

 

Tower login: root
Linux 2.6.32.9-unRAID.
root@Tower:~# dd if=/dev/zero count=8 of=/dev/hda
8+0 records in
8+0 records out
4096 bytes (4.1 kB) copied, 0.0300397 s, 136 kB/s
root@Tower:~#

It won't since the OS did not re-look at the partitioning on that disk yet.  It won't unless you either reboot or issue a command to have it re-read the partition table.

 

You can request it re-scan the partition table by typing

sfdisk -R /dev/hda

Alright. I shut down the array, ran the above command, restarted the array, and started formatting the disk. It completed, and the size is now correct.

 

Much thanks!