Re: Anyone else having trouble with Samsung 160G drives?
Chad Leigh -- Shire.Net LLC wrote: On May 10, 2004, at 11:23 AM, Bill Moran wrote: This is the weirdest problem I'm seen in a while. Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed to install them in an existing FreeBSD 4.9 system for additional storage space. As soon as the drives are installed, kernel won't boot. It freezes up right before the "ad0: ..." messages appear and won't respond to anything except the reset button. Tried primary slave, secondary slave ... threw in a Highpoint ATA card and tried every possible configuration ... no dice. This was on a relatively new AOpen mobo with a 2G processor (don't have the model # handy, but I'll get it if it's important) When you moved the drives, did you move the cables? Can the problem be diagnosed by switching out the cables? Didn't keep _real_ close track of it, but we had 4 different cables that were moving around, and I believe we tried a few different combinations of them. Additionally, we've tried the drive in 3 different computers in our lab, and each one has successfully booted so far. (2 older machines and a fairly recent 2G ASUS board) I'm tending to lean toward BIOS weirdness. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else having trouble with Samsung 160G drives?
Simon Barner wrote: Bill Moran wrote: Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed to install them in an existing FreeBSD 4.9 system for additional storage space. [ drives don't work in various systems except for one ] I once had a similar problem with a 120 GB Maxtor drive. My solution was not to specify the drive in the BIOS, and to pull all of its configuration. Using a smaller (10 GB) drive as a boot device, FreeBSD (4.9 and 5.2.1) magically detects the drive. Wow ... I haven't seem much of this kind of problem until now, I must have been very lucky! This sounds like a good suggestion, except it was the first thing we tried. The orignal plan was to add the two drives to an existing FreeBSD system to add storage space to it. So the first configuration we tried was to install the drives as slaves on an already-working FreeBSD 4.9 system. As soon as we tried to boot with the new drive plugged-in, the system froze up (as described in detail in the email). Thanks for the input. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else having trouble with Samsung 160G drives?
On May 10, 2004, at 11:23 AM, Bill Moran wrote: This is the weirdest problem I'm seen in a while. Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed to install them in an existing FreeBSD 4.9 system for additional storage space. As soon as the drives are installed, kernel won't boot. It freezes up right before the "ad0: ..." messages appear and won't respond to anything except the reset button. Tried primary slave, secondary slave ... threw in a Highpoint ATA card and tried every possible configuration ... no dice. This was on a relatively new AOpen mobo with a 2G processor (don't have the model # handy, but I'll get it if it's important) When you moved the drives, did you move the cables? Can the problem be diagnosed by switching out the cables? Chad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else having trouble with Samsung 160G drives?
Bill Moran wrote: > Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed > to install them in an existing FreeBSD 4.9 system for additional > storage space. [ drives don't work in various systems except for one ] I once had a similar problem with a 120 GB Maxtor drive. My solution was not to specify the drive in the BIOS, and to pull all of its configuration. Using a smaller (10 GB) drive as a boot device, FreeBSD (4.9 and 5.2.1) magically detects the drive. Simon signature.asc Description: Digital signature
RE: Anyone else having trouble with Samsung 160G drives?
Sounds like bio's problems. Check mfg web site of motherboard in question for bio's update. What kind of drives does client have on box now (mfg & size)? Are existing drives used as straight IDE drives? Try Freebsd formatting them on your box before putting them back into clients box. I have noticed that newer motherboards (IE: 1GB speed cpu's and faster) have an different version of bois which FBSD has problems using. 5.x versions have been trying to fix this with no good results to date. Some people have reported that adding device puc to kernel, forces use of different method to read bios and things work using it. Check out 3rd party bio's vendor www.unicore.com for plug in replacement bio chip. Use ms/windows fdisk to break 160 gb into 2 partitions before putting then in clients box. You have to play around trying different things, there is no simple answer. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bill Moran Sent: Monday, May 10, 2004 1:24 PM To: [EMAIL PROTECTED] Subject: Anyone else having trouble with Samsung 160G drives? This is the weirdest problem I'm seen in a while. Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed to install them in an existing FreeBSD 4.9 system for additional storage space. As soon as the drives are installed, kernel won't boot. It freezes up right before the "ad0: ..." messages appear and won't respond to anything except the reset button. Tried primary slave, secondary slave ... threw in a Highpoint ATA card and tried every possible configuration ... no dice. This was on a relatively new AOpen mobo with a 2G processor (don't have the model # handy, but I'll get it if it's important) Moved the drives into an older 466mhz system ... same effect ... boot locks up at the probe message just before it would normally detect ad0. In this new system, we even tried removing the existing drives altogether and starting from scratch on these drives ... the boot from the CD hangs just like everything else. So ... I brought one back to the office to put in a test machine so I could gather lots of good data, file a PR and get the problem fixed. Threw it into an old lab machine (266 mhz SOYO board) and the sucker WORKS PERFECT! (so much for gathering data for a bug report) So ... I'm at a complete loss as to what I should do ... and a bigger loss on what I should recommend to the client. Does anyone have any experience with Samsung hard drives? Are they buggy in some way? I've got the feeling that I'm going insane ... seriously, these things work everywhere except where I need them to work (as an aside ... the client tried them in a Windows desktop machine and they worked fine there as well) Does anyone have any suggestions? Thoughts? Anything? -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else having trouble with Samsung 160G drives?
On Monday 10 May 2004 10:46 am, Bill Moran wrote: > Kent Stewart wrote: > > On Monday 10 May 2004 10:23 am, Bill Moran wrote: > >>This is the weirdest problem I'm seen in a while. > >> > >>Client bought a pair of 160G Samsung SP1604N ATA drives. I'm > >>supposed to install them in an existing FreeBSD 4.9 system for > >>additional storage space. > >> > >>As soon as the drives are installed, kernel won't boot. It freezes > >>up right before the "ad0: ..." messages appear and won't respond to > >>anything except the reset button. Tried primary slave, secondary > >>slave ... threw in a Highpoint ATA card and tried every possible > >>configuration ... no dice. This was on a relatively new AOpen mobo > >>with a 2G processor (don't have the model # handy, but I'll get it > >> if it's important) > >> > >>Moved the drives into an older 466mhz system ... same effect ... > >> boot locks up at the probe message just before it would normally > >> detect ad0. In this new system, we even tried removing the > >> existing drives altogether and starting from scratch on these > >> drives ... the boot from the CD hangs just like everything else. > >> > >>So ... I brought one back to the office to put in a test machine so > >> I could gather lots of good data, file a PR and get the problem > >> fixed. Threw it into an old lab machine (266 mhz SOYO board) and > >> the sucker WORKS PERFECT! (so much for gathering data for a bug > >> report) > >> > >>So ... I'm at a complete loss as to what I should do ... and a > >> bigger loss on what I should recommend to the client. > > > > I don't think it is the drive unless size is considered. There are > > bios problems when the size goes above 120GB or so. You may be > > bumping into this problem.If that is the case, a bios upgrade may > > let you use the HD. > > That's pretty odd, as the only mobo that the drive works with is has > a bios that's completely unable to understand the drive (the bios > screen says it's 8G). Both of the other machines we tried in > detected the drive size correctly in the bios. > > Are you saying that an older bios that incorrectly detects the drive > is more likely to work than a newer one that _does_ detect it > correctly? Scratch that ... _I'm_ the one that's saying it, since > that's what I'm seeing. No, I was thinking just the opposite. The 160's aren't supposed to work in all of the older bioses. IIRC, you need a larger version of LBA to map the drive. The 8GB is a sign of even older bios problems. The only time I had the hang problem with booting was when I made the drive dangerously dedicated. There are bioses that simply hang at discovery time with a DD drive mounted. I have a 160 Maxtor running in my test machine. There were messages about it not working on all systems but it installed without a problem on 4-stable. It is also very fast for an IDE. I can do a buildworld with an AMD 2400+ in 18 minutes using it for my /usr/obj. -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else having trouble with Samsung 160G drives?
Kent Stewart wrote: On Monday 10 May 2004 10:23 am, Bill Moran wrote: This is the weirdest problem I'm seen in a while. Client bought a pair of 160G Samsung SP1604N ATA drives. I'm supposed to install them in an existing FreeBSD 4.9 system for additional storage space. As soon as the drives are installed, kernel won't boot. It freezes up right before the "ad0: ..." messages appear and won't respond to anything except the reset button. Tried primary slave, secondary slave ... threw in a Highpoint ATA card and tried every possible configuration ... no dice. This was on a relatively new AOpen mobo with a 2G processor (don't have the model # handy, but I'll get it if it's important) Moved the drives into an older 466mhz system ... same effect ... boot locks up at the probe message just before it would normally detect ad0. In this new system, we even tried removing the existing drives altogether and starting from scratch on these drives ... the boot from the CD hangs just like everything else. So ... I brought one back to the office to put in a test machine so I could gather lots of good data, file a PR and get the problem fixed. Threw it into an old lab machine (266 mhz SOYO board) and the sucker WORKS PERFECT! (so much for gathering data for a bug report) So ... I'm at a complete loss as to what I should do ... and a bigger loss on what I should recommend to the client. I don't think it is the drive unless size is considered. There are bios problems when the size goes above 120GB or so. You may be bumping into this problem.If that is the case, a bios upgrade may let you use the HD. That's pretty odd, as the only mobo that the drive works with is has a bios that's completely unable to understand the drive (the bios screen says it's 8G). Both of the other machines we tried in detected the drive size correctly in the bios. Are you saying that an older bios that incorrectly detects the drive is more likely to work than a newer one that _does_ detect it correctly? Scratch that ... _I'm_ the one that's saying it, since that's what I'm seeing. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else having trouble with Samsung 160G drives?
On Monday 10 May 2004 10:23 am, Bill Moran wrote: > This is the weirdest problem I'm seen in a while. > > Client bought a pair of 160G Samsung SP1604N ATA drives. I'm > supposed to install them in an existing FreeBSD 4.9 system for > additional storage space. > > As soon as the drives are installed, kernel won't boot. It freezes > up right before the "ad0: ..." messages appear and won't respond to > anything except the reset button. Tried primary slave, secondary > slave ... threw in a Highpoint ATA card and tried every possible > configuration ... no dice. This was on a relatively new AOpen mobo > with a 2G processor (don't have the model # handy, but I'll get it if > it's important) > > Moved the drives into an older 466mhz system ... same effect ... boot > locks up at the probe message just before it would normally detect > ad0. In this new system, we even tried removing the existing drives > altogether and starting from scratch on these drives ... the boot > from the CD hangs just like everything else. > > So ... I brought one back to the office to put in a test machine so I > could gather lots of good data, file a PR and get the problem fixed. > Threw it into an old lab machine (266 mhz SOYO board) and the sucker > WORKS PERFECT! (so much for gathering data for a bug report) > > So ... I'm at a complete loss as to what I should do ... and a bigger > loss on what I should recommend to the client. I don't think it is the drive unless size is considered. There are bios problems when the size goes above 120GB or so. You may be bumping into this problem.If that is the case, a bios upgrade may let you use the HD. Kent > > Does anyone have any experience with Samsung hard drives? Are they > buggy in some way? I've got the feeling that I'm going insane ... > seriously, these things work everywhere except where I need them to > work (as an aside ... the client tried them in a Windows desktop > machine and they worked fine there as well) > > Does anyone have any suggestions? Thoughts? Anything? -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
