2.1-TB limitation on hdd space for older computers

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

I always thought the reason that one couldn't swap the hard drive between computers was because Microsoft didn't want you to do that, since it would be one less rental of their operating system.

[goontron]

Re: 2.1-TB limitation on hdd space for older computers

I always thought the reason that one couldn't swap the hard drive between computers was because Microsoft didn't want you to do that, since it would be one less rental of their operating system.

thats why they didn't fix it.

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

I installed both hard drives into another Dell computer. Same situation: no desktop icon; GParted shows the device, but when selected GParted reports No devices detected. I can't mount a drive that is not there.

I will try to set up an operating system on the second drive, to see if it can operate as a single drive.

[goontron]

Re: 2.1-TB limitation on hdd space for older computers

I installed both hard drives into another Dell computer. Same situation: no desktop icon; GParted shows the device, but when selected GParted reports No devices detected. I can't mount a drive that is not there.

I will try to set up an operating system on the second drive, to see if it can operate as a single drive.

what is the output of "uname -a"

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

The output of fdisk -l is same as before, and sdb is not listed.

I tried to change a setting in BIOS. I have been doing a lot with these two computers in the last few days, so I can't say what original settings were. That said, the setting for SATA Operation is now on "RAID Autodetect / ATA". I tried to change this to the factory default, namely, "RAID Autodetect / AHCI". I received a severe warning about this change
"SATA Operation is being changed. Attention! Changing this setting may prevent your operating system from booting or require a reinstall. Are you sure you would like to continue? Discard or Accept"

I don't want to dwell on the fact that two days ago, I unwittingly obliterated my partitions, and rendered the original hard drive as unallocated disk space. I did recover from this crisis with no damage. But I want to be extra careful not to do anything like that again.

So I have to ask, how is this setting change going to affect my operating system?

[goontron]

Re: 2.1-TB limitation on hdd space for older computers

what is the output of "uname -a"? your kernel might be too old!

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

#uname -a
Linux puppypc 2.6.32 #1 SMP Tues May 10...2011 i686 GNU/Linux

from another forum:
Basically AHCI is a newer way to interface with the SATA controller. This allows you to take advantage of SATA features such as Native Command Queuing (basically, you give your hard drive a bunch of commands, and let it figure out the best order to run them in to increase total throughput... without command queuing, the operating system can only send one command at a time, and the OS really has very little idea how to do this in the optimum order... this helps most when you are accessing data scattered over the drive rather than in order... if you run multiple programs that both use the disk it'll help, but it will have little effect when playing a movie off the hard drive), there are some other features that are enabled, but are more appropriate for desktops. The downside is you need updated drivers (which are apparently not on the BART cd).

In ATA mode, the SATA controller is basically pretending to be Intel's last generation parallel ATA controller. Weather or not you have real performance differences between the two modes probably depends on exactly how you use your disk drive, so you may want to try it out (if your Operating System doesn't get spooked by the change). Additionally, you should be happy you have the option, I have a Latitude D520, which doesn't have this option, and I'm stuck in ATA mode, when command queuing could really help me out.

[goontron]

Re: 2.1-TB limitation on hdd space for older computers

your kernel is too old. >2TB exists in kernel 2.6.35 and newer.

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

">2TB exists in kernel 2.6.35 and newer"

I don't understand what you mean. Do you mean, I can exceed 2TB using a newer kernel? If the limitation is per drive, I do not exceed the limitation.

[goontron]

Re: 2.1-TB limitation on hdd space for older computers

the limitation for your kernel is 2TB minus one sector, hence why its not seeing it.
they implemented greater than 2TB -1 sector in kernel 2.6.35.
sorry about the confusion, im running on ~2 seconds of sleep.

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

I have fully installed Linux operating system on the second drive, operated as a single drive. It is working fine. Everything is nominal in GParted.

So if I run an OS on a live CD with a kernel 2.6.35 or newer, the second drive will be detected?

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

Right now, I am deleting the OS partition, sda1, and the swap partition. I am also formatting the data partition sda2, which I have previously created with GParted. I notice that when I select to format the partition, the progress description in italics is "creating a new ext3 file system." This description is identical to setting up the partition from unallocated space, creating the partition as ext3. It takes about as much time to format a partition as it takes to create it. This is why I have always assumed that formatting is redundant when setting up a partition with GParted. Even so, I often do format, just to be sure.

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

