Oshunluver, and anyone else with experience in ...

[GreyGeek]

Well, the bracket mounting for an HD in the second bay came today and I installed it and another 2.5" WD 750GB HD.
On booting up it was recognised as sdb. It now has Btrfs on sdb1 with no partitions.

Now I have to decide what to do with it.
Simply add it to my sda1 and make a Btrfs pool of sda1+sdb1 acting as a single storage pool?
Or, mount it to /backup only when I need to create a ro snapshot or do an incremental send & receive, freeing up space used by backup snapshots on sda1?

[FONT=monospace][COLOR=#000000][B]mount /dev/sda1 /mnt[/B][/COLOR]
vdir /mnt/
total 0
drwxr-xr-x 1 root root 256 Apr  8 16:53 @
drwxr-xr-x 1 root root  10 Apr  8 16:54 @home
drwxr-xr-x 1 root root 152 Apr  8 19:37 snapshots

[B]vdir /mnt/snapshots/[/B]
total 0
drwxr-xr-x 1 root root 276 Mar 29 11:16 @_bkup-2017-03-29
drwxr-xr-x 1 root root 256 Apr  8 16:53 @_bkup-2017-04-08
drwxr-xr-x 1 root root  30 Mar 24 14:46 @home_bkup-2017-03-29
drwxr-xr-x 1 root root  10 Apr  8 16:54 @home_bkup-2017-04-08
[B]
btrfs fi df /[/B]
Data, single: total=91.01GiB, used=90.49GiB
System, DUP: total=8.00MiB, used=16.00KiB
[/FONT]

As you can see, I am using only about 90GB on sda1.

And essentially nothing on sdb1.

btrfs fi df /backup

Data, single: total=8.00MiB, used=256.00KiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=1.00GiB, used=112.00KiB
GlobalReserve, single: total=16.00MiB, used=0.00B

Or, a third option is to move all ro backup snapshots to sdb1 and also use part of it to store other files, keeping it unmounted until needed.

The last option is the one I think I'll take, unless anyone has other suggestions.

[GreyGeek]

Update- The bracket didn't come with screws and I didn't have ant of the M2*2 or M2*3 screws, so I borrowed some from the DVD caddy and used rubber bands and a cardboard wedge to hold the HD in.
Works great, but I looking around for screws


Sent from my iPhone using Tapatalk

[oshunluvr]

You can fix anything with WD-40, duct tape, and zip-ties...LOL

[GreyGeek]

Drats!
I forgot about the duct tape!
What was I thinking?

[jlittle]

You can fix anything with WD-40, duct tape, and zip-ties...LOL

I dunno... I'd add number 8 fencing wire for high temperature applications, say hot exhausts, or fireplaces. Also, chaining more than about a dozen zip ties is tedious, and duct tape rope can be too springy.

John Little

[GreyGeek]

[emoji3]


Sent from my iPhone using Tapatalk

[GreyGeek]

Well, my ORINCO HD caddy lay in my desk drawer since the experience recorded above. Today, while looking in my giant chest of tools and electronic parts for some sort of wrench to fix the toilet handle I noticed a box that contained a bundle of bubble wrap. I unwrapped the bubble wrap and my eyes beheld a WD 750GB 2.5" HD, which was the old /dev/sda1 I replaced because of bad sectors. I had entirely forgotten about it. I decided to use it in the caddy.

Having changed the switch setting in that hidden switch the ORINCO support staff told me about, I put the HD into the caddy and tightened the screws. It slid easily into the bay and the bezel snapped firmly into place.

When I fired up the Acer and ran KPartition the HD in the caddy was recognized immediately, so changing the switch made the difference. Something interesting happened, which illustrates why UUID's are preferred when referencing hard drives. A month or so ago, when I plugged a new WD 750Gb HD into the 2nd SATA bay of my Acer, a bay which I did not know existed until I tried to use the ORINCO the first time, that HD partition was immediately recognized as /dev/sdb1. I decided to set up sda1 and sdb1 as RAID1, which is working perfectly. However, when I fired up KPartition I noticed that the drive in the CDROM caddy was identified as /dev/sdb1. What WAS /dev/sdb1 and part of my RAID1 setup is now identified as /dev/sdc. It is still part of the RAID1 setup which is still working beautifully.

Here is /etc/fstab

[FONT=monospace][COLOR=#000000]# <file system> <mount point>   <type>  <options>       <dump>  <pass>[/COLOR]
# / was on /dev/sda1 during installation
UUID=12980ae8-4117-4cc5-bbb8-8065e82af93d /               btrfs   defaults,subvol=@ 0       1
# /home was on /dev/sda1 during installation
UUID=12980ae8-4117-4cc5-bbb8-8065e82af93d /home           btrfs   defaults,subvol=@home 0       2
[/FONT]

Here is the output of blkid

blkid
/dev/sdb1: UUID="17f4fe91-5cbc-46f6-9577-10aa173ac5f6" UUID_SUB="4d5f96d5-c6c6-4183-814b-88118160b615" TYPE="btrfs" PARTUUID="5fa5762c-9d66-4fdf-ba8f-5c699763e636"
/dev/sda1: UUID="12980ae8-4117-4cc5-bbb8-8065e82af93d" UUID_SUB="568ad4a4-522e-4947-af9b-db9ca468d091" TYPE="btrfs" PARTUUID="99e4dabd-01"
/dev/sdc: UUID="12980ae8-4117-4cc5-bbb8-8065e82af93d" UUID_SUB="4342c984-fa3c-4665-b6aa-0b5199b5927b" TYPE="btrfs"

Clearly the RAID1 is undisturbed and is composed of /dev/sda1 and /dev/sdc. What is now /dev/sdb1 is not mounted.

sudo btrfs fi df /
Data, RAID1: total=95.00GiB, used=94.31GiB
System, RAID1: total=32.00MiB, used=16.00KiB
Metadata, RAID1: total=2.00GiB, used=978.83MiB
GlobalReserve, single: total=162.61MiB, used=0.00B

sudo btrfs fi show /
Label: none uuid: 12980ae8-4117-4cc5-bbb8-8065e82af93d
Total devices 2 FS bytes used 95.26GiB
devid 1 size 691.19GiB used 97.03GiB path /dev/sda1
devid 2 size 698.64GiB used 97.03GiB path /dev/sdc

And, here is the output from fdisk

sudo fdisk -l

Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 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: 0x99e4dabd

DeviceBootStart End Sectors SizeIdType
/dev/sda1 * 2048 1449523199 1449521152 691.2G 83 Linux


Disk /dev/sdb: 698.7 GiB, 750156374016 bytes, 1465149168 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: gpt
Disk identifier: CC604866-1B1D-4B67-B099-576FDE2A69CE

DeviceStart End Sectors SizeType
/dev/sdb1 2048 1465143295 1465141248 698.6G Linux filesystem


Disk /dev/sdc: 698.7 GiB, 750156374016 bytes, 1465149168 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

And the btrfs usage

[B]sudo btrfs fi usage /[/B]
Overall:
    Device size:                   1.36TiB
    Device allocated:            194.06GiB
    Device unallocated:            1.17TiB
    Device missing:                  0.00B
    Used:                        190.52GiB
    Free (estimated):            598.58GiB      (min: 598.58GiB)
    Data ratio:                       2.00
    Metadata ratio:                   2.00
    Global reserve:              162.62MiB      (used: 0.00B)


Data,RAID1: Size:95.00GiB, Used:94.30GiB
   /dev/sda1      95.00GiB
   /dev/sdc       95.00GiB


Metadata,RAID1: Size:2.00GiB, Used:978.88MiB
   /dev/sda1       2.00GiB
   /dev/sdc        2.00GiB


System,RAID1: Size:32.00MiB, Used:16.00KiB
   /dev/sda1      32.00MiB
   /dev/sdc       32.00MiB


Unallocated:
   /dev/sda1     594.15GiB
   /dev/sdc      601.61GiB

While using KPartition I also discovered that it now as a right mouse click option offering "Smart Status".
It showed that the newest HD, which I purchased about a month ago and put into the 2nd SATA bay, had been powered on for 647 hours (about 28 days) and power cycled 59 times, or about twice per day. Strangely, based on the power on hours, after converting my btrfs file system from a single to RAID1 it is now /dev/sda1, not /dev/sdb1

[GreyGeek]

I checked my Ksystemlog this morning, for no particular reason, and noticed a kernel error, but I am experiencing no problems and btrfs reports no errors. Must be self healing.

[SpecialEd]

I got myself a CD caddy for my 1TB HDD after replacing it with a 500GB SSD. It loaded fine, was recognized immediately, blah, blah, blah. BUT, it may be my imagination but my ASUS Q500A laptop seems to be running a lot hotter even when I'm not accessing that drive.

[GreyGeek]

My core temperature used to average 38-42C before installing my 2nd and 3rd HDs. Now, it averages 42-47C at idle, while typing this.

When I fire up Minecraft 1.12 with Forge and 7 mods on full screen (17") with my GT 650M Nvidia GPU, and fly in a straight line as fast as I can, with the chunk load at 8, my core temp oscillates between 70-80C. At 80C the fan turns on full blast. With the chunk load at maximum my Core temp can hit 85C and the screen will stutter on occasions. At 90C my computer reboots. My CPUs are supposedly rated at 105C but this box is 5 years old and I suspect that the thermal paste has dried out somewhat.