DM500 Unable to write to filesystem :(

[gifulo]

Hi all - long time reader, first time poster... first off, thanks to everyone who shares their knowledge, has been a massive help!

So... my problem - any suggestions, very warmly welcomed!

I've had my DM500C up and running for a few months now, followed many of the guides here and didn't have any real problems in getting started. However, the filesystem is no longer allowing me to write to it. I can connect via FTP no probs (or Telnet), but all attempts to write or edit files ends with a filesystem error, indicating there's no write permission. Also have the same kind of errors upon doing a scan, where it couldn't write the results and gave me a fatal error.

The folder permissions look fine (write for all), so I'm at a loss as to how this has happened - one day it was working, the next it was stopping me!

If anyone knows how I can rectify this (or any checks I should perform), please help a cabler in need! Don't particularly want to factory reset and start again (unless it's quick and easy with any tools).

[junkiepilot]

The image has gone read-only. There is no logical explanation it just happens now and again.

You should still be able to write to /tmp.

Stick an image in there and re-flash it.

Telnet to the box and paste the following command:

cat /dev/mtd/3 > /tmp/backup.img

then...

cd /tmp && eraseall /dev/mtd/3 && cp backup.img /dev/mtd/3 && reboot

[gifulo]

Thanks for the quick response junkiepilot! Got to love those illogical 's*it happens' system moments

I've followed your instructions, but it's stated "Segmentation fault" on the second command - narrowed it down to the "cp backup.img /dev/mtd/3" image copy. Does this error ring any bells?

[jfish]

Hi all - long time reader, first time poster... first off, thanks to everyone who shares their knowledge, has been a massive help!

So... my problem - any suggestions, very warmly welcomed!

I've had my DM500C up and running for a few months now, followed many of the guides here and didn't have any real problems in getting started. However, the filesystem is no longer allowing me to write to it. I can connect via FTP no probs (or Telnet), but all attempts to write or edit files ends with a filesystem error, indicating there's no write permission. Also have the same kind of errors upon doing a scan, where it couldn't write the results and gave me a fatal error.

The folder permissions look fine (write for all), so I'm at a loss as to how this has happened - one day it was working, the next it was stopping me!

If anyone knows how I can rectify this (or any checks I should perform), please help a cabler in need! Don't particularly want to factory reset and start again (unless it's quick and easy with any tools).

am sure I had a similiar issue, in the end my problem was no free space available, I deleted te icons folders and this seemed to fix it for me.

[gifulo]

Annoyingly, FTP and Telnet cannot access the box anymore and I'm now in the state of having deleted my image and not being able to reflash. I have a horrible feeling this is one of those null modem cable moments, which I don't have...

Is there a factory reset button on the box or anything else obvious that I'm missing?

[despdan]

The image has gone read-only. There is no logical explanation it just happens now and again.

You should still be able to write to /tmp.

Stick an image in there and re-flash it.

Telnet to the box and paste the following command:

cat /dev/mtd/3 > /tmp/backup.img

You have him manual put an image in the tmp folder then you get him to copy the image in flash into the tmp folder

cd /tmp && eraseall /dev/mtd/3 && cp backup.img /dev/mtd/3 && reboot

I would like to change this a little to:
cd /tmp
eraseall /dev/mtd/3 && cp backup.img /dev/mtd/3
reboot

The reason I do it this way is because if you forget to rename or put the image into the tmp folder you still can put it in there even after the erase. But if you do it your way the only option is dreamup.

Some times the box wont allow changes because the var folder is full, try deleting stuff

[junkiepilot]

You have him manual put an image in the tmp folder then you get him to copy the image in flash into the tmp folder

Perhaps the wording was a bit wrong, my bad.

I meant stick an image in /tmp by running the backup command that followed.

[gifulo]

Sooo.... you'll be glad to know I'm back up and running. Popped out and grabbed a null modem cable (was going to need one eventually when I fiddled around a little too much!), reflashed and a bit of magic later, I'm back up and running.

Oh and the filesystem is allowing me to write on it again. I reckon it could've been a space issue (had a fair number of picons on there and a skin), although I checked the other day and it seemed ok... maybe I was using the wrong commands.

What's the easiest way to check for remaining space?

Thanks to everyone who's replied though, got there in the end