Yes, indeedie, it was a kernel issue. I am running Linux kernel 3.2.23 as live CD, and the second hard drive shows up as an icon. GParted detects the drive as well.

I'm working with a live CD of the first candidate for replacement OS. The second drive is detected and accessible. The kernel is 2.6.32.59. So goontron, did you perhaps mean 2.6.32.35 as the first kernel to detect >2TB? (And thanks for the nudge in the right direction.)

As long as I am going to nuke the Linux OS on /dev/sda1, would it be okay to change the SATA Operation setting in BIOS, from "RAID Autodetect / ATA" to "RAID Autodetect / AHCI"?

[Per Hansson]

Re: 2.1-TB limitation on hdd space for older computers

Yes for sure if you nuke the install you can change to AHCI, and I recommend it, you will see better performance.
That being said you can usually switch from IDE > AHCI in Linux without issues.

It can be done it Windows aswell, but it takes a bit more planning. (It's usually not "plug & play")

Now for practice take a look in your messages logfile to see if the system has said anything about the HDD being unsupported, e.g:

grep sdb /var/log/messages

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

This is for kernel 2.6.32.59 (installed to hdd)
# grep sdb /var/log/messages
Jul 29 17:00:24 puppypc4609 user.notice kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Jul 29 17:00:24 puppypc4609 user.notice kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Jul 29 17:00:24 puppypc4609 user.notice kernel: sd 1:0:0:0: [sdb] Write Protect is off
Jul 29 17:00:24 puppypc4609 user.debug kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jul 29 17:00:24 puppypc4609 user.notice kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 29 17:00:24 puppypc4609 user.info kernel: sdb:
Jul 29 17:00:24 puppypc4609 user.warn kernel: sdb2
Jul 29 17:00:24 puppypc4609 user.notice kernel: sd 1:0:0:0: [sdb] Attached SCSI disk

Here is for kernel 3.2.33 (running as live CD)
# grep sdb /var/log/messages
Jul 30 08:12:29 puppypc6720 user.notice kernel: [ 2.165728] sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Jul 30 08:12:29 puppypc6720 user.notice kernel: [ 2.165730] sd 1:0:0:0: [sdb] 4096-byte physical blocks
Jul 30 08:12:29 puppypc6720 user.notice kernel: [ 2.165762] sd 1:0:0:0: [sdb] Write Protect is off
Jul 30 08:12:29 puppypc6720 user.debug kernel: [ 2.165764] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jul 30 08:12:29 puppypc6720 user.notice kernel: [ 2.165779] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 08:12:29 puppypc6720 user.info kernel: [ 2.213701] sdb: sdb2
Jul 30 08:12:29 puppypc6720 user.notice kernel: [ 2.213907] sd 1:0:0:0: [sdb] Attached SCSI disk
Jul 30 08:12:29 puppypc6720 user.info kernel: [ 35.178323] EXT3-fs (sdb2): using internal journal
Jul 30 08:12:29 puppypc6720 user.info kernel: [ 35.178328] EXT3-fs (sdb2): mounted filesystem with ordered data mod

"Jul 29 17:00:24 puppypc4609 user.warn kernel: sdb2"
Is this something to be concerned about?

[goontron]

Re: 2.1-TB limitation on hdd space for older computers

i would guess the warn is for the lack of proper accessibility and saying don't touch this if you have important data.

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

The data is definitely important. I guess I may have to upgrade to the newer kernel. I have that Puppy version installed on a laptop, but I'm not too thrilled with the bling, little stuff really.

[Per Hansson]

Re: 2.1-TB limitation on hdd space for older computers

Good, open the messages logfile in your favorite text editor and see if there is another message right after the "warn" point saying what it's about.

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

All the warn lines in the order they occur in the message:

Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: RSDP 000febf0 00024 (v02 DELL )
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: XSDT 000fcedc 0006C (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: FACP 000fd004 000F4 (v03 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: DSDT fff53074 036E3 (v01 DELL dt_ex 00001000 INTL 20050624)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: FACS dfe0ac00 00040
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: SSDT fff56878 000AC (v01 DELL st_ex 00001000 INTL 20050624)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: APIC 000fd0f8 00092 (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: BOOT 000fd18a 00028 (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: ASF! 000fd1b2 00092 (v32 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: MCFG 000fd244 0003E (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: HPET 000fd282 00038 (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: TCPA 000fd4de 00032 (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: SLIC 000fd2ba 00176 (v01 DELL B8K 00000015 ASL 00000061)
Jul 29 18:29:49 puppypc4609 user.warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 909740
Jul 29 18:29:49 puppypc4609 user.warn kernel: Console: colour VGA+ 80x25J
Jul 29 18:29:49 puppypc4609 user.warn kernel: Fast TSC calibration using PIT
Jul 29 18:29:49 puppypc4609 user.warn kernel: Detected 2660.123 MHz processor.
Jul 29 18:29:49 puppypc4609 user.warn kernel: Mount-cache hash table entries: 512
Jul 29 18:29:49 puppypc4609 user.warn kernel: bio: create slab <bio-0> at 0
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI Warning: Incorrect checksum in table [TCPA] - 00, should be 88 (20090903/tbutils-314)
Jul 29 18:29:49 puppypc4609 user.warn kernel: highmem bounce pool size: 64 pages
Jul 29 18:29:49 puppypc4609 user.warn kernel: intel_rng: Firmware space is locked read-only. If you can't or
Jul 29 18:29:49 puppypc4609 user.warn kernel: intel_rng: don't want to disable this in firmware setup, and if
Jul 29 18:29:49 puppypc4609 user.warn kernel: intel_rng: you are certain that your system has a functional
Jul 29 18:29:49 puppypc4609 user.warn kernel: intel_rng: RNG, try using the 'no_fwh_detect' option
Jul 29 18:29:49 puppypc4609 user.warn kernel: sdb2
Jul 29 18:29:49 puppypc4609 user.notice kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Jul 29 18:29:49 puppypc4609 user.warn kernel: sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Jul 29 18:29:49 puppypc4609 user.info kernel: Uniform CD-ROM driver Revision: 3.20
Jul 29 18:29:49 puppypc4609 user.debug kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
Jul 29 18:29:49 puppypc4609 user.warn kernel: sda1 sda2 sda3
Jul 29 18:29:49 puppypc4609 user.warn kernel: Zone PFN ranges:
Jul 29 18:29:49 puppypc4609 user.warn kernel: DMA 0x00000000 -> 0x00001000
Jul 29 18:29:49 puppypc4609 user.warn kernel: Normal 0x00001000 -> 0x000377fe
Jul 29 18:29:49 puppypc4609 user.warn kernel: HighMem 0x000377fe -> 0x000dfe0a
Jul 29 18:29:49 puppypc4609 user.warn kernel: Movable zone start PFN for each node
Jul 29 18:29:49 puppypc4609 user.warn kernel: early_node_map[2] active PFN ranges
Jul 29 18:29:49 puppypc4609 user.warn kernel: 0: 0x00000000 -> 0x0000009f
Jul 29 18:29:49 puppypc4609 user.warn kernel: 0: 0x00000100 -> 0x000dfe0a
Jul 29 18:29:49 puppypc4609 user.warn kernel: ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 1/0x1 ignored.
Jul 29 18:29:49 puppypc4609 user.warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 909740
Jul 29 18:29:49 puppypc4609 user.warn kernel: sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Jul 29 18:29:49 puppypc4609 user.warn kernel: VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
Jul 29 18:29:49 puppypc4609 user.warn kernel: <30>udev[116]: starting version 167
Jul 29 18:29:49 puppypc4609 user.warn kernel: mtrr: type mismatch for e0000000,8000000 old: write-back new: write-combining
Jul 29 18:29:56 puppypc4609 user.warn kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jul 29 18:31:34 puppypc4609 user.warn kernel: mtrr: type mismatch for e0000000,8000000 old: write-back new: write-combining

[binsonk]

Re: 2.1-TB limitation on hdd space for older computers

Just in case anybody is interested, when I changed the SATA Operations setting from ATA to AHCI, this action rendered my original OS as unbootable. Grub loading...Error 22. I have since installed the Puppy version with kernel 3.2.33, and it's working well. Probably a few kinks still to work out, but it will do for now.