NOTE! This site uses cookies and similar technologies.

If you not change browser settings, you agree to it.

I understand

Welcome, Guest
Username: Password: Remember me

TOPIC: could not mount /flash/SYSTEM after upgrading 1.95.5 to 1.95.7

could not mount /flash/SYSTEM after upgrading 1.95.5 to 1.95.7 4 years 11 months ago #1

  • opperpanter
  • opperpanter's Avatar
  • Offline
  • Junior Boarder
  • Posts: 22
  • Karma: 0
Hello,

I found some older threads with similar problems, but no solution.

I was running 1.95.5 (intel) nice and shiny on my DH55TC+Pentium G6950.
I upgraded to 1.95.7 using automatic update.
It told me to reboot, which I did.
The update process updated the kernel en system 'partitions'.
Then another reboot.

This fails with something like:
Error in prepare_sysroot: mount_common: Could not mount /flash/SYSTEM ******

Is there anything I can do to save my install, help debugging the problem by sending logs?
The administrator has disabled public write access.

Re: could not mount /flash/SYSTEM after upgrading 1.95.5 to 1.95.7 4 years 11 months ago #2

  • sraue
  • sraue's Avatar
  • Offline
  • Developer
  • Posts: 2094
  • Thank you received: 650
  • Karma: 130
can you:
- boot from a live cd
- check if the first partition (/flash) is full
- check the SYSTEM file for size and maybe md5 and comare with the file from our image you can manually download on our site?
- to fix the problem manually copy the SYSTEM file (maybe the KERNEL file too) to this partition
The administrator has disabled public write access.

Re: could not mount /flash/SYSTEM after upgrading 1.95.5 to 1.95.7 4 years 11 months ago #3

  • opperpanter
  • opperpanter's Avatar
  • Offline
  • Junior Boarder
  • Posts: 22
  • Karma: 0
Thanks.


I have mounted the first (and only) partition to /mnt/usb on a debian squeeze install.

It looks like this:
Disk /dev/sde: 4040 MB, 4040748544 bytes
255 heads, 63 sectors/track, 491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1         492     3946043   ee  GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(491, 66, 14)

and
root@NAS:/mnt/usb# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sde1               177487     97208     80279  55% /mnt/usb

and
root@NAS:/mnt/usb# ls -l
total 91574
-rw-r--r-- 1 root      root           109 Jul 16 20:54 extlinux.conf
-rw-r--r-- 1 valentijn valentijn  4411376 Aug 23 12:41 KERNEL
-r--r--r-- 1 root      root         32256 Jul 16 20:53 ldlinux.sys
drwx------ 2 root      root         12288 Jul 16 20:53 lost+found
-rwxr-xr-x 1 root      root      89313280 Jul 16 20:54 SYSTEM

Looks like only KERNEL got updated to .7 ?
The size matches the one downloaded from the site.

Should there be more partitions?
Should the SYSTEM image also have been upgraded?

I'll try to copy the SYSTEM image manually and see what happens.

It wouldn't be a big problem to start with a fresh install, I just want to help you guys make the autoupdate robust.
The administrator has disabled public write access.

Re: could not mount /flash/SYSTEM after upgrading 1.95.5 to 1.95.7 4 years 11 months ago #4

  • opperpanter
  • opperpanter's Avatar
  • Offline
  • Junior Boarder
  • Posts: 22
  • Karma: 0
I copied over the SYSTEM image to the /dev/sde1 partition and now the upgrade is finished. Running 1.95.7 succesfully, library and settings are still intact.
The administrator has disabled public write access.