alware as the firmware+bootloader. E.g.
https://lwn.net/Articles/748586/
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Oh, is this really dm-cache, not lvmcache? That might be a source of
confusion, if there isn't lvm metadata present to hint at LVM for proper
assembly. Of course, lvmcache still uses device mapper, but with LVM
metadata.
Anyway is quite an interesting, a
samba_share_t which is not
how any system files should be labeled.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Another idea is Fedora 27 or 28 live media, and 'dnf install blivet-gui'
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
e same thing.
> After posting I realized that one might want to use a UDF filesystem
> on RW media, and I suppose for that purpose one would need to format
> it, though I've not done that on a CD or DVD, only on USB.
>
Yep. Formatting but no burning.
https://github.com/pali/udftools/blob/master/doc/HOWTO.udf
---
Chris Murphy
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Fedora install
media (any) on a USB stick. Newer kernel and progs.
Ok maybe even 10 out of 10.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
d GPU is unavailable. So I advise testing
before committing to legacy mode.
Also, rare, but not all UEFI systems come with a Compatiblity Support
Module (fake BIOS), in which case you're stuck.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
remove the signature found
in both primary and backup.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
und this. Is there a solution?
>
Yes, but it means giving bad advice. And that is to enable "legacy" OS
support to present a faux BIOS to the booting system instead of exposing
UEFI. It's bad advice because you have no good rea
ough the
process of informing the firmware this is a valid binary by using
mokutil - but I estimate maybe 1 in 50 people might do this).
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Thu, Feb 1, 2018 at 10:13 AM, wwp wrote:
> Hello Chris,
>
>
> On Thu, 01 Feb 2018 17:00:03 + Chris Murphy
> wrote:
>
>> You can to use efibootmgr for this. NVRAM boot entry is what changed, not
>> the contents of the EFI System partition.
>>
>>
You can to use efibootmgr for this. NVRAM boot entry is what changed, not
the contents of the EFI System partition.
efibootmgr -v
Will list all entries and Boot Order. You need to use --bootorder to make
sure the CentOS entry is first.
Chris Murphy
itigation until Intel gets its ducks into a row.
*eye roll*
> Linus Torvalds agrees:
> http://tcrn.ch/2n2mEcA
His comments aren't about microcode though. And it also looks like he
got IBRS and IBPB confused. The better post on this front is
https://lkml.org/lkml/2018/1/22/598
As far as I
the impression that upstream was deprecating BTRFS.
>
Upstream being Red Hat, yes. Upstream Btrfs development continues
unaffected, Red Hat was not a major contributor to Btrfs development the
last few years.
Chris Murphy
> mark
>
> _
when they misbehave, etc.
Anyway, Btrfs has been my primary filesystem for roots and data for years.
And I've experienced no unplanned data loss. But I still keep many backups
(up to seven copies, five are independent, the of which are Btrfs based).
Chris Murphy
_
t. Libreoffice by default saves autorecovery
information every 10 minutes, for example.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Message from syslogd@fcshome at Aug 12 10:12:24 ...
> kernel:[Hardware Error]: Error Status: Corrected error, no action required.
Cosmic ray corrupted data in RAM, and ECC detected and corrected it?
Whatever it was, working as intended.
--
Chris Murphy
__
seldom discussed seed
device / overlay feature, useful for live media that's substantially
simpler to implement and understand compared to dm - and it's also
much more reliable. The dm solution we currently have for lives will
eventually blow up without warning when it gets full and the overlay
is toast.
https://github.com/kdave/btrfs-wiki/wiki/Seed-device
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
um
mismatch even if the hardware is not reporting problems. For impending
drive failures, still your best bet is smartd even though the stats
are that it only predicts drive failures maybe 60% of the time.
>Chris Murphy wrote:
>> There's 1500 to 3000 line changes to Btrf
On Fri, Aug 11, 2017 at 11:17 AM, Mark Haney wrote:
> On Fri, Aug 11, 2017 at 1:00 PM, Chris Murphy
> wrote:
>
>> Changing the subject since this is rather Btrfs specific now.
>>
>>
>>
>> >>
>> >> Sounds like a hardware problem. Btrfs
On Fri, Aug 11, 2017 at 7:53 AM, Robert Nichols
wrote:
> On 08/10/2017 11:06 AM, Chris Murphy wrote:
>>
>> On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz
>> wrote:
>>
>>>
>>>
>>> On 08/09/2017 10:46 AM, Chris Murphy wrote:
>>>>
Changing the subject since this is rather Btrfs specific now.
On Fri, Aug 11, 2017 at 5:41 AM, hw wrote:
> Chris Murphy wrote:
>>
>> On Wed, Aug 9, 2017, 11:55 AM Mark Haney wrote:
>>
>>> To be honest, I'd not try a btrfs volume on a notebook SSD. I did that
On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz wrote:
>
>
> On 08/09/2017 10:46 AM, Chris Murphy wrote:
> > If it's a bad sector problem, you'd write to sector 17066160 and see if
> the
> > drive complies or spits back a write error. It looks like a bad
ain in Fedora kernels.
Anyway, blkdiscard can be used on an SSD, whole or partition to zero them
out. And at least recent ext4 and XFS mkfs will do a blkdisard, same as
mksfs.btrfs.
Chris Murphy
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_cam
re it's a bad sector.
What is DID_BAD_TARGET?
And what do you get for
smartctl -x
Chris Murphy
On Wed, Aug 9, 2017, 8:03 AM Robert Moskowitz wrote:
> I am building a new system using an Kingston 240GB SSD drive I pulled
> from my notebook (when I had to upgrade to a 500GB SSD drive).
he
scenes outside of samba, you can run into label problems since
inheritance doesn't apply to moving).
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
which puts most of the
drivers, including video drivers, into user space. And Microsoft also
rarely changes things in their kernel, so again drivers tend to not
break.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
having to deal with the base system? If so then how?
You'll need to search the smartmontools site for their doc on bad sectors.
There's a how to, to find what file is affected by the bad sector so you
can replace it. That's the only way to fix the problem.
This gets tricky going through LVM.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
ntirely as I expect it needs a much
newer kernel. I don't think it strictly requires USB-C, but in practice
that's the only form factor I've seen it appear in so far.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.
ut I'm also really prepared to lose any of the copies at any time.
Even if I were using XFS on LVM, I'd still keep this many copies.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
This is my smb.conf, it's extremely basic.
https://paste.fedoraproject.org/519466/34678791/
Note that max version is commented out. I've been using some version
of Samba 4 for a little over a year, and with macOS versions 10.9
through 10.12.
Ch
aware of; however I'm using samba-4.5.3
since I'm using Fedora 25 server. It may be that older versions need
to force a lower version of SMB depending on which Mac client you're
using.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
s bothered by but may have an NVRAM garbage
collection bug that they don't care about or don't know about (yet).
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Exactly what efibootmgr command are you using?
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
tom CentOS boot
params, and whenever CentOS gets a kernel update and updates its
grub.cfg, you'll see those changes without having to do anything.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
boot order, separated
by commas.
I have no idea what RC at the end of these lines means though.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Tue, Sep 6, 2016, 8:08 PM Pat Haley wrote:
>
> Trying the gluster client seems to fix the problem.
>
Hmm, suggests an NFS export issue then, rather than permissions issue?
Chris Murphy
___
CentOS mailing list
CentOS@centos.
(they're 30 to 50 MB each).
>
I think jump using /boot is a bad idea. I wonder if that's really
necessary? Anyway, long term solution from the anaconda list is increasing
/boot size to 1GiB.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Thu, Sep 1, 2016, 8:11 AM Pat Haley wrote:
>
> For the enforcing=0, is that referring to SELinux? If so, we are not
> running SELinux.
>
OK so neither that nor chcon nor context mount option apply. It's something
else.
>
> On 08/31/2016 11:38
try the gluster client instead of using NFS. See if
you get a different result that narrows down what's going on.
My vague recollection is for Samba, without the correct SELinux label, I
could neither read nor write.
Chris Murphy
___
CentOS mailing li
vname=0"
> No location is specified, the installer works it out. Given the error you
> posted, I think sda1 might not be where anaconda is putting the EFI
> partition.
That appears to be basically correct. It'll put it on sda1 but it
doesn't want you to tell it to put
using
software RAID. So we're sorta stuck with mdadm raid1, or you'd have to
create your own script that syncs a primary ESP to the secondary ESP
(primary being the one mounted at /boot/efi and the only one that'd
get updated bootloa
ot a UEFI mode boot, it's using
CSM-BIOS mode, and that would explain why the wrong bootloader is
being installed by the installer.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
y. The proper entry can
be found with the earlier grep efibootmgr command, and you can just
use that, while adding an additional \ for each \, so that it's \\.
NVRAM should point to shim.efi and it's shim.efi that loads the
prebaked grubx64.efi.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
ub2-efi that should fix the problem,
the following two options are just information gathering in case the
reboot still doesn't work.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
$ sudo grep grub2 /var/log/anaconda/program.log
This will get you the commands the installer used for installing the bootloader.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
.
And yet another thing is that it's possible the initramfs isn't using
resume= which is currently a problem on
Fedora. So you might need to add this to the grub.cfg on the kernel
command line, something like resume=/dev/VG/swap or wherever it is. If
it's a /dev/sdXY, i.e. on a regular
On Fri, Jun 3, 2016 at 12:24 AM, Ned Slider wrote:
>
>
> On 03/06/16 04:45, Chris Murphy wrote:
>>
>> On Tue, May 31, 2016, 7:59 PM Albert McCann
>> wrote:
>>
>>> In CentOS 7.2.1511 does the 3.10.0-327.18.2.el7.centos.plus.x86_64 (Plus)
>>&g
. And there is no open source code for this. Upstream
liblkid doesn't even recognize it. It's actually a big problem as it
renders OS X HFS unreadable outside of OS X.
Microsoft's equivalent is Storage Spaces. But as yet it's not used by
default. Likewise no support on Linux stil
ub.cfg command line for root= parameter and fstab.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Anaconda live installs use this:
rsync -pogAXtlHrDx --exclude /dev/ --exclude /proc/ --exclude /sys/
--exclude /run/ --exclude /boot/*rescue* --exclude /etc/machine-id
/run/install/source/ /mnt/sysimage
Chris Murphy
___
CentOS mailing list
CentOS
ession does appear to have
> fixed the corruption problem I was seeing. I'll watch for an updated
> systemd package.
Does journalctl --verify no longer complain of corruption? Or is it
possible there's corruption but journalctl and rsyslogd n
On Wed, Apr 27, 2016 at 7:05 AM, Chris Adams wrote:
> Once upon a time, Chris Murphy said:
>> On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams wrote:
>> > Once upon a time, Chris Murphy said:
>> >> On Tue, Apr 26, 2016, 2:09 PM Chris Adams wrote:
>> >> &g
On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams wrote:
> Once upon a time, Chris Murphy said:
>> On Tue, Apr 26, 2016, 2:09 PM Chris Adams wrote:
>> > I have several recently-installed CentOS 7 servers that keep having
>> > systemd-journald corruption
>>
>> D
ffects rsyslog. Usually journalctl just
skips over corrupt parts and systemd-journald will rotate logs when it
detects corruption to isolate corrupt files.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
to thinks like user interface improvements or bug fixes.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Fri, Apr 22, 2016 at 4:11 AM, Timothy Murphy wrote:
> Chris Murphy wrote:
>
>> What you should revert back to UEFI only, with Secure Boot enabled,
>> and reinstall CentOS, deleting the previous partition/mount points
>> including the BIOS Boot partition that
mple partition
1 starts at LBA 2048 which is 1MiB aligned, and now make all
partitions sized in MiB increments and they will all align
Depending on the age of the file system, it's not a bad idea to just
start over every once in a while.
--
Chris Murphy
an the progs supports and the progs are too far behind.
And yes, this happens on the XFS list and the Btrfs list too where
people are using old progs with new kernels and it can be a problem.
Sometimes new progs and old kernels are a problem too but that's less
common.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
d /home. Just a
guess.
It's not a bad idea to get gdisk on the system, and change the type
code for the linux partition to gdisk code 8300, which translates to
partition type GUID 0FC63DAF-8483-4772-8E79-3D69D8477DE4. Windows 10
will ignore this, where at least Window
fi
package doesn't support chainloading the Windows bootloader. This is
getting fixed in Fedora 24 but I have no idea how long it'll take to
get to CentOS 7. You could either disable Secure Boot (which I don't
recommend) or you switch between CentOS and Wi
ey're modified, and only modified by API via the daemon. Of course this
doesn't exist yet. But without it, we've regressed in functionality and
reliability.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Sat, Mar 5, 2016 at 9:27 PM, g wrote:
>
>
> On 03/05/16 20:22, Fred Smith wrote:
>> On Sat, Mar 05, 2016 at 12:48:17PM -0600, g wrote:
>>>
>>>
>>> On 03/05/16 09:04, Chris Murphy wrote:
>>>> You don't say how you created the media.
On Sat, Mar 5, 2016 at 11:48 AM, g wrote:
>
>
> On 03/05/16 09:04, Chris Murphy wrote:
>> You don't say how you created the media.
>>
> --
>
> true, i did not say how i created cd's.
>
> i used k3b as it is easier, less to remember, than using co
>
>
> You don't say how you created the media. Also netinstall used the network
as source, not from CD/DVD. So you should just leave the source selection
on default.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://li
Default boot volume on Fedora is 500M, with a kernel installonly_limit
of 3. So far this seems sufficient, even accounting for the "rescue
kernel" (which is really a nohostonly initramfs, which is quite a bit
larger than the standard hostonly initramfs used for numbered
kernels).
__
rom top so we can see what is consuming
most of the cpu or anything consuming less than it should because it's
waiting for something else that's slower. It might be useful to see
'perf top' if perf is installed, and if not install it, reproduce the
problem and let perf
On Mon, Feb 8, 2016 at 1:35 AM, Chris Murphy wrote:
> Everything else is prone to failure.
Specifically, but not limited to, unetbootin. Really, people need to
just purge unetbootin from memory and stop recommending it. I've never
had it work on any (U)EFI system. And more often tha
On Mon, Feb 8, 2016 at 11:18 PM, John R Pierce wrote:
> On 2/8/2016 9:54 PM, Chris Murphy wrote:
>>
>> Secure erase is really the only thing to use on SSDs. Writing a pile
>> of zeros just increases wear (minor negative) but also doesn't
>> actually set the cells t
On Mon, Feb 8, 2016 at 10:54 PM, Chris Murphy wrote:
> Secure erase is really the only thing to use on SSDs.
Oops. It's probably a fairly close approximation to just mkfs.btrfs -f
(or xfs) the entire block device for the SSD. If the kernel sees it as
non-rotational, it'll issue a
On Mon, Feb 8, 2016 at 3:18 PM, wrote:
> Chris Murphy wrote:
>> DBAN is obsolete. NIST 800-88 for some time now says to use secure erase
>> or enhanced security erase or crypto erase if supported.
>>
>> Other options do not erase data in remapped sectors.
>
&
DBAN is obsolete. NIST 800-88 for some time now says to use secure erase or
enhanced security erase or crypto erase if supported.
Other options do not erase data in remapped sectors.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https
hdparm supports ATA secure erase. This is SSD safe, unlike other options.
It's faster than writing zeros to both HDD and SSD.
Chris Murphy
On Mon, Feb 8, 2016, 3:06 PM wrote:
> Wes James wrote:
> > Is there a utility to zero unused blocks on a disk?
> >
> > Cen
se is prone to failure.
CentOS 6.4 is kinda old for new hardware. You're better off looking at
CentOS 7.1.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Thu, Jan 21, 2016 at 9:27 AM, Lamar Owen wrote:
> On 01/20/2016 01:43 PM, Chris Murphy wrote:
>>
>> On Wed, Jan 20, 2016, 7:17 AM Lamar Owen wrote:
>>
>>> The standard Unix way of refreshing the disk contents is with badblocks'
>>> non-destructive
r more recently the 'inst.rescue'
boot parameter, which tells anaconda to run the text rescue mode, and
all of that code is found in anaconda and python-blivet.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
e Boot prevents. What the alternative?
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
message that secure boot is enabled. Just
'dmesg | grep -i secure'
You can also use 'mokutil --sb-state'
Chris Murphy
> Thanks.
> ___
> CentOS mailing list
> CentOS@ce
On Wed, Jan 20, 2016, 7:17 AM Lamar Owen wrote:
> On 01/19/2016 06:46 PM, Chris Murphy wrote:
> > Hence, bad sectors accumulate. And the consequence of this often
> > doesn't get figured out until a user looks at kernel messages and sees
> > a bunch of hard link resets
ce. You'll see the read errors in dmesg, and md writing back
to the drive with the bad sector.
This problem affects all software raid, including btrfs raid1. The
ideal scenario is you'll use 'smartctl -l scterc,70,70 /dev/sdX' in
startup script, so the drive fai
le. Fstrim. Lvdisplay. Now compare the two lvdisplay results.
It should show the PEs used are less after fstrim.
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Tue, Jan 19, 2016, 3:30 PM wrote:
> Chris Murphy wrote:
> > On Mon, Jan 18, 2016, 4:39 AM Alessandro Baggi
> >
> > wrote:
> >> Il 18/01/2016 12:09, Chris Murphy ha scritto:
> >> > What is the result for each drive?
> >> >
> >&g
On Mon, Jan 18, 2016, 4:39 AM Alessandro Baggi
wrote:
> Il 18/01/2016 12:09, Chris Murphy ha scritto:
> > What is the result for each drive?
> >
> > smartctl -l scterc
> >
> >
> > Chris Murphy
> > ___
Also useful, complete dmesg posted somewhere (unless your MUA can be set to
not wrap lines)
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
What is the result for each drive?
smartctl -l scterc
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
f why os-probe, which was supposedly fixed
> almost five years ago, according to what I google, is back to complaining
> at 4k sectors.
I suggest added to /etc/default/grub
GRUB_DISABLE_OS_PROBER="true"
Since you only care about the current system being added to the boot
menu, searching for other OS's is irrelevant anyway.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
he fs block is not aligned to physical
sector size. I'm pretty sure parted and fdisk on CentOS 6 does
properly align, whereas they don't on CentOS 5. Proper alignment is
when the partition start LBA is divisible by 8. So a start LBA of 63
is not aligned, where 2048 is aligned and now commo
heavy writes
> per second , Should we migrate it to ext4 ? Any pros / cons for it ?
Piles of pros, and no meaningful cons. Just use ext4 with defaults.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
x86_64
Firewalld and iptables are mutually exclusive, at least on Fedora.
There might be some use case for combining static and dynamic rules
(?) but I'd expect you should disable one or the other.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
no
need to keep an old CentOS 6 /boot partition around anyway.
>I am wondering if it is possible to replace Grub2 with Grub
> legacy on Centos7 machine?
Yeah just yum erase grub2 and then force the installation of the
CentOS 6 grub package; then run grub-install.
--
Chris Murphy
__
fdisk,
a.k.a. gdisk. Set the partition type to EF02, which will set the
partition type GUID to that of BIOS Boot. And now GRUB should install
- it will automatically find that partition.
If you use parted, the flag to use is biosboot, which does the same
thing as EF02 in gdisk.
--
Chris Murph
not correctly
partition these drives such that they have proper 8 sector alignment.
If you haven't already, check the logic board firmware and the HBA
firmware for current updates.
--
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
On Thu, Aug 6, 2015 at 5:19 PM, Chris Murphy wrote:
> Now I get to look back at OP's first email and see
> if he did this exact same thing already, and whether we've come full
> circle.
Shit. He did.
All I can think of is that either the GRUB/BIOS device designations
are wr
On Thu, Aug 6, 2015 at 5:04 PM, Chris Murphy wrote:
> I might try nerfing the parted and grub stage 1 bootloaders on disk2,
> and see if the grub shell (which I should still get to from disk 1)
> will let me install grub directly on these two drives properly.
OK I did that and t
On Thu, Aug 6, 2015 at 3:19 PM, Chris Murphy wrote:
> On Thu, Aug 6, 2015 at 2:59 PM, Gordon Messmer
> wrote:
>> On 08/05/2015 10:23 AM, Chris Murphy wrote:
>>>
>>> Nothing about hd0 or hd1 gets baked into the bootloader code. It's an
>>> absolute re
On Thu, Aug 6, 2015 at 2:59 PM, Gordon Messmer wrote:
> On 08/05/2015 10:23 AM, Chris Murphy wrote:
>>
>> Nothing about hd0 or hd1 gets baked into the bootloader code. It's an
>> absolute reference to a physical drive at the moment in time the
>> command is made.
On Thu, Aug 6, 2015 at 2:57 PM, Bowie Bailey wrote:
> On 8/6/2015 4:39 PM, Chris Murphy wrote:
>>
>> On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey wrote:
>>>
>>> On 8/6/2015 4:21 PM, Chris Murphy wrote:
>>>>
>>>> On Thu, Aug 6, 2015 at
On Thu, Aug 6, 2015 at 2:39 PM, Leon Fauster wrote:
> Am 06.08.2015 um 22:21 schrieb Chris Murphy :
>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey wrote:
>>
>>> Doing a new install on the two 1TB drives is my current plan. If that
>>> works, I can connect the
drives, so the
partitioning will not be correct with a new installation. There's no
way to get the installer to do proper alignment. You can partition
correctly in advance, and then have the installer reuse those
partitions though.
--
Chris Murphy
___
On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey wrote:
> On 8/6/2015 4:21 PM, Chris Murphy wrote:
>>
>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey wrote:
>>
>>> Doing a new install on the two 1TB drives is my current plan. If that
>>> works, I can connec
1 - 100 of 232 matches
Mail list logo
