RN316 does no finish booting and OS install gives error "could not extracting files) last FW

Hi Steve, thank you for sending this in.

Here are the results:

# rnutil chroot
root@3C62350D01347:/# btrfs fi df //
Data, single: total=3.01GiB, used=1.44GiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=497.50MiB, used=479.89MiB
GlobalReserve, single: total=240.00MiB, used=222.45MiB

Let me know if you had like to see this over a Teams meeting, I would need an email to send the invitation to.

Best regards,

---

helio wrote:

 

Data, single: total=3.01GiB, used=1.44GiB

---

This isn't full (used is 1.44 GiB out of 4), but I think it would be good to balance it (total allocated is 3 GiB)

This command would do that:

btrfs balance start //

It will give a warning (including a 10 second count down), but the OS partition is small, and it normally won't take very long (a minute or so).  

Then I suggest trying to mount the data volume, and see if that works.

If you are using XRAID, then the commands needed are:

# btrfs device scan
# btrfs fi show
# mount /dev/md127 /data

Note that if this works, you can then make a backup of your data (if you don't have one).

---

helio wrote:

 

Let me know if you had like to see this over a Teams meeting, I would need an email to send the invitation to.

---

I'm just another ReadyNAS owner, and I really can't do remote support.

Hey Stephen, 

It is not using X-Raid but Flex-Raid.

is the command the same if not, please, let me know, i stay put waiting for your reply.

Thank you.

Meanwhile the balance gave an error:

Starting balance without any filters.
ERROR: error during balancing '//': No space left on device
There may be more info in syslog - try dmesg | tail

bash: ERROR:: command not found
root@3C62350D01347:/# There may be more info in syslog - try dmesg | tail
bash: There: command not found
root@3C62350D01347:/# dmesg | tail
[ 264.060849] disk 0, o:1, dev:sdb5
[ 264.060853] disk 1, o:1, dev:sdc5
[ 264.060856] disk 2, o:1, dev:sda5
[ 264.060860] disk 3, o:1, dev:sdd5
[ 264.060864] disk 4, o:1, dev:sde5
[ 264.061090] md125: detected capacity change from 0 to 5000299151360
[ 264.081399] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 264.081605] BTRFS: device label 0ed5edda:root devid 1 transid 2563326 /dev/md0
[ 264.082254] BTRFS info (device md0): has skinny extents
[ 304.882558] BTRFS info (device md0): 15 enospc errors during balance

---

helio wrote:

Meanwhile the balance gave an error:

Starting balance without any filters.
ERROR: error during balancing '//': No space left on device
There may be more info in syslog - try dmesg | tail

---

Try 

btrfs balance start -dusage=0 //

and see if that completes.

If it does, try increasing dusage in steps (try 50 next)

---

helio wrote:

It is not using X-Raid but Flex-Raid.

is the command the same if not, please, let me know,

---

If you have a single volume, then the only thing you need to change is the volume name (/data) on the last command.  That needs to be your volume name (which you specified when you created the volume).

Note that is supposed to be 6 disks of 4TB , the  volume is called "data"

root@3C62350D01347:/# btrfs balance start -dusage=50 //
ERROR: error during balancing '//': No space left on device
There may be more info in syslog - try dmesg | tail
root@3C62350D01347:/# dmesg | tail
[ 264.061090] md125: detected capacity change from 0 to 5000299151360
[ 264.081399] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 264.081605] BTRFS: device label 0ed5edda:root devid 1 transid 2563326 /dev/md0
[ 264.082254] BTRFS info (device md0): has skinny extents
[ 304.882558] BTRFS info (device md0): 15 enospc errors during balance
[ 1510.489423] BTRFS info (device md0): 4 enospc errors during balance
[ 1753.653588] BTRFS: device label 0ed5edda:data devid 3 transid 4126965 /dev/md125
[ 1753.653684] BTRFS: device label 0ed5edda:data devid 2 transid 4126965 /dev/md126
[ 1753.653768] BTRFS: device label 0ed5edda:data devid 1 transid 4126965 /dev/md127
[ 1884.973521] BTRFS info (device md0): 4 enospc errors during balance

Here the mounting results:

root@3C62350D01347:/# btrfs device scan # btrfs fi show # mount /dev/md127 /Data
Scanning for Btrfs filesystems
root@3C62350D01347:/#

dmesg | tail
[ 264.060853] disk 1, o:1, dev:sdc5
[ 264.060856] disk 2, o:1, dev:sda5
[ 264.060860] disk 3, o:1, dev:sdd5
[ 264.060864] disk 4, o:1, dev:sde5
[ 264.061090] md125: detected capacity change from 0 to 5000299151360
[ 264.081399] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 264.081605] BTRFS: device label 0ed5edda:root devid 1 transid 2563326 /dev/md0
[ 264.082254] BTRFS info (device md0): has skinny extents
[ 304.882558] BTRFS info (device md0): 15 enospc errors during balance
[ 1510.489423] BTRFS info (device md0): 4 enospc errors during balance

Hi, it did not work, still cannot see my data shares:

Scanning for Btrfs filesystems

root@3C62350D01347:/# btrfs fi show

Label: '0ed5edda:root'  uuid: ae33cd9d-ca6c-4cfa-9b1d-eec946243757

        Total devices 1 FS bytes used 2.13GiB

        devid    1 size 4.00GiB used 4.00GiB path /dev/md0

Label: '0ed5edda:data'  uuid: cf02b0e0-e9f7-4b61-b57e-26975417ebb4

        Total devices 3 FS bytes used 12.68TiB

        devid    1 size 9.07TiB used 7.68TiB path /dev/md127

        devid    2 size 4.55TiB used 3.15TiB path /dev/md126

        devid    3 size 4.55TiB used 3.15TiB path /dev/md125

