Shifting Linux Filesystem From One SSD To Another

Soumik Chakraborty — Tue, 08 Aug 2023 10:43:08 +0000

Storyline

I use my gaming laptop as a daily driver for streaming and coding since I shifted to a new city. The base storage of the laptop is a 128G ssd in which I have a running archlinux installation with EFI boot partition and Linux filesystem partition. Now I wanted to play games on Lutris but my root partition only being 128G I need more space for more games.
I bought a 500G ssd and an external M.2 to USB adapter so that I can move my installation there.

Execution

First we need to create a similar partition table in the new ssd. Lets say when we connected the ssd using the external M.2 USB adapter its being detected as /dev/sdc. Check the device from the following command.

sudo fdisk -l

Lets say our root file system is on device

/dev/nvme0n1, check the partition table against /dev/nvme0n1 by using the same command as above

sudo fdisk -l

In my case I have two partitions against nvme0n1

nvme0n1p1 300M EFI System
nvme0n1p2 118.9G Linux filesystem

Now I will try to replicate a similar file system to /dev/sdc

sudo fdisk /dev/sdc
# now press m from help

press g to create a new gpt partition table
press n to create the first partition
press enter to accept the default starting sector
then enter +300M to create a partition with ending sector allowing a 300MB partition

press t to change the partition type
press L to list all existing partition numbers and choose the number listed against the EFI System otherwise the default would be linux filesystem

In my case EFI System is listed against 1 so I enter 1 as input and press enter

After the partitions has been created we can replicate data from one partition to another using dd command

# copy the EFI System data
sudo dd if=/dev/nvme0n1p1 of=/dev/sdc1

# copy the linux filesystem data
sudo dd if=/dev/nvme0n1p2 of=/dev/sdc2

Now use we need to resize the dd filesystem of sdc2 to allow the whole ssd space

sudo resize2fs /dev/sdc2

We are not done yet we still need to refresh the boot partition grub settings against the new storage in which we replicated the file system,

First create a linux bootable live usb, in my case I am using ubuntu.
Replace the ssd with the new ssd and bootup the system using the live usb created.
Now we need to manually mount the partitions before we can update grub
First we mount the linux file system partition

# first we mount the linux file system
sudo mount /dev/nvme0n1p2 /mnt

# then we mount the EFI partition
sudo mount /dev/nvme0n1p1 /mnt/boot/efi

# then we bind mount before performing chroot
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys

# now we perform the chroot command
sudo chroot /mnt

# now we perform the grub install and grub update commands
grub-install

Now we are done. Reboot the system and boot from the storage device itself the operating system should boot up fine

How To Agile

Soumik Chakraborty — Mon, 17 Aug 2020 02:04:24 +0000

Agile development defines a team that shows traits like collaborative efforts, self-organizing, and cross-functionality. There are mainly two frameworks for agile project management KANBAN and SCRUM.

KANBAN

This particular framework defines a continuous flow of work to the team thus focusing on efficiency as the team always knows what's the next task to come after the current one is finished.
Visualize it as a set of cards with a predefined set of works to be done and the due process completes a given project. These well-defined cards are atomic tasks. Teams can be divided with a set of cards to be completed.

Ex:-

DevOps | Github pipelines, dockers and cloud management
Backend | Api development, documenting
Frontend | Boilerplate, Themeing, Component flow mapping

KANBAN FLOW

SCRUM

This framework has a given time frame as the sprint window like 1 week or 2 weeks. Given tasks are divided into sets, estimating deliverables in the time frame chosen. Then these sets of work are allotted to teams to be sprinted upon in the given window. At the end of the sprint window, the external (task creator | scrum master) takes the list of work done.
The incomplete tasks/ bugs encountered in the given window is sprinted in the next time frame.

Ex: - Let's take the 1st-week window

DevOps:- sets docker-compose and GitHub workflows
Backend:- Designs API listing to be ingested and documents
Frontend :- Sets up bolierplate and themeing.

SCRUM FLOW

PROS

KANBAN

FLEXIBILITY:- The team is never overloaded with work as it only advances to the next task once the current ones done. The team is free to choose the order of completion of the tasks allotted.

INCREASED THROUGHPUT:- Efficiency is the first priority as the team always knows what to do next and thus doesn't sits idle or involves time on planning or strategies.

GOOD COMMUNICATION:- The team works in a closely coupled internal structure as it focuses to its own deliverables.

SCRUM

QUICK PLANNING:- As the team only needs 1/2 weeks of task set, so planning could be made quickly to get the progress started sooner. While the team's busy with the current set of work the scrum master can plan for the next window.

GREATER COLLABORATION:- The interdependence among teams is not an issue as the teams coupled, share a common set of deliverables.

SELF ORGANIZING:- As the team is provided with a big set of deliverables so the teams can plan atomic tasks on its own. Thus atomic planning is still in the dev team's hands.

RAPID IMPROVEMENT:- The issues in the current sprinted work can be dealt with in the next sprint. Focusing only on changes assures the robustness of outputs from each window.

CONS

KANBAN

CAN FALL APART QUICKLY:- If a project has a coupling dependency between teams, one team's lag or incompetency causes delivery issues on its end but also creates a domino effect on other teams thus the project falls apart and needs replanning.

NEED CONSTANT FLOW OF WORK:- As the throughput is high the teams need a constant inflow of work. If it's not attended to, the idle time of the team will increase and thus the project might fall apart.

DEADLINE PREDICTION IS TOUGH:- As the teams are free to choose the precedence of work and moves to the next set of work after the previous one has clearance thus the final deadline of the whole project is quite a hassle to predict and might often be impossible.

PRIORITY OF WORK IS NOT STATIC:- As the team itself sets the precedence, it often differs from the planner's perspective and that leads to issues.

SCRUM

SPRINT REVIEW LEADS TO MORE MEETINGS:- Each sprint review takes comparatively more time and involves more meetings than kanban. Thus this leads to eating up more dev time in standups and meets.

REQUIRES A LITTLE TIME TO GET IN PREDICTION FLOW:- When a new project starts off, timeline prediction takes some initial sprints to be set as the team takes some time to get used to the process flow.

PROPER WORKLOAD PLANNING:- If the task set is not correctly broken down to the team's throughput in a timeframe, each set can take more time to be completed than anticipated thus breaking the flow.

Some softwares to manage agile projects are

wish this helps you follow deadlines better

Forem: Soumik Chakraborty

Shifting Linux Filesystem From One SSD To Another

Storyline

Execution

Lets say our root file system is on device

Now I will try to replicate a similar file system to /dev/sdc

After the partitions has been created we can replicate data from one partition to another using dd command

We are not done yet we still need to refresh the boot partition grub settings against the new storage in which we replicated the file system,

How To Agile

Agile development defines a team that shows traits like collaborative efforts, self-organizing, and cross-functionality. There are mainly two frameworks for agile project management KANBAN and SCRUM.

KANBAN

KANBAN FLOW

SCRUM

SCRUM FLOW

PROS

KANBAN

SCRUM

CONS

KANBAN

SCRUM