From owner-freebsd-questions@freebsd.org Wed May 6 17:00:23 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EAF9B2DA076 for ; Wed, 6 May 2020 17:00:23 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49HNBZ6BfRz3Q6Z for ; Wed, 6 May 2020 17:00:22 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.222.27.16]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPA (Nemesis) id 1MdNwm-1ix2eZ38Yy-00ZKrT; Wed, 06 May 2020 19:00:19 +0200 Date: Wed, 6 May 2020 19:00:19 +0200 From: Polytropon To: Christoph Kukulies Cc: freebsd-questions@freebsd.org Subject: Re: SSD woes - boot Message-Id: <20200506190019.480bda48.freebsd@edvax.de> In-Reply-To: <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org> References: <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:1k3p8BlyoYpMObzg1z2GFVWOEYUgVARC7VXUwKBIrDzHBseSsYL ++x+TQcIN4TwvdH809HkysDzc1PbfaC3CoQfYRhJh42tynQSoqeTh4KSuCzjiXd1XNoQmL2 I9W0b1dZJ4R3ma8EQjo1lpqqgm/Hh+QHIW0eyYEqSe5xNawHDFFZ9yR9QTmpRDpPCfcOtyQ vGJkYrtJuAURguMHnhfow== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:/i8nIwRUcN4=:L2SgoD3tt8MLCqlRTasyL0 lAN15lGAs5+qnComr9tYu5cqzHnSPXkx1IPg7530L86uA6V/VFaBb8aE8r6Xyrz2rumdqmqVt 6QuIBXBhYiL5evFTRQPtUNUsjpagdL6FyeQdss7SMu9+edZOgqkegC88WIwpcx5UmJ1T/k1ez 5chlpxgmiaT8+QImVobo4Pg3O3C1ox1QhaiWgsHgI3acSDqqnKz99RyRrMVr6yb3GTQB5Vrin L7fMfnBvALX2XlDUYc0i61XXvXpJRB4+kWvDPZhO0bJJmGKYu2T0wu7FerD5lQ6ZHkXqtsCv+ eLfZuYeuGQ5BPy/m5YBDN4YXrtsEK73KwjSNtGfdereUmPhLC2aTD0HZbNcKqbHB6+/qX3tHF ow+dkUKSmtijPcXt3DXbrIqqU/sOsMQYZfqTZpw8lCiW0ZcL5TqvbA6EQ5qiYQM5ygJponOTx IE18hWJQML5I3o/8jEXOr0xbmJKPP+O0RmaYA/thagR5ae41KnvjVBFX9RCg6jCXslNhuHnj/ +KlfD/0cL7iKZTef2MFuj57xpF6x+ylIrbgWEV06HFQ0qzQiPtdM6RCrxZlnOiLQbV2eX98lL BxakaWZZVFN1wvP1SUiTHtSEuFtQ5KjoUk/jaBiBmbXm3kaMLbsZc+fC0X+kzI9w6OH/VIqbM 9qh1kTLvUvN7R5o/IwdhZf0OZvTWq86stYX1XzmaFiS9AxWUlh2SB9c9vzO9+fdVRSskeT880 v4oo8wlYElaNVfPbCEZcDkmOz2RXNa7XVOo6x6LNakTpLO+3j5w3I8GeZNHpW9oUlmJnrnTAR U/OJul+GeQyxL5518fX5lY8PBVtg8ivaMwxF9GUoeh1eN8LBLtKvm21snsPTbX+FCXie0JT X-Rspamd-Queue-Id: 49HNBZ6BfRz3Q6Z X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.134) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [4.78 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.45)[ip: (1.46), ipnet: 212.227.0.0/16(-1.20), asn: 8560(2.03), country: DE(-0.02)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.93)[0.928,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.998,0]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[134.126.227.212.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[134.126.227.212.rep.mailspike.net : 127.0.0.19]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2020 17:00:24 -0000 On Wed, 6 May 2020 11:56:24 +0200, Christoph Kukulies wrote: > Since yesterday, when I ran smartcontrol against my drives - don’t > know whether it has to do with that but I’m mentioning it just FWIW - > my Kingston 240 GB SSD suddenly was no longer visible in the ASRock > MB’2 BIOS. (ASRock939A790GMH). > > Strange, isn’t it, that a power fail or unclean shutdown/dismount > can cause the drive being no longer visible to the BIOS. There can be several other reasons. The firmware in modern SSDs is rather complex. A possible "firmware hickup" could lead to what you've been experiencing. It's very hard to diagnose what actually happened, and why. > To test whether it was still alive, I took it out of the system, > put it into an ICY box and connected it to a FreeBSD (11) VM I > have running under Parallels on my MacbookPro. > > It got recognized on the USB bus and after I ran an fsck against > it and put it back into the BIOS, it was recognized again. Many years ago, I had a similar problem with a disk taken from a system: No other computer would recognize it. The BIOS would try to detect it... but no device shows up. I wasn't able to access the disk in any other computer, not even with the USB forensic adapter. So I resurrected the PC it was originally working in, BIOS detect - and the disk was there! So I booted from a live system CD, started a FTP server, and copied what I needed using local FTP (directly connected, no Internet involved). I never found out why the disk would only work in _that_ machine. This is the reason I kept the particular machine, just in case I have to read data from a "strange disk"... ;-) > So far so good. But now, due to some misordering in the hard > disk numbering scheme in the BIOS I can’t aim at the right > partition to boot. > With the old F1/F5 bootload of FreeBSD it always boots the wrong > partition . Boot the system via CD or USB, and add labels. Put the labels instead of the device names. In worst case, use bsdinstall or gpart to re-install the boot manager. > Is there a better bootloader available which offers me a larger > choice, that eventually finds all bootable partitions on all > disks in the system? You will probably be happy with current GRUB; even though it is primarily intended for the use with Linux, it works with many operating systems. It's a very convenient solution for systems that boot BSDs, Linusi, even "Windows". :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...