having 2 issues: 1. just install a new hd 160GB but du only shows aprox. 150GB anything i can do to display full size of drive using 9.3 lares:/home/boricua # df -h Filesystem Size Used Avail Use% Mounted on /dev/hda4 129G 2.1G 127G 2% / tmpfs 126M 0 126M 0% /dev/shm /dev/hda2 9.9G 38M 9.4G 1% /home /dev/hda3 11G 103M 10G 2% /var 2. the old drive i set as slave but is not seen by the system i would like to mount it to retried some data from it thanks
On Saturday 17 September 2005 13:24, boricua wrote:
having 2 issues:
1. just install a new hd 160GB but du only shows aprox. 150GB anything i can do to display full size of drive using 9.3
You are seeing the full size. The problem is the definition of "giga". By tradition in the computer industry, kilo hasn't meant 1000, it's meant 1024, mega has meant 1024*1024, and giga has meant 1024*1024*1024. However, hard drive makers have chosen to stick with the real meanings of these prefixes. So a hard drive kilobyte is really 1000 bytes, a megabyte is a million and a gigabyte is a thousand million. So when a hard drive maker says a drive is 160 gigabytes, in "computer" terms that is 160000000/(1024*1024*1024) or just under 150 "giga"bytes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-09-17 at 07:24 -0400, boricua wrote:
1. just install a new hd 160GB but du only shows aprox. 150GB anything i can do to display full size of drive using 9.3
For manufacturers, 160GB is 160*1000*1000*1000, ie, 160E9 bytes. For programmers, 160GB is 160*1024*1024*1024, ie, 171798691840 bytes. Or, said another way, those 160GB for the manufacturer are in fact only 149GB (actually, it may be gB or Gb or some other case combination I forgot). Anyway, there you have your 150 GB. Welcome to the real world! ;-)
lares:/home/boricua # df -h
Actually, to see the real size, use "fdisk /dev/hda" (df will not show not mounted partitions, nor size used by "format"). For example, mine says: Disk /dev/hda: 60.0 GB, 60022480896 bytes which is 55Gb in fact.
2. the old drive i set as slave but is not seen by the system i would like to mount it to retried some data from it
Try "fdisk -l" to see if it is really not seen. If it is not, see in /var/log/boot.msg why not. I assume the bios does see it. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDLBA3tTMYHG2NR9URAoJyAJ4yEwDcyg96cKYcIeVsd7G9t7id+gCfeHF0 7hr0a1xaUvUtRmzKcK7dToY= =YuW5 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
For manufacturers, 160GB is 160*1000*1000*1000, ie, 160E9 bytes.
"Gb"
For programmers, 160GB is 160*1024*1024*1024, ie, 171798691840 bytes.
"Gib" jdd -- pour m'écrire, aller sur: http://www.dodin.net http://valerie.dodin.net http://arvamip.free.fr
On Saturday 17 September 2005 16:25, jdd sur free wrote:
Carlos E. R. wrote:
For manufacturers, 160GB is 160*1000*1000*1000, ie, 160E9 bytes.
"Gb"
For programmers, 160GB is 160*1024*1024*1024, ie, 171798691840 bytes.
"Gib"
In both cases it should be B. Lower case b always stands for 'bit', byte is B
Anders Johansson wrote:
On Saturday 17 September 2005 16:25, jdd sur free wrote:
Carlos E. R. wrote:
For manufacturers, 160GB is 160*1000*1000*1000, ie, 160E9 bytes. "Gb"
For programmers, 160GB is 160*1024*1024*1024, ie, 171798691840 bytes. "Gib"
In both cases it should be B. Lower case b always stands for 'bit', byte is B
right -- pour m'écrire, aller sur: http://www.dodin.net http://valerie.dodin.net http://arvamip.free.fr
Actually, to see the real size, use "fdisk /dev/hda" (df will not show not mounted partitions, nor size used by "format"). For example, mine says:
Disk /dev/hda: 60.0 GB, 60022480896 bytes
which is 55Gb in fact.
thanks it does show Disk /dev/hda: 160.0 GB, 160041885696 bytes why swap says solaris? /dev/hda1 1 99 795186 82 Linux swap / Solaris
Try "fdisk -l" to see if it is really not seen. If it is not, see in /var/log/boot.msg why not. I assume the bios does see it.
only shows a lares:/home/boricua # fdisk -l Disk /dev/hda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 99 795186 82 Linux swap / Solaris /dev/hda2 100 1405 10490445 83 Linux /dev/hda3 1406 2711 10490445 83 Linux /dev/hda4 * 2712 19456lares:/home/boricua # grep hdb /var/log/boot.msg <6> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio 134504212+ 83 Linux i assume the bios is not seeing it?
boricua wrote:
why swap says solaris?
here?
/dev/hda1 1 99 795186 82 Linux swap / Solaris
probably solaris uses also the "82" number. You may know if you are on a solaris ort linux system :-)
/dev/hda2 100 1405 10490445 83 Linux /dev/hda3 1406 2711 10490445 83 Linux /dev/hda4 * 2712 19456lares:/home/boricua #
grep hdb /var/log/boot.msg <6> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio 134504212+ 83 Linux
i assume the bios is not seeing it?
do fdisk don't see it and the kernel do???? and fdisk /dev/hdb gives nothing (probably)? may be the dmesg lines after (and just before) the given line are relevants jdd --- pour m'écrire, aller sur: http://www.dodin.net http://valerie.dodin.net http://arvamip.free.fr
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-09-17 at 10:35 -0400, boricua wrote:
thanks it does show
Disk /dev/hda: 160.0 GB, 160041885696 bytes
ie, 149.05 GiB (thks jdd).
why swap says solaris?
/dev/hda1 1 99 795186 82 Linux swap / Solaris
Both types of partition use the same id number, they are not distinguishable looking at the partition type in the partition table alone. But the make swap program places a pattern it recognizes. I suppose those numbers are limited, or there is not a registrar, or who knows.
Try "fdisk -l" to see if it is really not seen. If it is not, see in /var/log/boot.msg why not. I assume the bios does see it.
only shows a lares:/home/boricua # fdisk -l
Disk /dev/hda: 160.0 GB, 160041885696 bytes
Ah.
grep hdb /var/log/boot.msg <6> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio 134504212+ 83 Linux
It is there, as type "pio", which is weird. Not really recognized, it seems.
i assume the bios is not seeing it?
I can't say, you have to go into the bios setup and check. Maybe not connected properly, jumpers not correct perhaps. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDLLMxtTMYHG2NR9URAhLbAJ4mCO315e1+X/SeMSROOTQiy8C2fQCePeEb vFM/lcaDZ0bVVFzpVlwxSWo= =pCR7 -----END PGP SIGNATURE-----
On 09/17/2005 05:24 AM, boricua wrote:
<snip>
2. the old drive i set as slave but is not seen by the system i would like to mount it to retried some data from it
thanks Does the system BIOS see the drive? In my experience, it does not matter what parameters you enter into the BIOS, Linux will query the drive itself to get the correct parameters.
My BIOS (an old Award) has a bug that causes it to lock up whenever it tries to register a drive size larger than 64K MB. I told the BIOS my 80 GB drive was about 30 GB, and Linux happily ignored that information -- the kernel sees and uses the full 80 GB. I do not know if Linux will see the drive even if it is not registered in the BIOS; my suspicion is it will not. However, I do know that Linux will be able to see and use the drive if it is registered in the BIOS.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-09-17 at 15:14 -0600, Darryl Gregorash wrote:
I do not know if Linux will see the drive even if it is not registered in the BIOS; my suspicion is it will not. However, I do know that Linux will be able to see and use the drive if it is registered in the BIOS.
Yes, it will. It wont boot from it, becasue lilo and grub use bios funtions calls at first, but the kernel will have no problem. In theory. That theory I have tested in one of my machines, but... who knows? That it works for me is no proof in the general case.
- -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDLL5etTMYHG2NR9URAiEpAJ9vNjY8DURx9pMjDP6QuiMUA3uqPQCgiyQg koc+fcQAuJ3rfAxGw5r9Iqg= =nFGL -----END PGP SIGNATURE-----
participants (5)
-
Anders Johansson -
boricua -
Carlos E. R. -
Darryl Gregorash -
jdd sur free