Bananian

banana pi pro - expand filesystem error??

5 3646
  • hardware:

Banana Pi Pro.
Power Source is a TP-LINK UH720 7-Port USB 3.0 HUB + 2 powerports (2,4A)
SD-Card is a Samsung Memory 32GB EVO MicroSDHC UHS-I Grade 1 Class 10 Memory Card (up to 48MB/s) with SD Adapter.
keyboard is a Perixx Periboard-716DE.

  • problem:

Do I have a problem? After expanding with bananian-config, this warning showed up:
...
Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match resize2fs_once Default-Start values (2 3 4 5 S)
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match resize2fs_once Default-Stop values (none)
...
  1. Your current hardware configuration is: BananaPi
  2. Do you want to change it? (y/N) N
  3. ---------------------------------------------------------------------------------
  4. Do you want to expand the root file system (recommended)? (y/N) y

  5. Expanding root file system... (ignore the warnings and reboot immediately)


  6. Command (m for help):
  7. Disk /dev/mmcblk0: 32.0 GB, 32010928128 bytes
  8. 4 heads, 16 sectors/track, 976896 cylinders, total 62521344 sectors
  9. Units = sectors of 1 * 512 = 512 bytes
  10. Sector size (logical/physical): 512 bytes / 512 bytes
  11. I/O size (minimum/optimal): 512 bytes / 512 bytes
  12. Disk identifier: 0x6c70c806

  13.         Device Boot      Start         End      Blocks   Id  System
  14. /dev/mmcblk0p1            2048       43007       20480   83  Linux
  15. /dev/mmcblk0p2           43008     3970047     1963520   83  Linux

  16. Command (m for help): Partition number (1-4):
  17. Command (m for help): Partition type:
  18.    p   primary (1 primary, 0 extended, 3 free)
  19.    e   extended
  20. Select (default p): Partition number (1-4, default 2): First sector (43008-62521343, default 43008): Last sector, +sectors or +size{K,M,G} (43008-62521343, default 62521343): Using default value 62521343

  21. Command (m for help):
  22. Disk /dev/mmcblk0: 32.0 GB, 32010928128 bytes
  23. 4 heads, 16 sectors/track, 976896 cylinders, total 62521344 sectors
  24. Units = sectors of 1 * 512 = 512 bytes
  25. Sector size (logical/physical): 512 bytes / 512 bytes
  26. I/O size (minimum/optimal): 512 bytes / 512 bytes
  27. Disk identifier: 0x6c70c806

  28.         Device Boot      Start         End      Blocks   Id  System
  29. /dev/mmcblk0p1            2048       43007       20480   83  Linux
  30. /dev/mmcblk0p2           43008    62521343    31239168   83  Linux

  31. Command (m for help): The partition table has been altered!

  32. Calling ioctl() to re-read partition table.

  33. WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
  34. The kernel still uses the old table. The new table will be used at
  35. the next reboot or after you run partprobe(8) or kpartx(8)
  36. Syncing disks.
  37. update-rc.d: using dependency based boot sequencing
  38. update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match resize2fs_once Default-Start values (2 3 4 5 S)
  39. update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match resize2fs_once Default-Stop values (none)
  40. Please reboot
Copy the Code
When I had an issue resizing a partition, I put the SD card into a card reader, and used gparted under Linux to fsck the partition.

It solved the issue for me.

tkaiser  
Have you tried to reboot in the meantime?

yes I did. Seems to boot marvelously. But I don't know if I should check this matter. fsck sometimes makes things worse...

tkaiser  
herrmeier replied at Fri Jan 16, 2015 06:22
yes I did. Seems to boot marvelously. But I don't know if I should check this matter. fsck sometimes ...

Everything's allright. If you let bananian-config resize the rootfs then it just calls "raspi-config --expand-rootfs" end the results are as expected. You get warnings regarding partitioning and when you reboot automagically 'resize2fs /dev/mmcblk0p2' does the job. If "df -h" shows the correct partition size then there's no need to call fsck.

IIRC I asked Nico to change the behaviour of bananian-config to redirect stderr to /dev/null and echo "Reboot immediately for changes to take effect"... But maybe I remember wrong and I just wanted to suggest that...

@tkaiser: Thank you very much for sharing! All the best and a great sunday to all. Is it somehow possible to mark this thread as solved?

You have to log in before you can reply Login | Sign Up

Points Rules