Berkeley CSUA MOTD:Entry 16826
Berkeley CSUA MOTD
 
WIKI | FAQ | Tech FAQ
http://csua.com/feed/
2024/11/23 [General] UID:1000 Activity:popular
11/23   

1999/11/4-5 [Computer/SW/OS/Windows, Computer/HW/Drives] UID:16826 Activity:moderate
11/3    Hardware Question: I bought a computer with a 17 GB IDE hard drive.
        The computer came with RedHat 6 installed.  I tried to install
        Windows and failed and screwed up Linux as well.  When I tried to
        install Linux, the install script was unable to instal LILO.
        I tried installing LILO in MBR and otherwise, neither worked.
        Windows install claims it works but when I finish windows install
        and take the CD out to reboot, it fails to boot from the hard drive.
        Now I can't install either windows or linux.  My guess is neither
        install script can modify the messed up MBR.  Any suggestions?
        \_ So many bad memories.  Lilo hates booting to anything past
           1024 cylinders.  It's an IDE thing.
        \_ Try "fdisk /mbr" or something like that.  --PeterM
        \_ it probably won't help you but I know for a fact WinNT does
           not boot off partitions greater than 7.8something GB.  This may
           be general Intel X86 problem.
                \_ Bullshit.  You're flat dead wrong.  Get off the motd.
                   \_ apologies.  I mean a 7.8something *IDE* hard disk:
               http://support.microsoft.com/support/kb/articles/Q197/6/67.ASP
               http://support.microsoft.com/support/kb/articles/Q224/5/26.ASP
               http://support.microsoft.com/support/kb/articles/Q114/8/41.ASP
                      now be nice! =) =) =D
               \_ Thanks!  This is what I needed.  I also discoverd that
                  linux and LILO work fine if you put LILO in linear mode.
                  \_ does it go slower in linear mode?
           be a general BIOS problem.  Oh yeah, lilo will say fuck you
           near the end if you want to mark a partition to be bootable
           and any part of it extends beyond the first 1024 cylinders
           (generally 7.8something GB).  Put all bootable partitions
           wholly within the first 1024 cylinders.
        \_ Boot from a dos floppy.  fdisk /mbr as peter says.  Try again.
2024/11/23 [General] UID:1000 Activity:popular
11/23   

You may also be interested in these entries...
2007/7/17 [Computer/SW/Languages/C_Cplusplus] UID:47312 Activity:nil
7/13    CSUA Life Roster
1 point each for:                                               key:
                significant other (out of county rule applies)   G
                car (Chevy Novas do count)                       C
                housing (dorms DO NOT count)                     H
                own computer running reasonable multi-tasking OS U
	...
1999/8/24-26 [Computer/Networking, Computer/SW/OS/Windows] UID:16390 Activity:very high
8/24    Question. Which ISP is good for 24 hours and is reliable? I am
        willing to spend up to $30/month. Also, which auto password and
        auto Windows 95 dialer is good to download? Thanks.
        \_ ED!  ED!  ED is the STANDARD!  Tax Advisor.
                \_ /bin/cat you fool!
        \_ $30! That's pretty steep for an ISP.  Might as well spend a
	...
1997/3/4-5 [Computer/SW/OS/Windows] UID:32088 Activity:high
3/5     Can someone please tell me why Netscape 3.01 crashes so much
        more on my NT 4.0 than my Win95?
        \_ Insufficient RAM you have?
           \_ I have 32 megs, dude. Still, NT shouldn't be crashed.
           \_ Yoda, you are not. Speak like him, you should not. Weak with
              the force you are.
	...
1997/2/12 [Computer/SW/OS/Windows] UID:32064 Activity:nil
2/12    To the person who was trying to install both NT/95:
        You can create two primary partitions, hide the second one,
        install Win95 (by default, it'll install itself on the first
        primary partition), then afterwards, you hide it and set the
        second primary partition Active/Unhide, install NT, and now,
        when you need to boot just set the Active flag on either primary
	...
