<br><H3><A NAME="7.3">7.3 My formatted disk has much less space then advertised!</A></h3><i>filesystem, overhead</i>
<br><i>disk space</i>
<br><i>space, disk</i>
<br><i>filesystem, space</i>
<br>
<br>Let's assume you bought a disk drive advertised with 400 MB unformatted capacity. Vendors are not consistent with the MB definition. You may have much less space less than you think you have. Which of the following did you buy?
<br>(for Quantum drives the following is true: Quantum defines 1MB to be exactly 1000000 Bytes).
<br>
<br>The disk must be formatted. This is often done by the vendor, but occasionally by the user. Formatting maps the disk into sectors. Space is reserved for the disk geometry and bad sectors. Formatting can take 10-20% of the capacity depending on the sector size. Common sector sizes are 512 and 1024. Generally, bigger sectors mean less waste.
<br>
<br>Once formatted, the UNIX file system must be created. On the NeXT, this is one of the steps performed by the BuildDisk application. It invokes the mkfs command to make a file system. This reserves space for the UNIX file system (e.g., superblocks, inode tables). This overhead can take another 2-3% of the available disk space.
<br>
<br>If you issue the df command, you may be surprised to see another 10 the available disk space has disappeared. The df command shows the total, used, and available disk space. The df units are in kbytes (1024 bytes). The sum of the used and available numbers will generally be about 10 allow the UNIX file system to be efficient in its storage allocation. If your disk fills up, only the superuser can store files in the remaining 10%.
<br>
<br>To complete the picture, here's a snapshot of what may occur:
<br>For more information, refer to the df and mkfs man pages.
<br>
<br><H3><A NAME="7.4">7.4 Can't initialise my disk within the Workspace</A></h3><i>initializing</i>
<br>
<br>Sometimes there are problem initializing disks. This only occurs if the disk is already formatted, but in a different format, e.g. the sector size was changed etc.
<br>
<br>Mostly you can overcome this problem by using the <TT>sdformat</TT> utility available on the FTP sites. (<B>Not</B> <TT>sdform</TT> by NeXT, which is incapable to do this). After using <TT>sdformat</TT>, you should be abel to further format the media within Workspace.
<br>
<br><H3><A NAME="7.5">7.5 Initialing Opticals for NeXT</A></h3><i>OD, NeXT</i>
<br><H3><A NAME="7.6">7.6 How to use a tape drive ?</A></h3><i>tape drive</i>
<br>
<br>Using Configure.app add the SCSITape driver to support any SCSI tape drives in the "Others" config.
<br>
<br><H3><A NAME="7.7">7.7 How to recover from an partially formatted disk?</A></h3><i>recover, disk</i>
<br>
<br>Often people (mostly on Intel) complain about a formatted disk (sometimes partially) due to an installation process error of some other OS. There is a chance to recover most of the data. The following assumes you are on Intel, other hardware user have to handle things much less complicated, but the way is similar:
<br><ul><LI>Prepare a new hard drive for booting
<br>
<br><LI>Don't try to repair the broken drive!
<br>
<br><LI>On Intel run <TT>fdisk</TT> to repartition the drive as it was before. If you are not able to do this, you are lost. Delete all evtl. new created partitions. By repartitioning, you won't loose data on the drive.
<br>
<br><LI>Run <TT>disk</TT> on the broken drive e.g. type <TT>disk -rsd1h</TT>.
<br>
<br><LI>Now scan the disk for superblocks by entereing the <TT>scan</TT> command at the interactive <TT>disk</TT> command prompt.
<br>
<br><LI>If your disk was partially formatted, use a higher superblock number to supply fsck with an new superblock. E.g. if a superblock was found at 3145 use <TT>fsck -b3145 -y /dev/sd1a</TT> (assuming the first partition is the broken one).
<br>
<br><LI>After this run, it is most important to reboot without syncing the drives! E.g. just turn off the computer without shutting down, or use the <TT>reboot -n</TT> command.
<br>
<br><LI>After rebooting the run <TT>fsck</TT> again, if it isn't done by the system itself.
<br>
<br><LI>You should be able to access the drive again now. Recovered files are placed in the <TT>/lost+found </TT> directory.
<br></ul><img src="/images/trans.gif" border=0><h3><A NAME="7.8">7.8 What about the ZIP drive?</A></h3><i>IOmega, ZIP</i>
<br><i>ZIP drive</i>
<br>
<br>There are frequently asked questions about the IOmega ZIP drive. One question will be answered here: 'Yes, it works with NEXTSTEP'.
<br>
<br>For other question I'd like to point you to the ZIP-drive FAQ: <tt> <a href=http://www.radical.com/TheSolutions/RadicalSolution4.html target=_blank><u>http://www.radical.com/TheSolutions/RadicalSolution4.html</u></a></TT>
<br>
<br><H3><A NAME="7.9">7.9 How to partition a 4GB drive</A></h3><i>4GB drive</i>
<br><i>2GB partition limit</i>
<br><i>Quantum sizes</i>
<br>
<br>If you are going to use large drives (greater 2GB) you need to partition this drive (true at least for OS versions up to 4.0). These are the common ways to go without too much trouble and it provides an very easy way for 4GB drives under NS3.3.
<br>
<br>1. Solution: disktab
<br><ul><LI>If you need more than 3 partitions, you have to write a disktab entry! Using fdisk (Intel systems only) has no effect.
<br>
<br><LI>On how to write a disktab entry, read the NeXTanswers (search for partition)
<br>
<br><LI>other pointers are: <TT>'scsimodes'</TT> and <TT>'man disktab'</TT>.
<br></ul>2. Solution: installation on drive to partition
<br><ul><LI>for Quantum drives the following is true: Quantum defines 1MB to be exactly 1.000.000 bytes. So if you are suited best by using 2 partitions on a Quantum Atlas 34300 (4.3GB drive-Quantum size, 4GB+5MB real size)
<br>
<br><LI>2 partitions are automatically handled on all NS3.3 platforms
<br>
<br><LI>To easily install the drive by not writing a disktab entry do the following:
<br>
<br>1) disconnect all other drives and connect the 4GB drive with ID 0
<br>
<br>2) start a plain NS3.3 installation via disks and the CD-ROM
<br>
<br>3) when the installation of files starts (text based output) you may break the procedure (the disk will get fsck'ed later) or wait until the system reboots and hangs <TT>:-)</TT> (no fsck needed then)
<br>
<br>4) you should previously have read some line telling you: <TT>initializing sd0b</TT>
<br>
<br>5) now reconnect your old boot drives and restart NEXTSTEP with the old boot drives. Switch the 4GB drive to a different ID.
<br>
<br>6) Only the first partition of the 4GB drive will get mounted automatically, this is due to a documented bug in the automounter.
<br>
<br>7) to permanently mount both partitions, add your drive partitions to the <TT>/etc/fstab</TT> file. Test mounting and umounting by hand first.
<br>
<br>8) everything should work fine now after a second reboot, and if you set up your fstab file correctly, both partitions will get mounted.
<br>
<br><LI>To switch the boot partition to the new 4GB drive continue with:
<br>
<br>1) only the first partition is bootable (you'll notice that by doing a <TT>ls -l</TT> on the mount entry --- there is the <TT>'t'</TT> file mode)
<br>
<br>2) <TT>(cd / ; gnutar -clf -)|(cd <1.partition>; gnutar -xvpf -)</TT> This transfers your root <B>partition</B> to the new partition.
<br>
<br>3) now try a boot from the new drive, by entering in the boot prompt: <TT>sd(x)mach_kernel</TT> (<TT>bsd</TT> for NeXT)
<br></ul><img src="/images/trans.gif" border=0><h3><A NAME="7.10">7.10 How to mount/ignore a disk during boot</A></h3><i>fstab</i>
<br><i>mount, during boot</i>
<br><i>disk, protection</i>
<br><i>protection, disk</i>
<br><i>disk, ignore</i>
<br><i>foreign filesystems</i>
<br><i>filesystem, ignore</i>
<br>
<br>If you just format a new disk attached to your computer, it will get automounted by the Workspacemanager and unmounted when you log out. To utilize the disk during the boot process or to have fixed pathes and protections you need to create an entry in <TT>/etc/fstab</TT> for the drive. See the Unix manual pages for more details.
<br>
<br>This is also the solution for ignoring disks or partitions of a disk with a foreign filesystem, which the Workspacemanager otherwises would prompt you for formatting.
<br>
<br>A common mistake for <TT>/etc/fstab</TT> is to inlcude the <TT>noauto</TT> keyword in subsequent mounts. Don't include this keyword for further mount entries!
<br>Argh. Yes it's true. The original NEXTSTEP/OPENSTEP drivers can't read multisession CD-ROMs. Only the first session can be used. If it is audio, CDPlayer is started if it's data it is just automounted to become accessable though Worksapce manager.
<br>
<br>Luckily there is a commercial driver out there, which enables NEXTSTEP/OPENSTEP to take advantage of multisession CD-ROMs.
