Re: Boot problems after adding 2 new disks
On 23/2/19 5:16 pm, Craig Sanders via luv-main wrote: On Sat, Feb 23, 2019 at 03:42:57PM +1100, Andrew Greig wrote: Now I need to plug in my old SATA drive and copy my data to one of my data drives. Small thing, when I was setting the partitions the system did not like /data on two separate drives so for the moment one is /data0 and the othe is /data1. If I load one of the drives with my data, as soon as RAID is setup will that data copy across to the other drive? And the next step is RAID Well, kind of. Not if you're talking about using mdadm for RAID-1. btrfs does its own raid. and volume management. There's no need for mdadm or lvm or anything else. If you've used btrfs for those drives then what you need to do is: 1. unmount both of them $sudo umount /dev/sdb1 && umount /dev/sdc1 ? 2. remount ONE of them (say, data0) as /data (and edit /etc/fstab so that it gets mounted as /data on every reboot. also delete the line in fstab that mounts data1). Here is my current fstab (please note, partition manager took me an hour and a half to negotiate and I was unable to install swap on my SSD so I put a swap partition on each of the two SATA drives so that they would be exactly the same size. ) andrew@andrew:~$ 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). # # # / was on /dev/sda2 during installation UUID=d8e97417-7029-4f22-87ed-df529ac19614 / btrfs defaults,subvol=@ 0 1 # /data0 was on /dev/sdb2 during installation UUID=0e8718c8-03bf-4f1a-915f-df03fe117dc0 /data0 btrfs defaults0 2 # /data1 was on /dev/sdc2 during installation UUID=5969127b-f5e0-40dc-98ba-ea7252c9ee41 /data1 btrfs defaults0 2 # /efi was on /dev/sda1 during installation UUID=b588608e-8cf7-43be-8a53-03dfde6f8f15 /efibtrfs defaults0 2 # /home was on /dev/sda2 during installation UUID=d8e97417-7029-4f22-87ed-df529ac19614 /home btrfs defaults,subvol=@home 0 2 # swap was on /dev/sdb1 during installation UUID=ad17f0bf-978c-4905-b421-2113b7eb5ba9 noneswapsw 0 0 # swap was on /dev/sdc1 during installation UUID=dba5db92-eee2-4633-ba6c-86b68bc2d957 noneswapsw 0 0 andrew@andrew:~$ 3. destroy the partition table on the data1 drive, and recreate it (again, one big partition for the entire disk[1]) So by deleting the partition we eliminate the FS (btrfs) and in the addition step the FS is rebuilt?? but specifically to control both disks? Can /dev/sdc2 can be deleted with gparted? 4. add that drive to the existing btrfs array on /data e.g. *IF* /data1 was sdc1, you'd do something like: sudo btrfs device add -f /dev/sdc1 /data sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 /data The earlier you do this (i.e. the less data is already on it), the faster this conversion to raid1 will be. Nearly instant if there's little or no data. Much longer if there's a lot of data that needs to be synced to the other drive. i.e. best to do it before copying the data from your old drive. I have about 4Gb only of data from this morning's photo shoot, I can move that back to /home/andrew easily enough. I just tried the Data drive to see how my CHOWN went. ( I cheat, I use mc) [1] technically, you don't need a partition, btrfs can use the entire disk. but IMO a partition table is useful for clearly identifying that a disk is in use and what it is being used for. It doesn't hurt in any way to have one and the space used by the partition table is trivial - at most, a sector for the partition table itself and another 2047 sectors[2] to ensure that the first sector of the first (and only) partition is aligned at a 4K sector boundary. i.e. 1MB out of your 2TB drive. [2] it's not uncommon on disks with GPT partition tables (instead of the old style ms-dos partition tables) to create a tiny partition in that area with type EF02 for grub, especially if they're ever going to be used to boot grub. craig -- craig sanders ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main ___ 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 Sat, Feb 23, 2019 at 04:26:25PM +1100, Andrew Greig wrote: > Referring to an earlier message about my data drives, do I need to CHOWN > those drives to andrew:andrew and then set the permissions to rwx? I think i said perms should be 664. that was wrong. the execute bit is needed to access a directory, so it should be 775 (rwxrwxr-x). 770 (rwxrwx---) would also work if you didn't want any other accounts on the system (other than root and andrew, and any accounts that you add to group andrew) to access it. the chown and chmod commands need to be run so that your user is able to read and write to the /data directory. Otherwise it'll be owned by root and only writable by root. NOTE: the chown and chmod need to be done while /data is mounted. This only needs to be done once, and will retain the owner & permissions metadata whenever it is remounted (e.g. on a reboot). if you do the chown & chmod while the /data fs isn't mounted, you'll only be changing the permissions of the empty mount-point directory, not of the filesystem. > I think you mentioned a symlink, would that be necessary if I have done the > CHOWN? the symlink was for convenience only. useful but not necessary. mostly so that you can just navigate to your home dir and double-click on the symlink in any GUI file chooser dialog. or from the command line "cd ~/data". > How do I set up the RAID1 on the Data0 and Data1 drives, please? see my previous message. you should have only a /data fs combining both the 2TB drives into a single btrfs raid1 array. > I have btrfs on all drives. I am amazed at the speed of an SSD. Yeah, they're bloody fast, aren't they? and NVME SSDs are even faster. > I will pick up the RAM and a cradle for the SSD as it does not fit anywhere > in my case. It is just sitting in there at present. There are no moving parts in an SSD, so it's safe to leave it just hanging loose indefinitely until you get a cradle for it. I wouldn't do that for a HDD except in some of data-recovery emergency, but it's not a problem for an SSD. 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 Sat, Feb 23, 2019 at 03:42:57PM +1100, Andrew Greig wrote: > Now I need to plug in my old SATA drive and copy my data to one of my data > drives. > > Small thing, when I was setting the partitions the system did not like /data > on two separate drives so for the moment one is /data0 and the othe is > /data1. If I load one of the drives with my data, as soon as RAID is setup > will that data copy across to the other drive? > > And the next step is RAID Well, kind of. Not if you're talking about using mdadm for RAID-1. btrfs does its own raid. and volume management. There's no need for mdadm or lvm or anything else. If you've used btrfs for those drives then what you need to do is: 1. unmount both of them 2. remount ONE of them (say, data0) as /data (and edit /etc/fstab so that it gets mounted as /data on every reboot. also delete the line in fstab that mounts data1). 3. destroy the partition table on the data1 drive, and recreate it (again, one big partition for the entire disk[1]) 4. add that drive to the existing btrfs array on /data e.g. *IF* /data1 was sdc1, you'd do something like: sudo btrfs device add -f /dev/sdc1 /data sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 /data The earlier you do this (i.e. the less data is already on it), the faster this conversion to raid1 will be. Nearly instant if there's little or no data. Much longer if there's a lot of data that needs to be synced to the other drive. i.e. best to do it before copying the data from your old drive. [1] technically, you don't need a partition, btrfs can use the entire disk. but IMO a partition table is useful for clearly identifying that a disk is in use and what it is being used for. It doesn't hurt in any way to have one and the space used by the partition table is trivial - at most, a sector for the partition table itself and another 2047 sectors[2] to ensure that the first sector of the first (and only) partition is aligned at a 4K sector boundary. i.e. 1MB out of your 2TB drive. [2] it's not uncommon on disks with GPT partition tables (instead of the old style ms-dos partition tables) to create a tiny partition in that area with type EF02 for grub, especially if they're ever going to be used to boot grub. 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
Hi Craig, Referring to an earlier message about my data drives, do I need to CHOWN those drives to andrew:andrew and then set the permissions to rwx? I think you mentioned a symlink, would that be necessary if I have done the CHOWN? How do I set up the RAID1 on the Data0 and Data1 drives, please? I have btrfs on all drives. I am amazed at the speed of an SSD. I will pick up the RAM and a cradle for the SSD as it does not fit anywhere in my case. It is just sitting in there at present. Thanks very much 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
Well, The good new is that I found a command on YouTube $ sudo tasksel ran that with several choices I am now sending this email from my GUI based desktop. copied the .Thunderbird hidden folder to my /home/andrew and after 4.6Gb had transferred I started Thunderbird and all of my email addresses are exactly as they were yesterday. Overjoyed, the learning curve was steep, but worth it. Thank you very much for your assistance. Now I need to plug in my old SATA drive and copy my data to one of my data drives. Small thing, when I was setting the partitions the system did not like /data on two separate drives so for the moment one is /data0 and the othe is /data1. If I load one of the drives with my data, as soon as RAID is setup will that data copy across to the other drive? And the next step is RAID Thanks again Andrew On 23/2/19 3:07 pm, Craig Sanders via luv-main wrote: On Sat, Feb 23, 2019 at 02:30:46PM +1100, Andrew Greig wrote: Unfortunately I am stuck in tty1, I thought that the GUI was on tty7, but I have forgotten how to get there. I thought it used to be CTRL ALT F7 If you have a display manager (xdm, gdm, kdm, lightdm, etc) installed, it will start up automatically and give you a graphical login. I have a system, now, but not usable by me at this stage. Did you install gnome or kde (or xfce or whatever desktop environment you prefer)? And all the GUI apps you intend to use? This may be because you chose to do a "server" install. I have no idea what Ubuntu actually means by that, but I'd guess it doesn't include X or other GUI stuff because they're generally not needed on "servers". But it's not a big problem, nothing to worry about. You can always apt-get install whatever you need, whether you chose a "desktop" or a "server" install. It's the same OS, just with different programs installed by default. craig -- craig sanders ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main ___ 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 Sat, Feb 23, 2019 at 02:30:46PM +1100, Andrew Greig wrote: > Unfortunately I am stuck in tty1, I thought that the GUI was on tty7, but I > have forgotten how to get there. I thought it used to be CTRL ALT F7 If you have a display manager (xdm, gdm, kdm, lightdm, etc) installed, it will start up automatically and give you a graphical login. > I have a system, now, but not usable by me at this stage. Did you install gnome or kde (or xfce or whatever desktop environment you prefer)? And all the GUI apps you intend to use? This may be because you chose to do a "server" install. I have no idea what Ubuntu actually means by that, but I'd guess it doesn't include X or other GUI stuff because they're generally not needed on "servers". But it's not a big problem, nothing to worry about. You can always apt-get install whatever you need, whether you chose a "desktop" or a "server" install. It's the same OS, just with different programs installed by default. 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
Hi Craig, Thanks for the advice, I cleared the partition tables and eventually worked out how to create new partitions and set the filesystems up. For me the partitioning tool in Ubuntu is a quantum leap behind the partition manager in Mandrake/Mandriva, it is a pity that that graphical partition manager was not used universally. I am grateful for the assistance because now I have a system running, but it is running from a tty. I ran the command startx to get a graphical screen up, the system suggested an install of xinit, and that is loading at present. Unfortunately I am stuck in tty1, I thought that the GUI was on tty7, but I have forgotten how to get there. I thought it used to be CTRL ALT F7 I have a system, now, but not usable by me at this stage. Cheers Andrew On 22/2/19 11:38 pm, Craig Sanders via luv-main wrote: On Fri, Feb 22, 2019 at 08:20:48PM +1100, Andrew Greig wrote: The 1Tb is an SSD for speed and I have another 2 x 2Tb drives for my data. After 3 years of photography and 13,000 images in raw, proofs and full size jpgs I have around 500Gb of data. This should meet my needs for 2 years at least at which time I will build a bigger machine. I am in the partitioner at present, manual chosen, I want root on the SSD LVM VG ubuntu-vg LV root - 2.0TB Linux device-mapper (linear) is what I am presented with so do I need to change root to home? LVM VG ubuntu-vg, LV swap_1 - 1.0 GB Linux device-mapper (linear) You don't need LVM if you're using btrfs, it doesn't give you anything that btrfs doesn't - it'll just make your disk management more complicated. Delete the partition tables from all 3 drives and create them manually. 1. sda (1 TB SSD) You'll need a partition for EFI (optional), a swap partition and a btrfs partition for the root fs. 4 or 8GB should be plenty for swap. the btrfs partition should be the remainder of the disk. If you're motherboard is old-style BIOS rather than UEFI, you don't need a FAT32 partition. sda (if BIOS): 4-8GB swap remainder for btrfs root fs sda (if UEFI or if you think you might move this disk to a UEFI machine in future): 512 MB EFI partition 4-8GB swap remainder for btrfs root fs Setting this up with btrfs now gives you the option of easily converting it to raid-1 later. just add an identical drive, partition it exactly the same, and tell btrfs to add the new partition to the existing one. btw, because the second drive has identical partitioning, you'll have another free partition the same size as your swap partition. you can use that for more swap, or format it and use it for /tmp or something. i'd just add it as more swap. Using btrfs for the root fs also allows you to use btrfs snapshots, and btrfs send for backups. 2. both sdb and sdc (2 x 2TB HDD): 1 big partition for btrfs /data. the installer should ask you where you want to mount this (/data) when you set it up. So how do I partition this so that root and boot are on the 1.0TB SSD You don't really need a separate partition for /boot, it works just fine as a subdirectory of /. Old-timers like me only do that out of habit from the days when it was useful to do so. and so that /home is the RAID array of two disks of 2TB each? I'd leave /home on the SSD - it's fast, and it's much bigger than you need for the OS. Having all your config files and browser cache and the data you're currently working with on the SSD will be a huge performance boost. Use /home on your SSD as fast working space (editing your images and videos on the SSD will be MUCH faster than editing them on the HDD), and move the completed work to subdirectories under /data - i.e. use /data for long-term bulk storage. So, as noted above, format the 2 x 2TB drives with btrfs and mount them as /data. for convenience, you can make /data owned by your user and symlink it into your home directory (which will let you access it as /data and/or as /home/yourusername/data): sudo chown yourusername:yourgroupname /data sudo chmod 664 /data ln -s /data/ /home/yourusername/ When you restore your data from your old 1TB HDD, remember to copy it to subdirectories under /data, rather than under /home. BTW, if there's any possibility that you might want to use some of the space on /data for something not directly related to or belonging to your user (e.g. if you have a second user on the machine, or want to use it for a squid cache or web site or to store VM images or whatever), then don't use the top level of /data directly. use a subdirectory with, e.g., the same name as your user name. i.e. instead of the commands above, try something like this instead: sudo mkdir /data/yourusername sudo chown yourusername:yourgroupname /data/yourusername sudo chmod 664 /data/yourusername ln -s /data/yourusername /home/yourusername/data I recommend doing this anyway even if you don't think you'll need it. It doesn't hurt to have it, and if you ever
Re: Boot problems after adding 2 new disks
On Fri, Feb 22, 2019 at 05:33:53PM +1100, Andrew Greig wrote: > 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. 24GB is nice. With that and the SSD, you should see an enormous boost in performance. No more twiddling your thumbs waiting for it to boot. of course, not long after you get used to the new speed, it'll start to seem unbearably slow :) > MB = ASRock 890 GM Pro3 5 sata slots I guess that means you have a Phenom II CPU or maybe one of the early FX series chips. Nice CPUs for their day, and still pretty good even today. most of my machines have these. If you have an FX CPU, they're happiest with DDR3-1866 RAM. DDR3 is slowly disappearing from the market so you have to get what's available - other speeds will work if you can't get 1866, but 1866 is optimal. BTW, if you're not sure exacly what CPU you have, run 'lscpu | grep Model.name'. You'll see output like this: # lscpu | grep Model.name Model name: AMD FX(tm)-8320 Eight-Core Processor or # lscpu | grep Model.name Model name: AMD Phenom(tm) II X6 1090T Processor > Question - Should I choose Ubuntu 18.04 LTS or install 18.10 which will need > an upgrade at the end of July? It really depends on whether you want to upgrade every 6 to 12 months (18.10), or every two years (LTS). Stuff like gimp and darkroom tend to be fairly fast moving, so upgrading them every six months or so is probably a good idea. I'm generally in favour of keeping systems upgraded regularly. IMO two years is two long between upgrades. Free Software development moves way too fast for that. craig PS: what kind of GPU do you have? if you do a lot of graphical work, it may be worthwhile comparing some of the current low-end to mid-range models to your current card. A modern $200-$300 GPU should be 2 to 3 times faster than, e.g., a high-end GPU from 5 years ago, and use significantly less power. but this is definitely something that needs significant research before buying anything. googling "old model name vs new model name" gets good results. e.g. "gtx-560 vs gtx-1050" leads to several review sites which say that the 1050 (~ $170) is roughly 87% (1.87x) faster than the 560, and uses only 75 Watts rather than 150 W. The next model up, a "1050 Ti" is a bit over twice as fast and costs about $200, also using 75W. and the GTX-1060 3GB model is about 3.65 times as fast as a GTX-560 and costs about $250 (using 120 W) BTW, "2-3 times as fast as what I currently have for $200-$300" is generally what I wait for when upgrading my GPU. Unless noise and power usage is a problem, it's not really worth the cost of upgrading for anything less. Sometimes, though, new features of newer cards (like better video decoding or newer opengl/vulkan) makes it worth upgrading earlier. There are various AMD Radeon models of simialar performance and price. Unless you're willing to use the proprietary nvidia driver, you're better off with an AMD GPU. their open source driver is much better than the open source nouveau driver for nvidia. I mostly use nvidia cards with the proprietary nvidia driver (the AMD fglrx driver always sucked and the open source drivers for both amd and nvidia used to suck. now they're kind of decent, especially the AMD driver, unless you do a lot of 3D gaming at 1440p or better with all the pretty turned up to Ultra) -- 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 Fri, Feb 22, 2019 at 08:20:48PM +1100, Andrew Greig wrote: > The 1Tb is an SSD for speed and I have another 2 x 2Tb drives for my data. > After 3 years of photography and 13,000 images in raw, proofs and full size > jpgs I have around 500Gb of data. This should meet my needs for 2 years at > least at which time I will build a bigger machine. > > I am in the partitioner at present, manual chosen, > > I want root on the SSD > > LVM VG ubuntu-vg LV root - 2.0TB Linux device-mapper (linear) is what I am > presented with > > so do I need to change root to home? > > LVM VG ubuntu-vg, LV swap_1 - 1.0 GB Linux device-mapper (linear) You don't need LVM if you're using btrfs, it doesn't give you anything that btrfs doesn't - it'll just make your disk management more complicated. Delete the partition tables from all 3 drives and create them manually. 1. sda (1 TB SSD) You'll need a partition for EFI (optional), a swap partition and a btrfs partition for the root fs. 4 or 8GB should be plenty for swap. the btrfs partition should be the remainder of the disk. If you're motherboard is old-style BIOS rather than UEFI, you don't need a FAT32 partition. sda (if BIOS): 4-8GB swap remainder for btrfs root fs sda (if UEFI or if you think you might move this disk to a UEFI machine in future): 512 MB EFI partition 4-8GB swap remainder for btrfs root fs Setting this up with btrfs now gives you the option of easily converting it to raid-1 later. just add an identical drive, partition it exactly the same, and tell btrfs to add the new partition to the existing one. btw, because the second drive has identical partitioning, you'll have another free partition the same size as your swap partition. you can use that for more swap, or format it and use it for /tmp or something. i'd just add it as more swap. Using btrfs for the root fs also allows you to use btrfs snapshots, and btrfs send for backups. 2. both sdb and sdc (2 x 2TB HDD): 1 big partition for btrfs /data. the installer should ask you where you want to mount this (/data) when you set it up. > So how do I partition this so that root and boot are on the 1.0TB SSD You don't really need a separate partition for /boot, it works just fine as a subdirectory of /. Old-timers like me only do that out of habit from the days when it was useful to do so. > and so that /home is the RAID array of two disks of 2TB each? I'd leave /home on the SSD - it's fast, and it's much bigger than you need for the OS. Having all your config files and browser cache and the data you're currently working with on the SSD will be a huge performance boost. Use /home on your SSD as fast working space (editing your images and videos on the SSD will be MUCH faster than editing them on the HDD), and move the completed work to subdirectories under /data - i.e. use /data for long-term bulk storage. So, as noted above, format the 2 x 2TB drives with btrfs and mount them as /data. for convenience, you can make /data owned by your user and symlink it into your home directory (which will let you access it as /data and/or as /home/yourusername/data): sudo chown yourusername:yourgroupname /data sudo chmod 664 /data ln -s /data/ /home/yourusername/ When you restore your data from your old 1TB HDD, remember to copy it to subdirectories under /data, rather than under /home. BTW, if there's any possibility that you might want to use some of the space on /data for something not directly related to or belonging to your user (e.g. if you have a second user on the machine, or want to use it for a squid cache or web site or to store VM images or whatever), then don't use the top level of /data directly. use a subdirectory with, e.g., the same name as your user name. i.e. instead of the commands above, try something like this instead: sudo mkdir /data/yourusername sudo chown yourusername:yourgroupname /data/yourusername sudo chmod 664 /data/yourusername ln -s /data/yourusername /home/yourusername/data I recommend doing this anyway even if you don't think you'll need it. It doesn't hurt to have it, and if you ever change your mind it's already set up to make it easy to use for other purposes. > I am in Guided Partitioning at present, next step is Configure Sotware RAID > > Then Configure the Logical Volume Manager > > Then configure encrypted volumes > > Then configure iSCSI volumes Ignore all that. You don't need LVM or iscsi, and I'm guessing you don't care about or want the complications of full disk encryption. Just set up 2 btrfs filesystems, one for the rootfs, the other for /home/ 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
Hi Russell, The 1Tb is an SSD for speed and I have another 2 x 2Tb drives for my data. After 3 years of photography and 13,000 images in raw, proofs and full size jpgs I have around 500Gb of data. This should meet my needs for 2 years at least at which time I will build a bigger machine. I am in the partitioner at present, manual chosen, I want root on the SSD LVM VG ubuntu-vg LV root - 2.0TB Linux device-mapper (linear) is what I am presented with so do I need to change root to home? LVM VG ubuntu-vg, LV swap_1 - 1.0 GB Linux device-mapper (linear) SCS13 (0,0,0) (sda) - 1.0 TB ATA Samsung SSD 860 SCS15 (0,0,0)(sdb) - 2.0 TB ATA ST2000DM006-2DM1 #1 primary 2.0 TB K lvm SCS16 (0,0,0) (sdc) - 2.0 TB ATA ST2000DM006-2DM1 #1 primary 2.0 TB K lvm So how do I partition this so that root and boot are on the 1.0TB SSD and so that /home is the RAID array of two disks of 2TB each? I am in Guided Partitioning at present, next step is Configure Sotware RAID Then Configure the Logical Volume Manager Then configure encrypted volumes Then configure iSCSI volumes I wouls appreciate some advice as I am in pretty deep, my eyes are above the water but I need to take a breath soon. Gratefully Andrew On 22/2/19 7:04 pm, Russell Coker wrote: If you have a RAID-1 of 2TB disks a single 1TB disk doesn't provide much value. I suggest using the port for a second SSD instead and have a RAID-1 on SSD for root and /home and 2*2TB RAID-1 for everything else. If a 2TB RAID-1 isn't enough for your big files then consider getting a couple of 6TB disks, they are cheap nowadays. ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: upgrade
Hello rick, On 2/22/19, Rick Moen via luv-main wrote: > 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. 1 I knew, but I am glad for some idea of the time frame. 2 I would like to, but probably documentation, but I am still on the steep part of the learning curve, along with my paid work leaving me somewhat flat as an understatement. > Some would add, and in fact have been known to print on t-shirts: > > 3. Debian: Even hell freezes faster. Depends on what you believe about hell. Some would argue that we are already there but do not recognize. For me, doing the same thing day after day for eternity does not look quite so much to look forward to. I take the attitude that when I choose to stop learning, I will be choosing to put myself in my grave. The trouble is that it takes more to learn whatever I want and whatever the motivation, and I definitely still want to learn. 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
If you have a RAID-1 of 2TB disks a single 1TB disk doesn't provide much value. I suggest using the port for a second SSD instead and have a RAID-1 on SSD for root and /home and 2*2TB RAID-1 for everything else. If a 2TB RAID-1 isn't enough for your big files then consider getting a couple of 6TB disks, they are cheap nowadays. -- 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
