Difference between revisions of "Ext2/3 Partitions - Mounting them on the Desktop"

From NAS-Central Buffalo - The Linkstation Wiki
Jump to: navigation, search
(OS X)
(Before connecting)
Line 35: Line 35:
  
 
===Before connecting===
 
===Before connecting===
Make sure that you have ext2fsx installed.  Read its documentation before going further.
+
Make sure that you have ext2fsx installed.  Read its documentation (in the ReadMe.rtf) before going further.  Be aware that if it detects a filesystem that isn't clean, it will run fsck_ext on it automatically.
Unmount cleanly from current mount point.  Check w/ df -Th
+
 
 +
If you have the disk/partition mounted, make sure that you unmount it cleanly from current mount point.  Double check that it is unmounted by using
 +
df -Th
 +
in Linux or whatever the analogous command is in your operating system.
  
 
===Connecting and Determining diskMsN===
 
===Connecting and Determining diskMsN===

Revision as of 19:27, 14 January 2007


Contents

Why

  • If you need GUI-based access to the contents of a hard drive, or if you need to mount an ext2/3 hard drive on a computer running Windows or OS X, this page may have an answer for you. The process outlined here is useful for someone rescuing data from a backup USB hard drive, or from a data partition in a Linkstation.
  • Why would you want ext2/3 format anyway? Well Windows formats (FAT, FAT32, NTFS) have some serious limitations to them, namely filesize. For FAT the filesize limit is 2GB, and for FA32 or VFAT is it 4GB. OS X doesn't have these limitations for its HFS+, but it is a proprietary format and is not readable to many computer systems. Therefore, ext2/3 is a viable alternative. With drivers, it is readable by nearly all OS's, and it has a filesize limit that runs in the terabytes.
  • Perhaps the biggest reason for many FreeLink users is that Buffalo has for years used a proprietary ext2-like format for USB hard drives attached to the Linkstation. This format has a large filesize limit, but it does not mount under Linux, Windows or OS X. Moving to Freelink gives us the opportunity to unplug that USB drive and mount it directly to ones desktop, using the methods shown here.

Requirements

  • a USB storage device (flash, IDE or SATA) or hard drive formatted in ext2 or ext3
  • a computer running
    • OS X (10.3-10.4.x are currently supported),
    • Windows or
    • Linux/Unix
  • for OS X: ext2fsx driver from SourceForge.net
  • for Windows: explore2fs or Ext2 Installable File System For Windows
  • for Linux: Any common desktop distribution already comes with ext2/ext3 support
  • for Unix: Ask the vendor for an ext2/ext3 file system implementation

Windows

Before connecting

Connecting and Determining disk info

Mounting

Access

Unmounting

OS X

Before connecting

Make sure that you have ext2fsx installed. Read its documentation (in the ReadMe.rtf) before going further. Be aware that if it detects a filesystem that isn't clean, it will run fsck_ext on it automatically.

If you have the disk/partition mounted, make sure that you unmount it cleanly from current mount point. Double check that it is unmounted by using

df -Th

in Linux or whatever the analogous command is in your operating system.

Connecting and Determining diskMsN

Mounting

If the GUI interface provided through the Preferences Pane in OS X does not work out of the box, and seems difficult at best to get working. The command line method works well though. You must log in as administrator, make a mount directory in /Volumes, and then mount the partition. The command below are for a partition that is the first on disk2, for example.

sudo -s
mkdir /Volumes/linux
mount_ext2 -o rdonly -x /dev/disk2s1 /Volumes/linux

Access

Finder Menu Go->Go To Folder


Unmounting

umount /dev/disk2s1

Check w/ df -Th

Troubleshooting

Windows

OS X

Error messages and their possible causes:

  • Invalid argument
mount_ext2: /dev/disk3s1 on /Volumes/linux: Invalid argument

If you are using a USB drive, this may mean that you forgot to unmount (see the Unmount section above) before physically disconnecting your cable.


  • No such directory
/dev/disk3s1 on /Volumes/linux: No such file or directory

You may have forgotten to create the mount point directory in /Volumes.

References and Links