root@3C62350D01347:/# mount /dev/md127 /data

# btrfs fi df //
ERROR: not a btrfs filesystem: //

---

helio wrote:

# btrfs fi df //
ERROR: not a btrfs filesystem: //

---

Did you reboot?

This command worked before, correct?

yes, it worked before.

I rebooted after running 

mount /dev/md127 /data

to see if it worked.

What to do next?

How can I mount the file system back?

I noticed that the metadata looks quite full:

Metadata, DUP: total=497.50MiB, used=479.89MiB

I suspect that's why it's saying there is no remaining space, but I have no idea how it got to be so full to start with.

---

helio wrote:

I rebooted after running 

mount /dev/md127 /data

to see if it worked.

---

Did you reboot normally?

If you did, reboot in tech support mode again, and repeat the steps until you get the data volume mounted. (Don't try the balance).

At that point I think you should back up all the data, and do a factory default (setting up the NAS again).  We can start the SMB service if you need to back up over the network.

HI, yesterday, I got no error after running the mount cmd so I rebooted in normal mode to see if the data was available.

since then I get the error not a btrfs filesystem

at this point all I want is to back up the date but it says 

# mount /dev/md127 /Data
mount: mounting /dev/md127 on /Data failed: No such file or directory
# btrfs fi df //
ERROR: not a btrfs filesystem: //

how to get the btrfs up again and start SMB backup? 

Thanks,

StephenB Hello, Here are my last results, is it ready to start SMB backup or how to recover the data?

# rnutil chroot
root@3C62350D01347:/# btrfs fi df //
Data, single: total=3.01GiB, used=1.44GiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=497.50MiB, used=479.89MiB
GlobalReserve, single: total=240.00MiB, used=222.45MiB

root@3C62350D01347:/# btrfs device scan
Scanning for Btrfs filesystems
root@3C62350D01347:/# btrfs fi show
Label: '0ed5edda:root' uuid: ae33cd9d-ca6c-4cfa-9b1d-eec946243757
Total devices 1 FS bytes used 2.13GiB
devid 1 size 4.00GiB used 4.00GiB path /dev/md0

Label: '0ed5edda:data' uuid: cf02b0e0-e9f7-4b61-b57e-26975417ebb4
Total devices 3 FS bytes used 12.68TiB
devid 1 size 9.07TiB used 7.68TiB path /dev/md127
devid 2 size 4.55TiB used 3.15TiB path /dev/md126
devid 3 size 4.55TiB used 3.15TiB path /dev/md125

root@3C62350D01347:/# mount /dev/md127 /data

root@3C62350D01347:/# btrfs fi show
Label: '0ed5edda:root' uuid: ae33cd9d-ca6c-4cfa-9b1d-eec946243757
Total devices 1 FS bytes used 2.13GiB
devid 1 size 4.00GiB used 4.00GiB path /dev/md0

Label: '0ed5edda:data' uuid: cf02b0e0-e9f7-4b61-b57e-26975417ebb4
Total devices 3 FS bytes used 12.68TiB
devid 1 size 9.07TiB used 7.68TiB path /dev/md127
devid 2 size 4.55TiB used 3.15TiB path /dev/md126
devid 3 size 4.55TiB used 3.15TiB path /dev/md125

root@3C62350D01347:/# dmesg | tail
[ 1631.881384] disk 3, o:1, dev:sdd5
[ 1631.881388] disk 4, o:1, dev:sde5
[ 1631.881622] md125: detected capacity change from 0 to 5000299151360
[ 1631.897822] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 1631.898045] BTRFS: device label 0ed5edda:root devid 1 transid 2574192 /dev/md0
[ 1631.898746] BTRFS info (device md0): has skinny extents
[ 1711.771459] BTRFS: device label 0ed5edda:data devid 3 transid 4126974 /dev/md125
[ 1711.771548] BTRFS: device label 0ed5edda:data devid 2 transid 4126974 /dev/md126
[ 1711.771665] BTRFS: device label 0ed5edda:data devid 1 transid 4126974 /dev/md127
[ 1739.346811] BTRFS info (device md127): has skinny extents

root@3C62350D01347:/# btrfs fi df //
Data, single: total=3.01GiB, used=1.44GiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=497.50MiB, used=479.89MiB
GlobalReserve, single: total=240.00MiB, used=222.45MiB

Thanks :)

StephenB 

Yes, great, I see the shares : sorry I am slow to pick it up:

root@3C62350D01347:/# ls /data
AmazonCloudDrive DZI DropBox HdAProdz OneDrive Software Videos uFreak
Audio Documentation Freaks Music Pictures Transfer eBooks
BackUp Documents GDrive ODB Podcasts VSTIData home

StephenB  Is it ok to reboot and try a OS reinstall at this point?

---

helio wrote:

StephenB  Is it ok to reboot and try a OS reinstall at this point?

---

I'm not sure if it will help, but I think it is ok to try it.

Do you have a backup of the NAS data files?

StephenB , Hey, I do not have a backup of the data.

I would rather not reboot and get a SMB backup started.

I tried to start a backup from the PC but the RN316 would not accept my credentials when attempting to validate the source or could that just be the lack of SMB installed?

ok, how to backup from the support mode?

thanks

---

helio wrote:

 

ok, how to backup from the support mode?

 

---

Try entering 

systemctl start smb.service

Then see if you can access the shares from the PC.

I got this:

systemctl start smb.service
Running in chroot, ignoring request.

---

helio wrote:

I got this:

systemctl start smb.service
Running in chroot, ignoring request.

---

Try

service smb start

root@3C62350D01347:/# service smb start
smb: unrecognized service