LinuxMCE Forums

Hey,

I'm trying to add an extra hard drive to my system. But LinuxMCE won't get it...
My first disk is a SSD 60GB for the system (working perfectly), my second one is a SATA 1TB.
I have followed http://wiki.linuxmce.org/index.php/Add_an_additional_hard_drive. I just needed to add xfs in the procedure?

• Insert the disk (no format, partitions....)
• sudo fdisk /dev/sdb
• Options n - 1 (defaults)
• sudo apt-get install xfsprogs xfsdump  (since by default mkfs.xfs isn't possible)
• sudo mkfs.xfs /dev/sdb1
• rebooted
• Waited for about 10 minutes

Some additional information:

sudo fdisk -l
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a16a7

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        6994    56174592   83  Linux
/dev/sda2            6994        7298     2438145    5  Extended
/dev/sda5            6994        7298     2438144   82  Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009cadb

  Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      121601   976760001   83  Linux


sudo df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                 53G   26G   25G  51% /
none                  1.5G  372K  1.5G   1% /dev
/dev/disk/by-uuid/8beeb5ef-c123-4095-a54f-d9119e9dbeeb
                      53G   26G   25G  51% /
none                  1.5G     0  1.5G   0% /dev/shm
none                  1.5G  384K  1.5G   1% /var/run
none                  1.5G     0  1.5G   0% /var/lock
none                  1.5G     0  1.5G   0% /lib/init/rw


Can i do something to force it to pick up the hard disk?

Did LinuxMCE prompt you for the HDD when you inserted it the first time?

When i inserted? No..

• I've shutdown the server
• connected the drive
• Booted up (no messages)
• Did the things above (first with mkfs without options)
• Rebooted and waited for an orbiter (refresh-refresh...)
• Removed the partition and started over (now with mkfs.xfs)
• Rebooted, and still waiting  ;)

why don t you just format it on another pc and then insert it to the core like everybody else is doing it? 

okay, I'm just a spoiled gui-brat, but when I put in a second disk, I just went to the kde-desktop and formatted it there. From then on it didn't take long for the system to detect it and ask what to do with it

Quotewhy don t you just format it on another pc and then insert it to the core like everybody else is doing it? 

Because i believe that LinuxMCE should be capable to do what all other pc's can do? And even more...  :-\


In the meantime, don't ask me why, but i needed to look at the orbiter on my core machine.
In there, i've got the message that a new disk has been found.
When i double check this on my client computer (=weborbiter), it doesn't show up. On the side, this weborbiter is working fine?

Not sure why this is happening, but when i add the disk through the 'core orbiter', it seems to work perfect?

sudo df -h

/dev/sdb2             932G  4.3M  932G   1% /mnt/device/350

Sounds correct.

The weborbiter does not always update with messages.

This would be a good dev exercise.

I would love for someone to write a "blank disk radar" and to send a detected message to the router. If sent, the configure_1790.sh script could be amended to partition and format the disk. (use XFS as the filesystem)

-Thom

Do we want lmce formatting?

I would say it's a risk for LinuxMCE to be formatting. A drive can be partitioned and formatted with other machines. But if LinuxMCE detection routines mess up, it could lead to destruction of data... And, people would be tossing blame around.

Passing a message to the user that they need to partition/format the drive is another thing.

hmm. Come on, think this through fellas, seriously, before you start spouting crap.

(1) it would be a BLANK DISK RADAR. IF THERE ARE NO PARTITIONS, THEN FIRE A DEVICE DETECTED EVENT.
(2) the DEVICE DETECTED EVENT WOULD HAVE THE CORRECT PATH OF THE DISK THAT WOULD BE PASSED TO THE CONFIGURE SCRIPT, WHICH WOULD:

(a) ADD A PARTITION TO STORE THE DATA
(b) FORMAT SAID PARTITION WITH XFS.

THIS IS A NO-BRAINER, FELLAS. COME ON!

-Thom

It's an even big risk on another computer to format/create partitions. Data can be (and is already) lost that way, no? Once you start working with computers, it's a risk.  :o

I've done these steps in LinuxMCE. Ok, with fdisk/mkfs in a console, but nevertheless it was on my 'linuxMCE machine'. If for a dark reason sdb was replace with sda, is linuxMCE responsible? At the most, it was Murphy's law... ;) And like Thom said, enough failproof things can be build in.

It would be a nice addon for linuxMCE. You add physical your new disk, and you're on your way. No worries about partitions, filesystems, formats... Another step closer for a dummy userfriendly linuxMCE?


For those who have doubts?