Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
toh:linksys:whw03_v1 [2024/07/17 05:57] – [Repartitioning] lanchontoh:linksys:whw03_v1 [2024/07/17 06:09] – [Repartitioning] lanchon
Line 192: Line 192:
 IMPORTANT: DO NOT PROCEED WITHOUT DOING THE 2 SYSUPGRADES! For the procedure to succeed, the installed commands need to be in rootfs, not rootfs_data, as rootfs_data will have to be unmounted. IMPORTANT: DO NOT PROCEED WITHOUT DOING THE 2 SYSUPGRADES! For the procedure to succeed, the installed commands need to be in rootfs, not rootfs_data, as rootfs_data will have to be unmounted.
  
-- Make backups of the GPT (partition table) and relevant stock partitions:+- Make backups of the GPT (partition table):
  
 <code> <code>
Line 208: Line 208:
 33+0 records in 33+0 records in
 33+0 records out 33+0 records out
 +</code>
  
-# Note: The last partition (mmcblk0p19 "syscfg") has some configuration info used by stock firmware. +- Make backups of the stock partitions:
-# It is 3.4 GiB in size, with an ext4 filesystem that only contains about 250 KiB of files (when i looked). +
-# However this filesystem is not trimmed, and as time goes on it accumulates stale data in unused areas. +
-# If the backup commands below fail with /tmp running out of space, this stale data is the culprit. +
-# You then have 3 options: +
-# 1) If one backup fits in /tmp, scp the first backup, remove it from /tmp, then do the second backup. +
-# 2) Else pipe the backups over SSH (see below). (Note that this might not work from a Windows PC.) +
-# 3) Or mount and fstrim the partition to remove the stale data (requires the "fstrim" package).+
  
 +NOTE: The last partition (mmcblk0p19 "syscfg") has some configuration info used by stock firmware.
 +It is 3.4 GiB in size, with an ext4 filesystem that only contains about 250 KiB of files (when i looked).
 +However this filesystem is not trimmed, and as time goes on it accumulates stale data in unused areas.
 +If the backup commands below fail with /tmp running out of space, this stale data is the culprit.
 +
 +You then have 3 options:
 +
 +1) If one backup fits in /tmp, scp the first backup (see next step), remove it from /tmp, then do the second backup.
 +
 +2) Else pipe the backups over SSH (see below). Note that this might not work from a Windows PC due to character translations (but you could work some magic with base64 or similar).
 +
 +3) Or mount and fstrim the partition to remove the stale data (requires the "fstrim" package).
 +
 +<code>
 # now you can backup the complete eMMC (GPTs and all partitions): # now you can backup the complete eMMC (GPTs and all partitions):
  
Line 231: Line 239:
 you@your-pc:~$ ssh root@192.168.1.1 "gzip -c /dev/mmcblk0p19" >mmcblk0p19-syscfg.img.gz you@your-pc:~$ ssh root@192.168.1.1 "gzip -c /dev/mmcblk0p19" >mmcblk0p19-syscfg.img.gz
  
-# test your backups afterwards, especially if done from a Windows PC:+and test your backups after piping them, especially if done from a Windows PC:
  
 you@your-pc:~$ gzip -t mmcblk0*.img.gz you@your-pc:~$ gzip -t mmcblk0*.img.gz
  • Last modified: 2024/07/17 08:31
  • by lanchon