2007/11/12-16 [Computer/SW/OS/Linux, Computer/SW/Unix] UID:48623 Activity:nil
11/12   how do i make a fail safe magical backup for my debian box
        that i can quickly boot from if the box explodes?
        \_ keep a linux live boot cd around for just such an emergency
           \_ And learn about 'dd'
        \_ I was hoping there was something as slick as CCC, for unix.
           \_ You can first duplicate the disk offline with dd, then just
	...
2006/6/2-4 [Computer/HW/Drives] UID:43264 Activity:low
6/2     I own a 1999 Taurus. I would like to replace the OEM in-dash
        cassette deck with a CD player that won't cost more than say $120 and
        which will have a "detacheable face". How likely is my car to be broken
        into if I do it?
        \_ The likelihood of your fancy shmancy CD player getting stolen
           10-15 years ago would be the same as those expensive fancy shmancy
	...
2005/12/30-2006/1/4 [Computer/SW/OS/Windows] UID:41180 Activity:nil 65%like:41172
12/29   A friend's primary Windows 2000 hard disk got nuked, and her
        backup drive is missing data. I'm looking for any
        recommendations for data recovery software for FAT/NTFS
        (restoring deleted files or corrupted filesystems) or
        recommendations for data recovery services in SF?
        \_ Get an external USB drive enclosure.  You want something
	...
