התקנת דיסק קשיח בממיר CUBE REVO

Hardisk partitioning on IpBox / Cuberevo / Mini
What the box expects:
The IpBbox uses a /media folder to save recordings, which is normally a mounted partition (giving a “mount” command will normally show /dev/sda2 on /media). The mounted partition can be ext2 or ext3, but ext2 works about twice as fast (important for double recordings, or simultaneous recording and playback).
Depending on what is detected on startup, /dev/sda2 can be a harddisk attached to the internal or external SATA port, or a USB-attached drive. Note that attaching a large (>4Gb) drive to the USB port may cause automatic use of this device as /dev/sda, even though a harddisk is present on the SATA.
The IpBox expects one of limited series of harddisks, so not every SATA disk will work. There´s an entry in the WIKI about working and non-working harddisks: working_cuberevo_harddrives, troublesome_cuberevo_harddrives.
How to setup a harddisk:
Method 1)
If an empty harddisk is detected, the box will try to format it automagically. Attaching a “virgin” harddisk to the SATA port will normally means that the automatic format is started once the box is booted. In this way, a 128Mb /sda1 partiton and a big /sda2 partition (the rest of the harddisk) are created, ready to be mounted once the Linux kernel starts. Later firmware versions will make both partitions ext2.
Note: formatting may take a while (up to 10 minutes for a 250Gb disk). During this time, the box may seem stuck at booting or refuse to show the “PVR preferences” menu options.
Method 2)
If the first method fails, it may help to force an automatic format of the harddisk: The option to format the harddisk at boot can be set in the “Preferences” menu under “PVR options” and is called “Format HDD at next boot”. The box is forced to go through the process described above, even though /sda1 and /sda2 are already made, so this method wil erase all recordings! Its best to check again after boot to see if the format option is turned off again.
Also here, the formatting may be “invisible” for 10-15 minutes. Give the box some time!
Method 3)
If all fails, it may be possible to do a manual format from a shell prompt. Only do this if you have some experience using a shell prompt under linux! The process is as follows:
After logging in to the box in a telnet shell, see if the harddisk is recognized by a “fdisk /dev/sda” command. You have to start fdisk with the device to work on as argument, and you will get another “command promt” style to enter commands that act on that particular device. Check if the /dev/sda point to the harddisk and not a USB drive!
If the fdisk command does not see the harddisk, it simply isn´t recognized by the box, end of story.
The “fdisk /dev/sda command” has to show the hardisk (if the system can access the device), and you can list the partitons (or empty table). Use the fdisk help to see what commands you have at your disposal, the “m” command inside fdisk will give a list of commands.
Remembering the expected layout, you can make a partiton table with two type 83 (ext2) partitions. A small one (sda1, 128Mb-1Gb) for system or swap and a big one (sda2) for media files. For now, the fdisk instructions available on http://tldp.org/HOWTO/Partition/fdisk_partitioning.html are enough to make the two partitons. Don´t forget to write the table before quitting fdisk!
After making the partitions, they can be formatted with the mkfs.ext2 command. It will be enough to give the command “mkfs.ext2 /dev/sda1”, followed by the command “mkfs.ext2 /dev/sda2”. Remember that the command may take some time to complete!
After a reboot, the correct folder should be mounted automatically on /media, and available for recordings.

http://tldp.org/HOWTO/Partition/fdisk_partitioning.html

. Partitioning with fdisk
This section shows you how to actually partition your hard drive with the fdisk utility. Linux allows only 4 primary partitions. You can have a much larger number of logical partitions by sub-dividing one of the primary partitions. Only one of the primary partitions can be sub-divided.
Examples:

1. 
   Four primary partitions (see Section 5.2)
   
2. 
   Mixed primary and logical partitions (see Section 5.3)
   

5.1. fdisk usage


fdisk is started by typing (as root) fdisk device at the command prompt. device might be something like /dev/hda or /dev/sda (see Section 2.1.1). The basic fdisk commands you need are:
p print the partition table
n create a new partition
d delete a partition
q quit without saving changes
w write the new partition table and exit

Changes you make to the partition table do not take effect until you issue the write (w) command. Here is a sample partition table:

Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders Units = cylinders of 4032 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 184 370912+ 83 Linux /dev/hdb2 185 368 370944 83 Linux /dev/hdb3 369 552 370944 83 Linux /dev/hdb4 553 621 139104 82 Linux swap

The first line shows the geometry of your hard drive. It may not be physically accurate, but you can accept it as though it were. The hard drive in this example is made of 32 double-sided platters with one head on each side (probably not true). Each platter has 621 concentric tracks. A 3-dimensional track (the same track on all disks) is called a cylinder. Each track is divided into 63 sectors. Each sector contains 512 bytes of data. Therefore the block size in the partition table is 64 heads * 63 sectors * 512 bytes er...divided by 1024. (See 4 for discussion on problems with this calculation.) The start and end values are cylinders.

5.2. Four primary partitions


The overview:
Decide on the size of your swap space (see Section 4.4) and where it ought to go (see Section 4.4.3). Divide up the remaining space for the three other partitions.
Example:
I start fdisk from the shell prompt:

# fdisk /dev/hdb

which indicates that I am using the second drive on my IDE controller. (See Section 2.1.) When I print the (empty) partition table, I just get configuration information.

Command (m for help): p Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders Units = cylinders of 4032 * 512 bytes

