- Code: Select all
df- h
ls -l /tmp
ls -l /tmp/upgrade
df- h
ls -l /tmp
ls -l /tmp/upgrade
There is an .img file generated of 251MB (263.208.960 bytes). Do you want me to post (a link to) that file?
I'll run it now for the sda5 too?
ls -l /etc/init.d/rcS*
-rwxr-xr-x 1 root root 20716 2020-03-21 09:59 /etc/init.d/rcS
-rwxr-xr-x 1 root root 20399 2017-05-20 12:28 /etc/init.d/rcS.org
cat /boot.log
e2fsck -fn /dev/sda5
Jocko wrote:So try to run step2 and re-post
- Code: Select all
df- h
ls -l /tmp
ls -l /tmp/upgrade
/dev/sda5: recovering journal
The filesystem size (according to the superblock) is 385528 blocks
The physical size of the device is 384536 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes
dd if=/dev/sda5 bs=1 of=/share/1000/public/sda5.img > dd.txt &
btw: i'm now running
Code:
dd if=/dev/sda5 bs=1 of=/share/1000/public/sda5.img > dd.txt &
I guess it will again take half a day
cd /rw_fs
tar -czf /my-sda5-etc.gz etc
cat /boot.log
df -h
e2fsck -n /dev/sda5
tune2fs -l /dev/sda5
Nopeetn wrote:I assume I need to restore the backup file first and then retry the upgrade?
Found sda5 backup file, we go to format again sda5...
Creating filesystem with 384536 1k blocks and 96256 inodes
Filesystem UUID: 79bedc37-a865-4d02-96b0-cd2a305ad026
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Allocating group tables: 0/47 done
Writing inode tables: 0/4728/47 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/47 done
We run now a fs scan...
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 11/96256 files (0.0% non-contiguous), 22438/384536 blocks
Regular boot script is restored...
We restore now sda5 content...
etc/
etc/nas_conf_db.xml
etc/nas_ext_hdd_db.xml
etc/ntp.conf
etc/dropbear/
etc/dropbear/dropbear_rsa_host_key
etc/dropbear/dropbear_rsa_host_key.org
etc/ssl/
etc/ssl/owncert.pem
etc/nas_conf_db.xml.bak
etc/mdadm.conf
etc/nas_conf_db.xmle
etc/install-firmware.log
you should have now the file my-sda5-etc-old.gzJocko wrote:The regular boot script is restored after rebooting and your backup archive is renamed : my-sda5-etc-old.gz
Users browsing this forum: No registered users and 5 guests