2005/12/27-30 [Computer/HW/Drives, Computer/SW/OS/Windows] UID:41151 Activity:nil
12/27   I'm trying to help out with my mother in law's computer problems. She
        has two Windows XP computers (one desktop, one tablet pc) that she was
        using for her job before she retired. The computers themselves are old
        and her workplace doesn't want them back but they are installed with
        all this corporate Novell stuff that I don't know anything about and
        her account on the computer has very restricted permissions (she can't
	...
2005/6/22-23 [Computer/SW/OS/OsX] UID:38251 Activity:high
6/22    When I burn an iso image using the "Disk Utility" in OS X (Tiger)
        and I then use readcd on a linux box to verify the md5sum of the
        burned cd, the md5sum of the CD doesn't match the md5sum of the
        origional iso file. Is OS X modifying the iso image before it
        burns it or something? Seems strange.
        \_ Does this match on any of your other burned-CDs vs. ISO files?
	...
2005/5/18-19 [Computer/SW/Apps/Media, Computer/HW/Drives] UID:37730 Activity:nil
5/17    My second data backup question. I am looking for a backup media I can
        take off-site. I'll repeat that we've found the failure rate backing up
        to CD unacceptable. She wants to go with an Iomega product but I was
        wondering if people have had good/bad experience with these,
        reliability-wise and if they have better suggestions. I have about
        $400 for this.
	...
2005/4/1-3 [Computer/HW/Laptop, Computer/HW/Drives] UID:37032 Activity:low
4/1     I'd like to play my favorite EA game on the laptop. However, I
        don't have a CD player for my laptop and I'm wondering if it
        is possible to mount the CD on my desktop and access it via
        wireless. I know that EA has really weird CD protection
        schemes, that's why I'm wondering if anyone has successfully
        done this. -ok thx
	...
2005/3/19-20 [Computer/HW/Drives, Computer/HW/CPU] UID:36772 Activity:high
3/19    Given the choice between a firewire and USB2.0 connection
        (between an external hard drive and my computer), which one is
        better and why? Thanks.
        \_ Firewire is faster and more robust for that application.  USB
           is more widely available if you'd ever want to move the disk to
           another machine.  -tom
	...
2005/2/23-24 [Computer/SW/Security] UID:36377 Activity:very high
2/23    Hi, my girlfriend's mom is in Taiwan.  Her computer stopped booting;
        it shows BIOS, but it won't show the WinXP screen.  So, it sounds like
        a virus (less likely, partial drive failure / OS corruption, but let's
        assume it's a virus).
        She is concerned about recovering her files.
        Normally if I were on-site I'd just pull out the drive, put it in an
	...
2005/2/3-5 [Computer/HW/Memory, Computer/HW/Drives] UID:36055 Activity:moderate
2/3     So, I'm really confused about this notion of computer science
        metrics where everything's kind of 2^n, but sometimes not. For
        example, if I have a 4 GIG hard drive, does that mean I have
        exactly 2^32 bytes of space? Does that translate to 4000000000
        bytes, or some number that's close to it? How about megahertz?
        Say I have a 2.5GHz computer, does it run at exactly 2500000
	...
2005/1/18-19 [Finance/Banking, Computer/HW/Drives] UID:35762 Activity:moderate
1/18    A bunch of CD-ROMS I have are corrupted. They're in a nice
        CaseLogic case, closed, stored in a temperate (70-85F), dry
        location. I have no idea why they're corrupted, but I know
        one thing-- they've been sitting close my Sharper Image Ionizer
        [plus UV mode turned on], for maybe 6 months. I'm suspecting
        that either the ions or the UV killed them, but is it actually
	...
Cache (1215 bytes)
support.microsoft.com/support/kb/articles/Q197/6/67.ASP -> support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q197/6/67.ASP&NoWebContent=1
Discussion groups and Forums about specific Microsoft products, technologies, and services. This article was previously published under Q197667 SYMPTOMS During the installation of Microsoft Windows NT to an 8 gigabyte (GB) or larger IDE hard drive, the computer may stop responding (hang) during the format portion of setup. If the drive was previously formatted as file allocation table (FAT) and designated to be converted to NTFS file system (NTFS), the computer may hang during the conversion process. Other symptoms include the drive taking an extremely long time to format or Windows NT not recognizing the entire size of the drive. This issue only affects IDE-based drives 8 GB and larger. For more information, please see the following article in the Microsoft Knowledge Base: 24 114841 Windows NT Boot Process and Hard Disk Constraints NOTE: The system board basic input/output system (BIOS) must support and recognize drives larger than 8GB before Windows NT can access the entire drive. You can verify this ability by entering into the BIOS or contacting your system board manufacturer. STATUS Microsoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article.
Cache (4230 bytes)
support.microsoft.com/support/kb/articles/Q224/5/26.ASP -> support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q224/5/26.ASP&NoWebContent=1
Discussion groups and Forums about specific Microsoft products, technologies, and services. MORE INFORMATION The system partition is defined as the partition containing the files needed for the initial system startup. A boot partition is defined as the partition containing the system files. For Windows NT, this is the partition containing the %SystemRoot%\System32 folder. The system partition and boot partition can be on the same partition or on different partitions. Because there can be multiple operating systems installed on a single computer, a computer can have multiple boot partitions, but a computer has only a single system partition. This file is simply a renamed copy of the disk controller driver. The addressable area of the disk is determined by this driver. When an Intel-based computer first boots, a number of things occur that result in the operating system being loaded and started. This process, known as the bootstrap process, has inherent hardware and software limitations beyond which Windows NT cannot operate. During the bootstrap process, the only mechanism available to Windows NT (or any other operating system) to access the drive is a set of functions in the BIOS known as Interrupt 13 (INT13). The INT13 functions allow low-level code to read from and write to the drive by addressing a specific sector on the drive. When the INT13 architecture was developed back in the early 1980s, the possibility of multi-gigabyte hard disks was not taken into consideration. The INT13 functions define 24 bits to describe a sector on the hard disk. This breaks down to a maximum of 256 heads (or sides), 1024 cylinders, and 63 sectors. With these numbers, only 256*1024*63 (or 16,515,072) sectors can be used with INT13 functions. The INT13 functions are the only means available to the operating system to gain access to the drive and system partition until the operating system loads additional drivers that allow it to gain access to the drive without going through INT13. Note Partitions other than the system partition are not affected by the these limitations. Other operating systems, such as Microsoft Windows 95 OEM Service Release 2, Microsoft Windows 98, and Microsoft Windows 2000, can boot from larger partitions because these operating systems were written after the computer industry defined a new standard for BIOS INT13 functions (the "INT13 extensions") and implemented this new functionality on manufactured motherboards. This occurs because Setup first formats the partition using the FAT file system. If you want to use an NTFS partition, the partition is converted to NTFS after the first reboot. The FAT file system has a file system limitation (unrelated to any BIOS limitations) of 4 GB. In the future, additional limitations may come into play as well. Although the NTFS file system can address 16 exabytes of disk space in a single partition, current disk-partitioning schemes store partition information in structures that limit partitions to 2^32 sectors, or 2 terabytes, in size. The ATA hardware interface uses 28-bit addressing, which supports drives that are 2^24 sectors, or 137 GB, in size. These limitations may apply to partitions other than the system partition as well. Note that file system limitations and hardware limitations exist independently of each other, and the most restrictive of the two is the determining factor in the maximum partition size. Another factor to consider when you are troubleshooting partitioning problems is that hard disk manufacturers often use "decimal megabytes" (1 megabyte = 1,000,000 bytes), whereas Windows NT uses "binary megabytes" (1 megabytes = 1,048,576 bytes). Using both definitions of a megabyte in calculations can often account for "lost" disk space. Also, this article assumes a sector size of 512 bytes in all calculations. Although a 512-byte sector has become a de facto industry standard, it is possible that disk manufacturers could produce drives with a different sector size. This would result in a corresponding change in partition limits. Partitions are based on cylinder, head, and sector calculations, not on byte calculations. Therefore, a change in bytes per sector causes a change in bytes per partition.
Cache (8192 bytes)
support.microsoft.com/support/kb/articles/Q114/8/41.ASP -> support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q114/8/41.ASP&NoWebContent=1
Discussion groups and Forums about specific Microsoft products, technologies, and services. This article was previously published under Q114841 SUMMARY This article describes hard disk size constraints under Windows NT and Windows NT Advanced Server. To understand these constraints, it is necessary to understand both the data structures that define the disk partitions and the interactions between Windows NT and the system BIOS interface used during the hardware and operating system's boot process. MORE INFORMATION The Partition Table The data structure that describes the hard disk's partitions is known as the partition table. Each entry has 10 fields that describe the following attributes of a partition: FIELD SIZE ----------------- -------- Boot Flag 1 byte Starting Side 1 byte Starting Cylinder 10 bits Starting Sector 6 bits System Indicator 1 byte Ending Side 1 byte Ending Cylinder 10 bits Ending Sector 6 bits Relative Sectors 4 bytes Number of sectors 4 bytes System Indicator The System Indicator is used to specify the type of file system that is contained in the partition. Some common values include: VALUE FILE SYSTEM ----- ----------- 0x0B Primary Fat32 Partitions up to 2047 GB 0x0C Same as 0x0B, uses Logical Block Address Int 0x13 extensions 0x0E Same as 0x06, uses Logical Block Address Int 0x13 extensions 0x0F Same as 0x05, uses Logical Block Address Int 0x13 extensions 0x05 Extended partition 0x06 BIGDOS File Allocation Table (FAT) format. For example, an FT FAT partition has a System Indicator value of 0x86 and an FT NTFS partition has a System Indicator value of 0x87. When a member of an FT set is disabled, Windows NT sets the two highest bits. For example, a disabled FAT partition has a System Indicator value of 0xC6 and a disabled FT NTFS partition has a System Indicator value of 0xC7. Boot Flag The Boot Flag indicates which partition is active or bootable. The Boot Flag value for the active partition is set to 0x80. The Master Boot Record (described later in more detail) searches for this flag to locate the active boot sector. Starting and Ending Side, Cylinder, and Sector The Starting and Ending Side, Cylinder and Sector fields are very important with respect to how Windows NT interacts with the disk. The maximum number of Sides (read/write heads) that can be represented with 1 byte is 256. The maximum number of Cylinders that can be represented with 10 bits is 1024. The maximum number of Sectors that can be represented with 6 bits is 63 because Sectors start counting with 1 (versus Cylinders and Sides which start counting with 0). The Cylinder value, represented by 10 bits, is too large to fit into a single byte. To store 10 bits, two bits are taken from the byte which stores the 6 bit Sector value. This is particularly important because the same field sizes are employed by the INT 13 BIOS interface which defines how the system BIOS interacts with the hard disk. Relative Sectors The Relative Sectors represents the offset from the beginning of the partition table to the beginning of the partition, counting by sectors. Number of Sectors The Number of Sectors represents the total number of sectors in the partition. NOTE: The Relative Sectors and Number of Sectors fields are each 32 bits in size. Under most conditions, together they contain the same information as Starting and End Side, Cylinder, and Sector values that are represented with a total of 24 bits for Starting and 24 bits for Ending. Windows NT Boot Process On Intel-based computers, the system BIOS controls the initial operating system boot process. After the initial Power On Self Test (POST) when hardware components are initialized, the system BIOS identifies the boot device. In the case of the hard disk, the BIOS reads the first physical sector on the disk, called the Master Boot Sector, and loads an image of it into memory. The BIOS then transfers execution to that image of the Master Boot Sector. The Master Boot Record contains the partition table and a small amount of executable code. The executable code examines the partition table and identifies the active (or bootable) partition. The Master Boot Record then finds the active partition's starting location on the disk and loads an image of its first sector, called the Boot Sector, into memory. The Master Boot Record then transfers execution to that Boot Sector image. Whereas the Master Boot Record is generally operating system independent, the Boot Sector of the active partition is dependent on both the operating system and the file system. In the case of Windows NT and Windows NT Advanced Server, the Boot Sector is responsible for locating the executable file, NTLDR, which continues the boot process. The only disk services available to the Boot Sector code at this stage of system boot up are provided by the BIOS INT 13 interface. The Boot Sector code must be able to find NTLDR and file system data structures such as the root directory, the File Allocation Table (FAT) in the case of an MS-DOS FAT volume or the Master File Table in the case of an NTFS volume. These must be present within the area of the disk addressable by the 24-bit side, cylinder, sector structure used by the BIOS INT 13 interface and the partition table. NOTE: Other constraints may apply depending on the computer hardware and file system. This provides eight additional bits to represent sectors. These additional bits allow partitions to be described with up to 2^32 sectors. With a standard sector size of 512 bytes, the 32 bits used to represent the Relative Offset and Number of Sectors translates into a maximum possible partition size of 2 terabytes or (2,199,023,255,552 bytes). When partitioning a disk, Windows NT will write the correct values to the partition table fields whenever possible. When the total number of sectors in a partition exceeds the number which can be described in Side, Cylinder, Sector notation, Windows NT writes the maximum permitted values to these fields in the partition table. This prevents the system BIOS from attempting to calculate the Starting and Ending addresses based on erroneous data. If the extended sector translation feature is disabled on the adapter, it might report the following disk characteristics to the system BIOS: Cylinders: 1023, Sides: 64, Sectors: 32 which translates to about 1 gigabyte. Once Windows NT is up and running, it uses its SCSI drivers to directly interact with the disk without using the BIOS INT 13 interface. So, during normal operation the BIOS parameters are largely unimportant. However, the differences are critical if the disk is to be formatted with a single partition and used as the boot drive. Without extended translation, Windows NT notices that the disk is larger than the BIOS parameters indicate. When Windows NT partitions the drive during initial installation, the starting and ending sector addresses will be filled in with their maximum possible values. With extended translation, Windows NT will be able to write valid values for the starting and ending addresses into the partition table, and thus, the partition remains bootable. These error messages may appear when extended translation is not enabled and the Master Boot Record is unable to locate the Boot Sector of the active partition: Error loading operating system. File Systems FAT and HPFS both have internal limits of 4 GB due to the fact that they use 32-bit fields to store file sizes. NTFS uses 64-bit fields for all sizes, permitting its data structures to handle volumes up to 2^64 bytes (16 exabytes or 18,446,744,073,709,551,616 bytes). This value is the theoretical limit for the NTFS file system. Practical limits having to do with the maximum allowable partition size described above limit the size of an NTFS partition to approximately 2 terabytes. Because the 32-bit fields of the partition table refer to the number of sectors in the partition, disks with larger sector sizes translate into larger permissible partition sizes. Currently Windows NT supports sector sizes up to 4 Kilobytes. With 4KB sectors, Windows NT can support a 16 terabyte partition. As new hardware or software schemes become available, NTFS will ...