From owner-freebsd-questions@freebsd.org Mon Dec 21 20:50:28 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23ECFA4E616 for ; Mon, 21 Dec 2015 20:50:28 +0000 (UTC) (envelope-from mcdonnjd@pcam.org) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0111.outbound.protection.outlook.com [157.56.110.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD41C1734 for ; Mon, 21 Dec 2015 20:50:27 +0000 (UTC) (envelope-from mcdonnjd@pcam.org) Received: from BLUPR07MB321.namprd07.prod.outlook.com (10.141.25.14) by BLUPR07MB321.namprd07.prod.outlook.com (10.141.25.14) with Microsoft SMTP Server (TLS) id 15.1.361.13; Mon, 21 Dec 2015 20:50:17 +0000 Received: from BLUPR07MB321.namprd07.prod.outlook.com ([169.254.13.26]) by BLUPR07MB321.namprd07.prod.outlook.com ([169.254.13.26]) with mapi id 15.01.0361.006; Mon, 21 Dec 2015 20:50:17 +0000 From: John McDonnell To: FreeBSD Questions Subject: RE: POS system trashing hard drives during install Thread-Topic: POS system trashing hard drives during install Thread-Index: AdE42/YAUl1Y0GLdSvaQohL1/K9PRAAeH/+AALMoILAAAb3EKQABTfAg Date: Mon, 21 Dec 2015 20:50:17 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=mcdonnjd@pcam.org; x-originating-ip: [68.234.51.1] x-microsoft-exchange-diagnostics: 1; BLUPR07MB321; 5:wGfoq5O0b4XQc2pwbtM7Y0mYkCdEATp8hpTZDuCUVp/c1peLUbCf0TMh7IjlTqun+6xKET0Lwp4UDST3gjoJRguO/7/nPxvwnBsEBGhvRR2aWHdwSUnKmbL9HkXrPE3OmRCy9Q/TrD/18kp7GLJ2nA==; 24:oLrWlom30eSOAc1Iax1Aq0LhqDaOD5sFhGw32VXx/kZrGS/D84RfDjnUa7ayW3q4dbQTdHqwqN8qIiUrjuUXObXxRcsfIJ8fd5hvjH7b11I=; 20:DxKDm72SC/SdCGlpVlzJ68IBxQbmcFUJISQ9VTjbkgvfj+NwZDcPM+vXrUHXJOyhkMxVrTMpU8IGNH8OcrHg6UUs09zZxMZOCiVThOoc+zD7Jdv7BWzumaPCsUB+L3ls/LpxzZspQHPbEWjpjEIyQXg3DRllWMVB6nvGhG2WVbI= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR07MB321; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(192713067249063); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(520078)(5005006)(8121501046)(3002001)(10201501046); SRVR:BLUPR07MB321; BCL:0; PCL:0; RULEID:; SRVR:BLUPR07MB321; x-forefront-prvs: 079756C6B9 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(10400500002)(19580395003)(99286002)(19580405001)(76576001)(5008740100001)(5003600100002)(450100001)(101416001)(1220700001)(11100500001)(40100003)(86362001)(1096002)(122556002)(81156007)(92566002)(33656002)(106356001)(105586002)(189998001)(97736004)(6116002)(2900100001)(107886002)(110136002)(586003)(3846002)(102836003)(66066001)(2950100001)(5004730100002)(5002640100001)(76176999)(54356999)(50986999)(93886004)(87936001)(74316001)(5001960100002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR07MB321; H:BLUPR07MB321.namprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; received-spf: None (protection.outlook.com: pcam.org does not designate permitted sender hosts) spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: pcam.org X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Dec 2015 20:50:17.3254 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 4d0a72ee-ba26-46d5-8bbe-6430f01b636a X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR07MB321 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2015 20:50:28 -0000 I had a thought and realized that the hard drives I had tried using on the = POS all were drives from Windows machines, and maybe one that was blank, an= d the POS had no trouble POSTing with those drives. It wasn't until after r= ebooting with FreeBSD installed on the drive that the machine will no longe= r POST. So, there couldn't be something specific to the drive in the system= itself as it has no trouble with other drives until FreeBSD is actually in= stalled. I took this to mean that there shouldn't be something specific on the drive= to prevent it from POSTing. For a test, I have a network bootable copy of = Xubuntu 12.0 sitting on my PXE server that I just installed to the POS syst= em. It made it through POST and booted from the drive with no problem. So, = I really don't think it is something to do with dpecial information stored = to the drive itself. About the only other thing I can think of trying in or= der to get FBSD working on the POS is doing an old "dangerously dedicated" = mode install and see if the machine likes that better. But I think I need t= o find an older install disk somewhere for that, or find instructions onlin= e somewhere on how to do it manually. I've never had an issue where I felt = the need to try that style of install. If nothing else, I should at least be able to get a version of Linux runnin= g on the machine, which will be an improvement over XP, but not as nice as = running FreeBSD. (Though if I can't get the touchscreen running, it'll be b= ack to XP. I'm betting it is fairly simple to get done, I was just surprise= d it didn't work out of the box since I believe it's an old serial connecte= d touchscreen. I'll look into it after I exhaust my options of getting Free= BSD installed.) --=20 John McDonnell Penn Cambria School District mcdonnjd@pcam.org