Re: upgrade
Quoting Mark Trickett (marktrick...@gmail.com): > A small query, nothing fixed, but when is Buster expected > to be released? Russell already gave you the serious answer, so I can now supply the frivolous one that doesn't help you. ;-> There are two traditional answers inside Debian Projet to the question 'When will the next stable release be?' 1. When it's ready. 2. Sooner if you help. Some would add, and in fact have been known to print on t-shirts: 3. Debian: Even hell freezes faster. ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
> Question - Should I choose Ubuntu 18.04 LTS or install 18.10 which will > need an upgrade at the end of July? > > Question: To set up my SSD for root and the other two drives as RAID 1 > mounted as /home, is it simply a matter of choosing btrfs? I haven't > built a Ubuntu Server before. Hi Andrew, I have been using Kubuntu (not Ubuntu) 18.04 LTS every day, almost since it was released, and haven't had any issues. Running it on bare metal and inside VirtualBox on the same server. Been updating periodically and that has gone smoothly as well. Previously used 12.04LTS and 14.04LTS for many years. I always go for the LTS versions - fewer issues for more stability, and everything I need is available. HTH Andrew ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
Hello Andrew, On 2/22/19, Andrew Greig via luv-main wrote: > Hi All, > > I have purchased a new 1Tb SSD and I have two unused SATA 2Tb drives, > and currently 8Gb RAM (max capacity 32Gb DDR3 1866) I will settle for > 24Gb soon. > > I have two optical drives, I will settle for one. > > MB = ASRock 890 GM Pro3 5 sata slots > > Currently the optical drive is in slot one > > So I will order my installation for the SSD in slot one and the optical > in slot 5 slots 2 and 3 are for the 2 x SATA 2Tb drives, slot 4 will be > for my old and now full Sata 1 Tb drive.l > > I will back-up my Thunderbird profile(s) to a USB stick for easy restore > when the new system is running. Copy/back up all your home directory structure to something big enough, preferably more than one copy. Consider a USB hard drive, USB memory sticks are good, but my experience is that they can fail unexpectedly. They make a reasonable short term storage, and for not critical material. Some last better. The other thing is to burn copies to optical media, carefully done, choosing the right disks, that can be an archival storage. > Question - Should I choose Ubuntu 18.04 LTS or install 18.10 which will > need an upgrade at the end of July? > > Question: To set up my SSD for root and the other two drives as RAID 1 > mounted as /home, is it simply a matter of choosing btrfs? I haven't > built a Ubuntu Server before. I have used Ubuntu, quite a while back. These days, Debian, with an interest in the derivatives that go away from systemd. The Debian installer has made big strides of progress, and very effective. Whichever way you go, before you restore any of your backed up data, look at how it went and be prepared to redo as a learning experience if it makes a mess. Minor problems are a different challenge, learning to rectify helps with other skills for when you are up and running. > Any "gotcha's"? >From your discussion, learn and understand what options the BIOS/UEFI offers, and the implications as to which drives it will look at for booting. Understand that a drive, any drive is a bit bucket. It needs the partitions as a logical data structure for dividing it up, although that relaxes with BTRFS. Then there are the higher level data structures in the partition that allocate particular addresses to particular files. You do not need a detail understanding such that you can look at the raw data and understand, but enough of the logical framing that the bits fit together in your mind. A basic Debian install is very flexible, it can do server and/or desktop, depending on what you add on top. I am certain Craig and Russell can comment on exactly the sane choices to make, with small detail variations of preference between them. The differences can look bigger than they are, do some research and read up about what the various filesystems offer. Craig has made some very pertinent remarks about the implications. > Andrew Greig > and thanks very much to Craig Sanders for his consistent support. I > think the "scorched earth" approach may fix all of my earlier confusion. > If I get stuck in the install I will write from my notebook. Regards, Mark Trickett ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
Hi All, I have purchased a new 1Tb SSD and I have two unused SATA 2Tb drives, and currently 8Gb RAM (max capacity 32Gb DDR3 1866) I will settle for 24Gb soon. I have two optical drives, I will settle for one. MB = ASRock 890 GM Pro3 5 sata slots Currently the optical drive is in slot one So I will order my installation for the SSD in slot one and the optical in slot 5 slots 2 and 3 are for the 2 x SATA 2Tb drives, slot 4 will be for my old and now full Sata 1 Tb drive.l I will back-up my Thunderbird profile(s) to a USB stick for easy restore when the new system is running. Question - Should I choose Ubuntu 18.04 LTS or install 18.10 which will need an upgrade at the end of July? Question: To set up my SSD for root and the other two drives as RAID 1 mounted as /home, is it simply a matter of choosing btrfs? I haven't built a Ubuntu Server before. Any "gotcha's"? Andrew Greig and thanks very much to Craig Sanders for his consistent support. I think the "scorched earth" approach may fix all of my earlier confusion. If I get stuck in the install I will write from my notebook. ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: upgrade
On Friday, 22 February 2019 4:55:07 PM AEDT Mark Trickett wrote: > Hello Russell, > > On 2/22/19, Russell Coker via luv-main wrote: > > A few days ago there was some downtime on the LUV server because rebooting > > another VM on the same hardware revealed a bug in the KVM scripts that > > shut > > off IPv4 access. > > > > Tonight I have just upgraded the LUV server to Debian/Testing (we are in > > the freeze process for the next release of Debian). In the process of > > upgrading the LUV server and other servers I run to Debian/Testing I've > > fixed many issues with my code and filed bug reports against some other > > packages. > My thanks also for your efforts in keeping the LUV server up and > running and secure. Also thanks for much else you do for the LUV > community. A small query, nothing fixed, but when is Buster expected > to be released? I have issues with scanning that I need to sort, but > there are a couple of different approaches, and the expected time > frame for Buster will influence whether I wait a little, or try > something else that will probably be more involved and susceptible to > mistakes. Not a firm date, but an expectation only. I don't know when it will be released. But the freeze process has started so maybe a few months. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: upgrade
Hello Russell, On 2/22/19, Russell Coker via luv-main wrote: > A few days ago there was some downtime on the LUV server because rebooting > another VM on the same hardware revealed a bug in the KVM scripts that shut > off IPv4 access. > > Tonight I have just upgraded the LUV server to Debian/Testing (we are in the > freeze process for the next release of Debian). In the process of upgrading > the LUV server and other servers I run to Debian/Testing I've fixed many > issues with my code and filed bug reports against some other packages. My thanks also for your efforts in keeping the LUV server up and running and secure. Also thanks for much else you do for the LUV community. A small query, nothing fixed, but when is Buster expected to be released? I have issues with scanning that I need to sort, but there are a couple of different approaches, and the expected time frame for Buster will influence whether I wait a little, or try something else that will probably be more involved and susceptible to mistakes. Not a firm date, but an expectation only. Regards, Mark Trickett ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
Hi Craig, I am unsure how much to clip as your response is comprehensive. But to start /dev/sda1 is my 1 TB drive and it is showing as having boot and lvm, do not know how root and swap were assigned to sdb1 The extra drives are 2 TB drives The problem with /dev/sdc1 not being part of the group is beyond me. I must have done something in gparted to get sdb1 recognised as part of the group, and not been able to do the same with /dev/sdc1 The fact that /dev/sdb1 is showing as active suggests it may have been formatted but I do not know how, On 22/2/19 12:35 pm, Craig Sanders via luv-main wrote: > On Thu, Feb 21, 2019 at 11:14:13PM +1100, Andrew Greig wrote: >> Looking at the disks in gparted I have: >> >> /dev/sda1 >> File system lvn2 pv >> Label >> UUID sI0LJX-JSme-W2Yt-rFiZ-bQcV-lwFN-tSetH5 >> Volume Group ubuntu-vg >> Members /dev/sda1 /dev/sdb1 >> Partition /dev/sda1 >> Name >> Flags boot/lvm >> >> /dev/sdb1 >> File system lvm2 pv >> Label >> UUID 9HV3H6-JIYu-IdaS-2CGr-lkZQ-9xcB-RVu9Ks >> Status Active >> Volume group /dev/sda1 /dev/sdb1 >> Logical Volumes root swap-1 >> Partition Path /dev/sdb1 >> Name >> Flags lvm >> >> /dev/sdc1 >> File system lvm2 pv >> Label >> UUID mqbYsB-xpm2-7c11-RLN5-q47a-A0bB-wcefad >> Status Not active(not a member of any volume group)Volume Group >> Members >> Logical Volumes >> PartitionPath /dev/sdc1 >> Name >> Flags lvm > > It looks like you've added one of the two new 3TB drives to the same volume > group as your root fs and swap partition. The other 3TB drive has been turned > into an unrelated volume group. Why? No idea > > Which drive is the old 1TB drive? and which are the new 3TB drives? /dev/sda1 is the old drive and /dev/sdb1 and /dev/sdc1 are the new drives > > My *guess* is that sdb1 is the old 1TB drive (because that's the only one > where the root and swap-1 LVs are mentioned). If that's the case, then I'll > also guess that the 1TB drive is plugged into the second SATA portso when > you plugged the new drives in, you plugged one of them into the first SATA > port. Try swapping the cables for those two drives around so that the 1TB > drive is in the first port. > > try running 'fdisk -l'. That will show each disk and all partitions on > it, including the brand, model, and size of the drive. knowing the logical > identifiers is only half the story, you also need to know which physical drive > corresponds to those identifiers. andrew@andrew-desktop:~$ sudo fdisk -l Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048 1953523711 1953521664 931.5G 8e Linux LVM Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xc3e8f29f Device Boot StartEndSectors Size Id Type /dev/sdb12048 3907028991 3907026944 1.8T 8e Linux LVM Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x7325946b Device Boot StartEndSectors Size Id Type /dev/sdc12048 3907028991 3907026944 1.8T 8e Linux LVM > > Once you have this information, i strongly recommend writing it down or > printing it so you always have it available when planning what to do. > > >> My current fstab is this >> andrew@andrew-desktop:~$ cat /etc/fstab >> # /etc/fstab: static file system information. >> # >> # Use 'blkid' to print the universally unique identifier for a >> # device; this may be used with UUID= as a more robust way to name devices >> # that works even if disks are added and removed. See fstab(5). >> # >> # >> /dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1 >> /dev/mapper/ubuntu--vg-swap_1 noneswapsw 0 0 >> andrew@andrew-desktop:~$ >> >> So /dev/sdb1 is part of a lvm group but /dev/sdc1 is not >> >> What command do I use to get these added to the fstab? I haven't consciously >> formatted either of the two new drives,is there a step I have missed? > > dunno, there isn't enough info to safely give any direct instructions. the > best I can give is generic advice that you'll have to adapt to your hardware > and circumstances. > > But the first thing you need to do is undo the existing mess - why did you add > one of the new drives to the existing volume group (VG)? and, since you added > the new drive, why didn't you just create a new logical volume (LV), format > it, and start using it? This is my problem, my understanding of lvm is minimal, it allows the partitions to grow or shrink to best use the disk space. That is it. lvm was set up as a default in the Ubuntu install > > You'll need to check that it isn't being actively used
RAM & LUV's HW Library (was Re: Boot problems after adding 2 new disks)
On Fri, Feb 22, 2019 at 10:22:38AM +1100, Russell Coker wrote: > In regard to the hardware advice. The LUV hardware library often has DDR3 > RAM for free, but 4G modules don't hang around long. If anyone is upgrading > from a DDR3 system to DDR4 please donate your old RAM as lots of people have > a use for this. When I get around to upgrading my systems to use DDR-4, I'll have a bunch of 8GB DDR-3 sticks to donate (with speeds ranging from DDR3-1333 to DDR3-1866). That won't be for some time, though. my current plan is to merge my mythtv box (FX-8150, 16GB RAM) and my file/dns/web/kvm/everything-server (phenom ii 1090T, 32GB RAM) into a single threadripper 2920x or 2950x machine with at least 64GB (not because i need that many CPU cores, but because I really need the PCI-e lanes...Ryzen 5 & 7 only have 20 lanes, which is not enough for GPU+DVB cards+SAS cards. Threadripper has 64 lanes). I can't afford to do that any time soon, though. Even if i could find somewhere that had the last-gen 8-core 1900x TR4 in stock (around $450, in theory, if available, vs the ~ $1000 for 2920x or ~ $1400 for 2950x), 64GB of new DDR-4 RAM would cost around $800 and a good X399 motherboard to suit would cost around $400, for a minimum build cost of $1650 or so. > Also we need more SATA disks, if anyone has disks of 300G+ that they don't > need then please donate them. Don't have any spare old drives, though. I use them until they die. craig -- craig sanders ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
On Thu, Feb 21, 2019 at 11:14:13PM +1100, Andrew Greig wrote: > Looking at the disks in gparted I have: > > /dev/sda1 > File system lvn2 pv > Label > UUID sI0LJX-JSme-W2Yt-rFiZ-bQcV-lwFN-tSetH5 > Volume Group ubuntu-vg > Members /dev/sda1 /dev/sdb1 > Partition /dev/sda1 > Name > Flags boot/lvm > > /dev/sdb1 > File system lvm2 pv > Label > UUID 9HV3H6-JIYu-IdaS-2CGr-lkZQ-9xcB-RVu9Ks > Status Active > Volume group /dev/sda1 /dev/sdb1 > Logical Volumes root swap-1 > Partition Path /dev/sdb1 > Name > Flags lvm > > /dev/sdc1 > File system lvm2 pv > Label > UUID mqbYsB-xpm2-7c11-RLN5-q47a-A0bB-wcefad > Status Not active(not a member of any volume group)Volume Group > Members > Logical Volumes > Partition Path /dev/sdc1 > Name > Flags lvm It looks like you've added one of the two new 3TB drives to the same volume group as your root fs and swap partition. The other 3TB drive has been turned into an unrelated volume group. Why? Which drive is the old 1TB drive? and which are the new 3TB drives? My *guess* is that sdb1 is the old 1TB drive (because that's the only one where the root and swap-1 LVs are mentioned). If that's the case, then I'll also guess that the 1TB drive is plugged into the second SATA portso when you plugged the new drives in, you plugged one of them into the first SATA port. Try swapping the cables for those two drives around so that the 1TB drive is in the first port. try running 'fdisk -l'. That will show each disk and all partitions on it, including the brand, model, and size of the drive. knowing the logical identifiers is only half the story, you also need to know which physical drive corresponds to those identifiers. Once you have this information, i strongly recommend writing it down or printing it so you always have it available when planning what to do. > My current fstab is this > andrew@andrew-desktop:~$ cat /etc/fstab > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are added and removed. See fstab(5). > # > # > /dev/mapper/ubuntu--vg-root / ext4errors=remount-ro 0 1 > /dev/mapper/ubuntu--vg-swap_1 noneswapsw 0 0 > andrew@andrew-desktop:~$ > > So /dev/sdb1 is part of a lvm group but /dev/sdc1 is not > > What command do I use to get these added to the fstab? I haven't consciously > formatted either of the two new drives,is there a step I have missed? dunno, there isn't enough info to safely give any direct instructions. the best I can give is generic advice that you'll have to adapt to your hardware and circumstances. But the first thing you need to do is undo the existing mess - why did you add one of the new drives to the existing volume group (VG)? and, since you added the new drive, why didn't you just create a new logical volume (LV), format it, and start using it? You'll need to check that it isn't being actively used in the VG, and then remove that drive from the VG before you do anything else. > I haven't got the dollars for a M/B upgrade so I will purchase some more > DDR3 Ram to get me to the limit of the motherboard, and I will purchase a > SDD as recommended. It wouldf be nice to get thses disks running so that > I can dump my data on to them and then add the SDD and do a fresh install > using btrfs, which, I believe will give me an effective RAID 1 config. The SSD or SSDs should be used for grub, the root fs /, the EFI partition (if any), /boot (if it's a separate partition and not just part of /), and swap space. the 3TB drives are for your home directory and data. You don't want to mix the SSD(s) and the hard drives into the same btrfs array. You can, however, have two btrfs arrays: one for the boot+OS SSD(s), the other for your bulk data (the 3TB drives). If all your data is going to be under your home directory then mount the latter as /home. If you're going to use it for other stuff too, mount it as /data or something and symlink into it (e.g. while booted in recovery mode, or logged in as root with nothing running as your non-root user: "mv /home /data/; ln -sf /data/home/ /") BTW, if you only get one SSD but plan to get another one later, btrfs allows you to convert it to RAID-1 at any time. So does ZFS, you can always add a mirror to a single drive. To do the same with mdadm, you have to plan ahead and create an mdadm degraded raid-1 array (i.e. with a missing drive) when you partition and format the drive. Probably the easiest way to do this is to remove ALL drives from the system, install the SSD(s) into the first (and second) SATA ports on the motherboard, and the two 3TB drives into the third and fourth SATA ports. Examine the motherboard carefully and check the m/b's manual when choosing which port to plug each drive into - the first port will probably be labelled SATA_0 or similar.
Re: Boot problems after adding 2 new disks
In regard to the hardware advice. The LUV hardware library often has DDR3 RAM for free, but 4G modules don't hang around long. If anyone is upgrading from a DDR3 system to DDR4 please donate your old RAM as lots of people have a use for this. Also we need more SATA disks, if anyone has disks of 300G+ that they don't need then please donate them. -- Sent from my Huawei Mate 9 with K-9 Mail. ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: making backports I have built recognised as providing correct package
Hello Craig, On 2/20/19, Craig Sanders via luv-main wrote: > On Wed, Feb 20, 2019 at 08:11:16PM +1100, Mark Trickett wrote: >> Aha, another piece of using apt-get. It is brilliant, but also a very >> steep >> learning curve. It would be very good to have a good cheat sheet in a >> printable form. > > $ apt-get --help > apt 1.8.0~rc3 (amd64) > Usage: apt-get [options] command >apt-get [options] install|remove pkg1 [pkg2 ...] >apt-get [options] source pkg1 [pkg2 ...] > > apt-get is a command line interface for retrieval of packages > and information about them from authenticated sources and > for installation, upgrade and removal of packages together > with their dependencies. > > Most used commands: > update - Retrieve new lists of packages > upgrade - Perform an upgrade > install - Install new packages (pkg is libc6 not libc6.deb) > reinstall - Reinstall packages (pkg is libc6 not libc6.deb) > remove - Remove packages > purge - Remove packages and config files > autoremove - Remove automatically all unused packages > dist-upgrade - Distribution upgrade, see apt-get(8) > dselect-upgrade - Follow dselect selections > build-dep - Configure build-dependencies for source packages > clean - Erase downloaded archive files > autoclean - Erase old downloaded archive files > check - Verify that there are no broken dependencies > source - Download source archives > download - Download the binary package into the current directory > changelog - Download and display the changelog for the given package That is a good summary, but what I (and probably others) would find very useful is a more expanded "cheat sheet" with good examples that we can extrapolate from. When I taught myself basic Postscript, I needed a cookbook of examples, the reference manual is good, but to generic in the descriptions of how to do. I still need to comprehend the standard prelude and postscripts portions that are usual. For that, I need more detail than the reference manual, and probably also some intro to Level 3, while what I have is Level 2. > See apt-get(8) for more information about the available commands. > Configuration options and syntax is detailed in apt.conf(5). > Information about how to configure sources can be found in sources.list(5). > Package and version choices can be expressed via apt_preferences(5). > Security details are available in apt-secure(8). > This APT has Super Cow Powers. Again, I am still looking for something a it more verbose, better explaining the detail, rather than just a summary. It is also why I would like a regional interest group relatively local, getting together and learning through group efforts and practice. >> I am now considering two installs on the computer, one stable, the other >> sid, and dual booting to get the scanning. As there is one normal user, I >> should be able to set up a shared home partition and the one user in each >> install sharing the one home directory structure. That way, I still have >> a >> usable system for most things, but can get at the stuff in sid at need. > > That seems overly complicated but it should work. the only thing to be wary > of > is to make sure that your user has the same UID and GID on both systems > (which > should be the default, as debian makes users with UIDs starting from 1000) I really do not want to not have a usable system now I need to use it to send in time cards. I am also (reluctantly) using Internet banking and having to depend on it. I tend to be working hours that preclude using storefront services to pay rates, electricity and Telstra, and more recently, ATO payments. Some I can pay on line with a Mastercard, some I need to use BPay from the bank site. > You probably don't even need a separate /home partition. You could just > mount > the stable system (e.g. as /stable) and symlink /home/mark on the sid system > to /stable/home/mark. Provided that sid does not have a regression or other issue that corrupts the disk, it has happened. For that reason, would have the sid install have a home on that hard drive, and not access the stable or testing. Then use the stable to transfer the files, or else use a USB stick. > Personally, I'd just upgrade to sid. I've never considered the stable > release > to be anything special, its main use to me is providing an installer to > build > new systems with (that then get immediately upgraded to sid). > > I'm biased, though: I've been using debian unstable since the 90s. BTW, the > only reason why "unstable" is called "unstable" is because a CD distributor > in 1994 or 1995 jumped the gun and released a "Debian 1.0" CD before it was > ready. The name was deliberately chosen to be scary enough to discourage > anyone from doing the same thing again...it doesn't mean that it's flaky or > crash-prone. My first copy of Linux was floppys that I never had the space to try, then Yggdrasil on CD with the drivers
Re: upgrade
On 22/2/19 12:33 am, Russell Coker via luv-main wrote: > Tonight I have just upgraded the LUV server to Debian/Testing (we are in the > freeze process for the next release of Debian). In the process of upgrading > the LUV server and other servers I run to Debian/Testing I've fixed many > issues with my code and filed bug reports against some other packages. Thanks Russell for all your hard work! Much appreciated. Cheers, Andrew ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
upgrade
A few days ago there was some downtime on the LUV server because rebooting another VM on the same hardware revealed a bug in the KVM scripts that shut off IPv4 access. Tonight I have just upgraded the LUV server to Debian/Testing (we are in the freeze process for the next release of Debian). In the process of upgrading the LUV server and other servers I run to Debian/Testing I've fixed many issues with my code and filed bug reports against some other packages. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
Looking at the disks in gparted I have: /dev/sda1 File system lvn2 pv Label UUID sI0LJX-JSme-W2Yt-rFiZ-bQcV-lwFN-tSetH5 Volume Group ubuntu-vg Members /dev/sda1 /dev/sdb1 Partition /dev/sda1 Name Flags boot/lvm /dev/sdb1 File system lvm2 pv Label UUID 9HV3H6-JIYu-IdaS-2CGr-lkZQ-9xcB-RVu9Ks Status Active Volume group /dev/sda1 /dev/sdb1 Logical Volumes root swap-1 Partition Path /dev/sdb1 Name Flags lvm /dev/sdc1 File system lvm2 pv Label UUID mqbYsB-xpm2-7c11-RLN5-q47a-A0bB-wcefad Status Not active(not a member of any volume group)Volume Group Members Logical Volumes Partition Path /dev/sdc1 Name Flags lvm My current fstab is this andrew@andrew-desktop:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/ubuntu--vg-root / ext4errors=remount-ro 0 1 /dev/mapper/ubuntu--vg-swap_1 noneswapsw 0 0 andrew@andrew-desktop:~$ So /dev/sdb1 is part of a lvm group but /dev/sdc1 is not What command do I use to get these added to the fstab? I haven't consciously formatted either of the two new drives,is there a step I have missed? I haven't got the dollars for a M/B upgrade so I will purchase some more DDR3 Ram to get me to the limit of the motherboard, and I will purchase a SDD as recommended. It wouldf be nice to get thses disks running so that I can dump my data on to them and then add the SDD and do a fresh install using btrfs, which, I believe will give me an effective RAID 1 config. Many thanks Andrew ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Boot problems after adding 2 new disks
Hi Craig, I tried to follow the UUID process and I think it worked OK. andrew@andrew-desktop:~$ blkid /dev/sdb1: UUID= andrew@andrew-desktop:~$ blkid /dev/sda1: UUID="sI0LJX-JSme-W2Yt-rFiZ-bQcV-lwFN-tSetH5" TYPE="LVM2_member" PARTUUID="92e664e1-01" /dev/mapper/ubuntu--vg-root: UUID="b0738928-9c7a-4127-9f79-99f61a77f515" TYPE="ext4" /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/loop2: TYPE="squashfs" /dev/loop3: TYPE="squashfs" /dev/loop4: TYPE="squashfs" /dev/loop5: TYPE="squashfs" /dev/loop6: TYPE="squashfs" /dev/loop7: TYPE="squashfs" /dev/loop8: TYPE="squashfs" /dev/loop9: TYPE="squashfs" /dev/loop10: TYPE="squashfs" /dev/loop11: TYPE="squashfs" /dev/loop12: TYPE="squashfs" /dev/loop13: TYPE="squashfs" /dev/loop14: TYPE="squashfs" /dev/loop15: TYPE="squashfs" /dev/loop16: TYPE="squashfs" /dev/loop17: TYPE="squashfs" /dev/loop18: TYPE="squashfs" /dev/loop19: TYPE="squashfs" /dev/loop20: TYPE="squashfs" /dev/loop21: TYPE="squashfs" /dev/loop22: TYPE="squashfs" /dev/loop23: TYPE="squashfs" /dev/loop24: TYPE="squashfs" /dev/loop25: TYPE="squashfs" /dev/loop26: TYPE="squashfs" /dev/loop27: TYPE="squashfs" /dev/loop28: TYPE="squashfs" /dev/loop29: TYPE="squashfs" /dev/loop30: TYPE="squashfs" /dev/loop31: TYPE="squashfs" /dev/loop32: TYPE="squashfs" /dev/loop33: TYPE="squashfs" /dev/loop34: TYPE="squashfs" /dev/loop35: TYPE="squashfs" /dev/mapper/ubuntu--vg-swap_1: UUID="2f34e0cb-eb8f-498a-ada4-7e786b7b9f2b" TYPE="swap" /dev/sdb1: UUID="9HV3H6-JIYu-IdaS-2CGr-lkZQ-9xcB-RVu9Ks" TYPE="LVM2_member" PARTUUID="c3e8f29f-01" /dev/sdc1: UUID="mqbYsB-xpm2-7c11-RLN5-q47a-A0bB-wcefad" TYPE="LVM2_member" PARTUUID="7325946b-01" /dev/sdd1: LABEL="EOS_DIGITAL" UUID="130D-103C" TYPE="vfat" andrew@andrew-desktop:~$ I haven't deliberately formatted the new disks yet, so can I choose btrfs for the two new 2Tb disks? And what will I use to format them, and having done that will the fstab get written to automatically? Thanks Andrew On 20/2/19 10:05 pm, Craig Sanders via luv-main wrote: # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/ubuntu--vg-root /ext4 errors=remount-ro0 1 /dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0 ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
