I'm a total newbie to Linux, but just installed archlinux to my GoFlex Home 3TB using these directions.
Worked like a charm, and I am able to SSH into my new ArchLinux box and login as root. Then, I followed the First Steps directions, setting up Open NTP, changing my root password, making a new Linux user, setting up sudo, and updating using pacman.
Right now, I'm trying to set up the Samba server so that I can copy files from my Windows computers onto the hard drive. I've been partially successful following this Samba Guide, but it seems to be for configuring a Pogoplug that doesn't have a built-in hard drive. So the one modification I made was to point the path to /media/. Here is my smb.conf file currently.
$this->bbcode_second_pass_code('', '[global]
workgroup = WORKGROUP
server string = ALARM
netbios name = ALARM
security = share
load printers = no
printing = bsd
printcap name = /dev/null
disable spools = yes
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = no
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=131072 SO_SNDBUF=131072 SO_KEEPALIVE
[ArchLinuxARM]
path = /media/
read only = no
public = yes
writable = yes
force user = root
')
Here's the problem. I'm currently able to see a "ArchLinuxARM" share in the "ALARM" workgroup. I'm able to copy and write files to it, but it's showing only 16 Gb of space available instead of the 3 Tb that should be there. Now, the original installation instructions seems to create a 20 gigabyte swap partition in Step 9, so I think that's what I'm seeing.
How can I reconfigure Samba to point at the big unused partition? I don't know if the 3TB size itself is a problem or not. If I run fdisk to check the partitions, it gives me some warnings... See log below.
$this->bbcode_second_pass_code('', '[root@alarm /]# /sbin/fdisk /dev/sda
WARNING: The size of this disk is 3.0 TB (3000592982016 bytes).
DOS partition table format can not be used on drives for volumes
larger than (2199023255040 bytes) for 512-byte sectors. Use parted(1) and GUID
partition table format (GPT).
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): p
Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 63 39086144 19543041 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 39086145 4294961684 2127937770 83 Linux
Partition 2 does not start on physical sector boundary.
')
Thanks in advance to anyone who can help a Linux n00b!