I've been obsessed with sharing my desktop files over the home network to all the devices connected to my home router. I finally did it once as I said here. Since then, after several reinstalls and wipes of hard drives, I lost the configuration file for the original system. In short I can't make it work. I've forgotten how I did it exactly.
It turns out that samba and my samba configuration files aren't to blame.
I was doing firewall configuration files with my rkhunter setup. I noticed that I don't have any entry for samba. I added my samba rule in the firewall. I checked my smartphone file manager and there it is my shares automatically appearing and ready for use. No login required.
The firewall rule is:
#ufw allow samba
Saturday, September 10, 2016
This is not going away soon. Will you give up this kind of power? To take life without answering for it?
Tuesday, September 6, 2016
Good night. Oh it's morning. Good morning then.
I retried the previous command. It worked. The resync restarted from where it was interrupted.
#mdadm /dev/md0 --stop
This returns a message that my component devices are BUSY. Are they just trying to ignore me? Not at this ungodly hour, okay. So I have to stop the devices.
#mdadm -assemble --update=resync /dev/md0 /dev/sdb1... /dev/sdd1
Using Ubuntu 16.04 with RAID and Logical Volumes. I am adding Disk Encryption to my skill set. After using the Fedora 24 installer to do all of these in one night (and day) of operating system installation fiesta, I am now trying to finish the same thing using the Ubuntu installer this early morning. There's a power loss of about 30 seconds. It happens in the very early morning. Some power engineer decided to test a new hardware or to pull out an equipment for servicing in the wee hours of the morning while I'm in the middle of resyncing my RAID. I heard the sigh of the fan motors.I checked the status of the RAID - inactive, okay. Then bring it back on, right? I had to continue the resync somehow so I went back to the mdadm man pages.
Monday, August 29, 2016
#vgchange --activate y ubuntu-vg
If you have data in the missing volumes, first try to salvage it. Afterwards, the remaining logical volumes are activated with this command:
#vgreduce --removemissing ubuntu-vg
I think in my case the physical volume was really wiped out, formatted, erased including the metadata. So, can I restore the volume group instead with the remaining physical volume? With the commands pvdisplay, vgdisplay and lvdisplay, it looks promising that I could. After consulting the man pages for vgreduce and vgchange I hit the terminal again.
Unfortunately, I get an error message telling me that the Device is not found. (or ignored by filter). So I have to check the /etc/lvm.conf if by chance my device is simply being ignored or left out, simply not detected due to an uncommented line in the file.
#pvcreate --uuid UUID --restorefile PATH-TO-THE-BACKUP-FILE-
volume-group". So pick the current or latest one in /etc/lvm/backups or the older ones in /etc/lvm/archives/"volume- group". You need two things - the backup configuration file and the UUID of the physical volume. Using the terminal type:
LVM keeps its configuration files in /etc/lvm/backups and also in /etc/lvm/archives/"name-of-
I had to reinstall my linux operating system with an existing LVM over RAID. During the install I formatted one of the physical volumes PV. I used it for / (root), swap and /boot partitions. I could have used the existing Logical Volume LV for these but this device is also encrypted. I doubt I can reuse it without unlocking it. So I simply wiped it clean and made a clean install. After reboot I checked the status of the LVM and the RAID. Both are okay-ish. The RAID is clean according to mdadm. LVM informed me that the volume group is degraded. I'm missing a physical volume. I know I wiped it clean.So how do I restore the volume group so I can get at my data.
Now check the status of your LVM with pvdisplay, vgdisplay and lvdisplay. My logical volumes now appear on the file manager, so that's a good sign I have saved the data.
Monday, August 22, 2016
Lives that are (1) napabuti, (2) naituwid, at (3) nailigtas.— Ram (@RamuelAsturiano) August 22, 2016
Di mga buhay na biglang nawala. #BEST @risahontiveros pic.twitter.com/7m7YK25Emh
Thursday, August 18, 2016
It's been a while since I created these logical volumes and extended my volume group (the only one) to include the newly grown raid5 array on a 2-2-1 TB device. Frown all you want as long as it works. When that 1 TB HDD shows some signs of failing or error, I'll replace it with a 2TB HDD. The raid array will then be a complete 2-2-2 TB raid5.
Here's the status of the raid array now:
I'm replacing the 1 TB HDD when it fails or errors, or when I need to increase the capacity of the array, whichever comes first. The present raid array size is 2 TB.