How to Add Media Director Hard Disk Device

[trimble]

I've added a new 1TB SATA hard disk to one of my Media Directors and could use some assistance in how to get it formated.

The FAQ wiki (http://wiki.linuxmce.org/index.php/Frequently_Asked_Questions#How_should_I_format_additional_hard_drives.3F) provides the command to properly format partition the drive for media files:

Code: [Select]

mke2fs -b 4096 -m 1 -j /dev/whatever
where "whatever" is the hard disk in question (hda1, sda1, etc.) and this is what I could use some help with in creating. The 1TB SATA disk on this Media Director is recognized in the Media Directors Systems Settings: Disk & Filesystems. I'm not sure whether this disk device should be (hd, sd, hd1, sd1, hda1, sda1, etc.) or how to actually create the device.

Any help appreciated.

Regards,
Mark

[tschak909]

The disk must be partitioned.

Look at dmesg after plugging in the device, to see what the device name is (sdb for example)

run fdisk /dev/sdX

and create a single partition. Write it.

then apt-get install xfsprogs

why?

You should use the XFS instead of ext3 file system to format the disk. In fact, this will be the standard file system recommended to be used for release.

then run mkfs.xfs /dev/sdX1 to format the disk.

after formatting, wait, the orbiter will ask about it.

-Thom

[trimble]

Thanks Thom.

I'm making progress. I checked dmesg and found out the drive is identified as sda. I ran fdisk /dev/sda and now have a partition sda1.

However, attempting to run either "apt-get install xfsprogs" or "sudo apt-get install xfsprogs" at the MD produced the error "E: Couldn't find package xfsprogs".

I ran "sudo apt-get install xfsprogs" at the core and it installed fine and mkfs.xfs is now in the core's /sbin, but this is not visible on the MD.

I checked the apt sources.list on the MD and it appears identical to the core's, so I'm guessing there's something blocking installs on MDs. I tried rebuilding the MD image, thinking this would replicate the current core package set on the MD, but it didn't.

What should I do to install xfsprogs on the MD?

Mark

[tschak909]

try running apt-get update

-thom

[colinjones]

Also, if you are using 0710, make sure your Ubuntu repos are old-releases.ubuntu.com as 0710 is no longer supported

[trimble]

Running a straight "apt-get update" and "sudo apt-get update" had no effect on the error, so I went into the MD's sources.list and made the following changes:

FROM
deb http://archive.ubuntu.com/ubuntu/ gutsy main restricted multiverse universe
deb http://archive.ubuntu.com/ubuntu/ gutsy-security main restricted multiverse universe
deb http://archive.ubuntu.com/ubuntu/ gutsy-updates main restricted multiverse universe

TO
deb http://old-releases.ubuntu.com/ubuntu/ gutsy main restricted multiverse universe
deb http://old-releases.ubuntu.com/ubuntu/ gutsy-security main restricted multiverse universe
deb http://old-releases.ubuntu.com/ubuntu/ gutsy-updates main restricted multiverse universe

I reran apt-get update on the MD and saw a bunch of updates load.

However, upon running "sudo apt-get install xfsprogs" I was greeted with a boatload (pages, literally) of unmet dependencies and offered the option of running "apt-get -f install" to correct. I then ran "sudo apt-get -f install xfsprogs" just to see what would happen and I again was presented with pages of packages that were going to be updated upon pressing Enter.

I didn't. I know it's "just" a diskless MD, but the wholesale upgrade of just about every package on the MD to install a package that loaded without incident on the core seems suspicious.

However, now that I think of it, there *is* a difference between the LMCE systems on the core and the MD. While I don't know much about this stuff, the core is a P4 running a standard 386 package set and the MD is an Intel Dual Core which I believe is running an AMD (kernel?) which came up as part of the MD's diskless autoconfiguration. Perhaps this explains the different behavior vis-a-vis the xfsprogs package on the core and the MD?

Mark

[colinjones]

hmmm I would start by changing the architecture type to i386 in the MD's device data, then rebuilding the image... so that both core and MD are running 32 bit. Then modify the MD's sources again. So the sudo apt-get update, then try reinstalling again.

I can confirm that I was able to install xfsprogs without any issue on both my 0710 hybrid and MD (both i386)

[trimble]

That was the problem. The MD was running an AMD64 image; once it was changed back to i386, xfsprogs installed without issues and I was able to run mkfs.xfs /dev/sda1 to format the partition. LMCE has now recognized and is managing the drive. Thanks for the help!

Cheers,
Mark