I knew that I had a 1.2Gb drive, but now I really know: 64 * 63 * 512 * 621 = 1281982464 bytes. I decide to reserve 128Mb of that space for swap, leaving 1153982464. If I use one of my primary partitions for swap, that means I have three left for ext2 partitions. Divided equally, that makes for 384Mb per partition. Now I get to work.

Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-621, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-621, default 621): +384M

Next, I set up the partition I want to use for swap:

Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (197-621, default 197): Using default value 197 Last cylinder or +size or +sizeM or +sizeK (197-621, default 621): +128M

Now the partition table looks like this:

Device Boot Start End Blocks Id System /dev/hdb1 1 196 395104 83 Linux /dev/hdb2 197 262 133056 83 Linux

I set up the remaining two partitions the same way I did the first. Finally, I make the first partition bootable:

Command (m for help): a Partition number (1-4): 1

And I make the second partition of type swap:

Command (m for help): t Partition number (1-4): 2 Hex code (type L to list codes): 82 Changed system type of partition 2 to 82 (Linux swap) Command (m for help): p

The end result:

Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders Units = cylinders of 4032 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 196 395104+ 83 Linux /dev/hdb2 197 262 133056 82 Linux swap /dev/hdb3 263 458 395136 83 Linux /dev/hdb4 459 621 328608 83 Linux

Finally, I issue the write command (w) to write the table on the disk.
Side topics:

• 
  Section 10.2
  
• 
  Section 10.1
  
• 
  Section 10.3
  

5.3. Mixed primary and logical partitions


The overview: create one use one of the primary partitions to house all the extra partitions. Then create logical partitions within it. Create the other primary partitions before or after creating the logical partitions.
Example:
I start fdisk from the shell prompt:

# fdisk /dev/sda

which indicates that I am using the first drive on my SCSI chain. (See Section 2.1.)
First I figure out how many partitions I want. I know my drive has a 183Gb capacity and I want 26Gb partitions (because I happen to have back-up tapes that are about that size).
183Gb / 26Gb = ~7
so I will need 7 partitions. Even though fdisk accepts partition sizes expressed in Mb and Kb, I decide to calculate the number of cylinders that will end up in each partition because fdisk reports start and stop points in cylinders. I see when I enter fdisk that I have 22800 cylinders.

> The number of cylinders for this disk is set to 22800. There is > nothing wrong with that, but this is larger than 1024, and could in > certain setups cause problems with: 1) software that runs at boot > time (e.g., LILO) 2) booting and partitioning software from other > OSs (e.g., DOS FDISK, OS/2 FDISK)

So, 22800 total cylinders divided by seven partitions is 3258 cylinders. Each partition will be about 3258 cylinders long. I ignore the warning msg because this is not my boot drive (Section 4).
Since I have 4 primary partitions, 3 of them can be 3258 long. The extended partition will have to be (4 * 3258), or 13032, cylinders long in order to contain the 4 logical partitions.
I enter the following commands to set up the first of the 3 primary partitions (stuff I type is bold ):

Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-22800, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-22800, default 22800): 3258

The last partition is the extended partition:

Partition number (1-4): 4 First cylinder (9775-22800, default 9775): Using default value 9775 Last cylinder or +size or +sizeM or +sizeK (9775-22800, default 22800): Using default value 22800

The result, when I issue the print table command is:

/dev/sda1 1 3258 26169853+ 83 Linux /dev/sda2 3259 6516 26169885 83 Linux /dev/sda3 6517 9774 26169885 83 Linux /dev/sda4 9775 22800 104631345 5 Extended

Next I segment the extended partition into 4 logical partitions, starting with the first logical partition, into 3258-cylinder segments. The logical partitions automatically start from /dev/sda5.

Command (m for help): n First cylinder (9775-22800, default 9775): Using default value 9775 Last cylinder or +size or +sizeM or +sizeK (9775-22800, default 22800): 13032

The end result is:

Device Boot Start End Blocks Id System /dev/sda1 1 3258 26169853+ 83 Linux /dev/sda2 3259 6516 26169885 83 Linux /dev/sda3 6517 9774 26169885 83 Linux /dev/sda4 9775 22800 104631345 5 Extended /dev/sda5 9775 13032 26169853+ 83 Linux /dev/sda6 13033 16290 26169853+ 83 Linux /dev/sda7 16291 19584 26459023+ 83 Linux /dev/sda8 19585 22800 25832488+ 83 Linux

Finally, I issue the write command (w) to write the table on the disk. To make the partitions usable, I will have to format (Section 10.1) each partition and then mount (Section 10.3) it.

5.4. Submitted Examples


I'd like to submit my partition layout, because it works well with any distribution of Linux (even big RPM based ones). I have one hard drive that ... is 10 gigs, exactly. Windows can't see above 9.3 gigs of it, but Linux can see it all, and use it all. It also has much more than 1024 cylenders.
Table 7. Partition layout example
PartitionMount pointSize

/dev/hda1	/boot	(15 megs)
/dev/hda2	windows 98 partition	(2 gigs)
/dev/hda3	extended	(N/A)
/dev/hda5	swap space	(64 megs)
/dev/hda6	/tmp	(50 megs)
/dev/hda7	/	(150 megs)
/dev/hda8	/usr	(1.5 gigs)
/dev/hda9	/home	(rest of drive)

I test new kernels for the USB mass storage, so that explains the large /boot partition. I install LILO into the MBR, and by default I boot windows (I'm not the only one to use this computer).

I also noticed that you don't have any REAL examples of partition tables, and for newbies I HIGHLY suggest putting quite a few up. I'm freshly out of the newbie stage, and partitioning was what messed me up the most.