Title: Completely stuck configuring a new disk in a mono slab
Post by: dsmous on November 26, 2011, 05:00:35 AM
Post by: dsmous on November 26, 2011, 05:00:35 AM
Here's where I'm at...
It's an IBM DDRS-34560 - a 4.5 gig drive...
Where on earth am I going wrong?
I'm assuming it uses the name in the first line of disktab, and compares it to the name of the drive as is in the messages, correct?
scsimodes output...
And the verbose version, for the interested...
And the section from Disktab
This is from the boot messsages...
When i format it, the max I get is 261MB, as seen here:
Any thoughts?? I love this system, but the existing drive is getting VERY loud, and somewhat unreliable :-/[/code]
It's an IBM DDRS-34560 - a 4.5 gig drive...
Where on earth am I going wrong?
I'm assuming it uses the name in the first line of disktab, and compares it to the name of the drive as is in the messages, correct?
scsimodes output...
Code Select
next:7# /usr/etc/scsimodes /dev/rsd1a
SCSI information for /dev/rsd1a
Drive type: IBM DDRS-34560W
512 bytes per sector
218 sectors per track
5 tracks per cylinder
8387 cylinder per volume (including spare cylinders)
0 spare sectors per cylinder
0 alternate tracks per volume
8924999 usable sectors on volume
And the verbose version, for the interested...
Code Select
next:9# /usr/etc/scsimodes -v /dev/rsd1a
plh_len = 35
plh_medium = 0
plh_wp = 0
plh_blkdesclen = 8
bd_density = 0
bd_nblk = 8925000
bd_blklen = 512
dfp_savable = 0
dfp_pagecode = 3
dfp_pagelen = 22
dfp_trkszone = 5241
dfp_altsecszone = 0
dfp_alttrkszone = 0
dfp_alttrksvol = 0
dfp_sectors = 218
dfp_bytessector = 512
dfp_interleave = 1
dfp_trkskew = 11
dfp_cylskew = 20
dfp_ssec = 0
dfp_hsec = 1
dfp_rmb = 0
dfp_surf = 0
plh_len = 35
plh_medium = 0
plh_wp = 0
plh_blkdesclen = 8
bd_density = 0
bd_nblk = 8925000
bd_blklen = 512
rdp_savable = 0
rdp_pagecode = 4
rdp_pagelen = 22
rdp_maxcyl = 8387
rdp_maxheads = 5
rdp_wpstart = 0
rdp_rwcstart = 0
rdp_steprate = 0
rdp_landcyl = 0
last logical block=8924999
block length=512
And the section from Disktab
Code Select
DDRS|DDRS-34560W|IBM DDRS-34560W:\
:ty=fixed_rw_scsi:nc#8387:nt#5:ns#218:ss#512:rm#7200:\
:fp#320:bp#0:ng#0:gs#0:ga#0:ao#0:\
:os=sdmach:z0#64:z1#192:hn=next:rw=b:\
:pa#0:sa#8388608:ba#8192:fa#1024:ca#16:da#4096s:ra#1:oa=time:\
:ia:ta=4.3BSD:
This is from the boot messsages...
Code Select
Aug 17 17:12:09 next mach: SEAGATE ST15150W Rev 0017 as sd0 at sc0 target 0 lun 0
Aug 17 17:12:09 next mach: Disk Label: Disk
Aug 17 17:12:09 next mach: Disk Capacity 4095MB, Device Block 512 bytes
Aug 17 17:12:09 next mach: IBM DDRS-34560W Rev S92A as sd1 at sc0 target 1 lun 0
Aug 17 17:04:32 next mach: Generic SCSI Device as sg0 at sc0 target 7 lun 7
Aug 17 17:04:32 next mach: Generic SCSI Device as sg1 at sc0 target 7 lun 7
Aug 17 17:04:32 next mach: Generic SCSI Device as sg2 at sc0 target 7 lun 7
Aug 17 17:04:32 next mach: Generic SCSI Device as sg3 at sc0 target 7 lun 7
When i format it, the max I get is 261MB, as seen here:
Code Select
Aug 18 00:17:55 next mach: IBM DDRS-34560W Rev S92A as sd1 at sc0 target 3 lun 0
Aug 18 00:17:55 next mach: Disk Label: NewDisk
Aug 18 00:17:55 next mach: Disk Capacity 261MB, Device Block 512 bytesAny thoughts?? I love this system, but the existing drive is getting VERY loud, and somewhat unreliable :-/[/code]
Title: Re: Completely stuck configuring a new disk in a mono slab
Post by: cubist on November 26, 2011, 03:07:37 PM
Post by: cubist on November 26, 2011, 03:07:37 PM
Quote from: "dsmous"
Any thoughts?? I love this system, but the existing drive is getting VERY loud, and somewhat unreliable :-/
Stick to < 2GB partitions on 3.3. And that's probably good advice for 4.X but some swear 4GB is reliable.
Title: Re: Completely stuck configuring a new disk in a mono slab
Post by: t-rexky on November 27, 2011, 08:45:04 AM
Post by: t-rexky on November 27, 2011, 08:45:04 AM
I am by no means a disktab expert, but I spent an excessive amount of time earlier in the year playing with a box of random SCSI drives that I was trying to fit into my slab.
Looking at your post, the 261MB has nothing to do with the size of the partition that you created on your drive - that message reports the size of the SCSI device based on the block count. What I learned in my experimenting is that things go really funny in NS and OS once you go beyond the magical 4096MB number.
The 261MB is simply the size of your drive above the 4096 number: your drive reports 8924999 sectors, which is 8924999/2/1024=4357.9=4096MB+261.9MB. I bet that once you try to mount the partition you will get access to full 4GB. However, beware that there are a few things that break on 4GB partitions even on OS4.2. One of them is the dump utility, which will prevent you from backing up your 4GB partition using the dump/restore method. Interestingly restore works just fine, which makes things confusing. On NS3.3 4GB just plain does not work as cubist has indicated.
I eventually standardized on 2GB partitions on NS3.3 and 2GB boot partition plus 4GB data partitions on OS4.2. This allows the use of gnutar to back up data partitions and the dump/restore method for the boot partition.
Looking at your specific disktab I have two quick comments:
1. In all my disktabs I followed the format of others with respect the drive naming convention:
2. You have a term :rw=b: in your entry that refers to partition b that you are not creating. All my disktabs contain a term :ro=a: instead.
In summary, I am sure that your 4GB partition is there and it is just fine. Can you try to mount it and confirm?
Looking at your post, the 261MB has nothing to do with the size of the partition that you created on your drive - that message reports the size of the SCSI device based on the block count. What I learned in my experimenting is that things go really funny in NS and OS once you go beyond the magical 4096MB number.
The 261MB is simply the size of your drive above the 4096 number: your drive reports 8924999 sectors, which is 8924999/2/1024=4357.9=4096MB+261.9MB. I bet that once you try to mount the partition you will get access to full 4GB. However, beware that there are a few things that break on 4GB partitions even on OS4.2. One of them is the dump utility, which will prevent you from backing up your 4GB partition using the dump/restore method. Interestingly restore works just fine, which makes things confusing. On NS3.3 4GB just plain does not work as cubist has indicated.
I eventually standardized on 2GB partitions on NS3.3 and 2GB boot partition plus 4GB data partitions on OS4.2. This allows the use of gnutar to back up data partitions and the dump/restore method for the boot partition.
Looking at your specific disktab I have two quick comments:
1. In all my disktabs I followed the format of others with respect the drive naming convention:
Code Select
IBM DDRS-34560W|IBM DDRS-34560W-512:\2. You have a term :rw=b: in your entry that refers to partition b that you are not creating. All my disktabs contain a term :ro=a: instead.
In summary, I am sure that your 4GB partition is there and it is just fine. Can you try to mount it and confirm?
Quote from: "dsmous"Here's where I'm at...
It's an IBM DDRS-34560 - a 4.5 gig drive...
[...]
Where on earth am I going wrong?
When i format it, the max I get is 261MB, as seen here:Code SelectAug 18 00:17:55 next mach: IBM DDRS-34560W Rev S92A as sd1 at sc0 target 3 lun 0
Aug 18 00:17:55 next mach: Disk Label: NewDisk
Aug 18 00:17:55 next mach: Disk Capacity 261MB, Device Block 512 bytes
Any thoughts?? I love this system, but the existing drive is getting VERY loud, and somewhat unreliable :-/[/code]
Title: Completely stuck configuring a new disk in a mono slab
Post by: dsmous on November 27, 2011, 10:53:24 PM
Post by: dsmous on November 27, 2011, 10:53:24 PM
So far, so good!
You were exactly right with the sectors issue, I just for whatever reason missed the fact that I had to do some math there, and sdform doesn't appear to use disktab, which were the numbers confusing me!
So, here's the progress!
You were exactly right with the sectors issue, I just for whatever reason missed the fact that I had to do some math there, and sdform doesn't appear to use disktab, which were the numbers confusing me!
So, here's the progress!
Title: Completely stuck configuring a new disk in a mono slab
Post by: t-rexky on November 28, 2011, 12:22:24 PM
Post by: t-rexky on November 28, 2011, 12:22:24 PM
Excellent! I'm really glad that it's all working for you...
Quote from: "dsmous"So far, so good!
You were exactly right with the sectors issue, I just for whatever reason missed the fact that I had to do some math there, and sdform doesn't appear to use disktab, which were the numbers confusing me!
So, here's the progress!