[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-sparc
Subject:    Re: larger than 128GB drives in U5/10's?
From:       "Jay Hart" <jhart () nacs ! net>
Date:       2005-09-21 14:25:29
Message-ID: 20050921142529.M37315 () nacs ! net
[Download RAW message or body]

JIm,

Don't know if this will help. I sometimes set up partitions on new disks for my OBSD 
boxes by creating the partitions using Linux's fdisk utility.  If the partitions look 
good after I create them, then I move the disk to the OBSD box and format them for use.

I've had better success doing this, then trying to get the partitions working under OBSD.

Hope this helps,

Jay

--
N2NET (http://www.n2net.net)


---------- Original Message -----------
From: jjhartley@att.net
To: sparc@openbsd.org
Sent: Tue, 20 Sep 2005 21:51:57 +0000
Subject: larger than 128GB drives in U5/10's?

> I replaced the original 9GB IDE Seagate Medalist in a Sun Ultra 5 with a newer 
> Seagate Barracude 160GB drive even though I know that the IDE controller Sun 
> used back circa 1999 was unable to address more than ~128GB. disklabel ran fine 
> asking for the number of sectors which I copied from what I found on Seagate's 
> site. I've been running OpenBSD 3.7 for weeks now with no problem, until I 
> looked at the output of df which shows more than 128GB being on the disk. 
> Running disklabel to see the geometry parameters showed warnings that the end of 
> the last partition were not  accessible. I suspect I am not not seeing problems 
> now because I'm still using legitimately addressable space, but as I fill up the 
> disk, I will run into trouble at some point.
> 
> I don't mind losing ~40GB of space on this drive given the relatively cheap 
> price of 160GB drives. In fact, I expect to do so. I simply would like to use a 
> newer drive for practicality reasons. What do I need to do make this work? I can 
> initialize the disk through disklabel again limiting the number of addressed 
> sectors manually to 128GB given that I know the number of bytes/sector, but are 
> there other gotchas of which I am unaware?
> 
> Thanks for any knowledge/candor/experience that can be passed on.
> 
> Jim
------- End of Original Message -------

[prev in list] [next in list] [prev in thread] [next in thread]