Hello,
I have a Pogoplug V4 with working ssh access.
At some point, the file system was locked in read-only mode, and I'm unable to undo it.
dmesg is overflooded with messages like

[ 11.150000] UBIFS error (pid 652): ubifs_budget_space: cannot budget space, error -30

The device is installed in a remote location, where I cannot access the serial console.
It should be possible to insert a USB/SD card, but still complex.

What would be the easiest and safest way to recover it and possibly install OpenWrt?

Here is the output of some commands I tried

~ # mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,relatime)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
none on /tmp type tmpfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)

~ # mount -o remount,rw,noatime /
mount: mounting ubi0:rootfs on / failed: Invalid argument

~ # df -h
Filesystem Size Used Available Use% Mounted on
rootfs 97.0M 89.2M 7.8M 92% /
ubi0:rootfs 97.0M 89.2M 7.8M 92% /
none 57.9M 9.7M 48.2M 17% /tmp

~ # dmesg | grep "cannot budget space"|wc -l
178

~ # dmesg | grep -v "cannot budget space"
[ 13.980000] XCE: XCE: LED -> DISCONNECTED

~ # cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"

~ # ubinfo -a
UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:63
Present UBI devices: ubi0

ubi0
Volumes count: 1
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 895 (113643520 bytes, 108.4 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 1
Count of reserved physical eraseblocks: 8
Current maximum erase counter value: 171
Minimum input/output unit size: 2048 bytes
Character device major/minor: 252:0
Present volumes: 0

Volume ID: 0 (on ubi0)
Type: dynamic
Alignment: 1
Size: 883 LEBs (112119808 bytes, 106.9 MiB)
State: OK
Name: rootfs
Character device major/minor: 252:1

I was trying to follow the steps provided here https://forum.doozan.com/read.php?4,100764,101409#msg-101409
I could workaround the read-only FS using the following approach

/tmp # ./tools/fw_printenv
Cannot parse config file: No such file or directory
/tmp # echo /dev/mtd0 0xc0000 0x20000 0x20000 >/etc/fw_env.config
-sh: can't create /etc/fw_env.config: Read-only file system
/tmp # mkdir /tmp/etc
/tmp # cp -a /etc/* /tmp/etc/
/tmp # mount --bind /tmp/etc /etc
/tmp # echo /dev/mtd0 0xc0000 0x20000 0x20000 >/etc/fw_env.config
/tmp # ./tools/fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

But I'm afraid to continue without knowing the status of bad blocks. The info about it is not visible in dmesg because of the huge amount of "cannot budget space" logs, and it was not recommended to proceed if a block in 0-7 is bad.

Thank you

Linux Device Hacking

Message History

Delivery option(s)