Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 10 hrs, 2 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 22 hrs ago - more...
|
2012-02-01
, 05:55
|
|
Posts: 116 |
Thanked: 44 times |
Joined on Nov 2010
@ Chennai, India
|
#52
|
Someone active here can help me??? I have posted this already in The Great NITDroid forum, but this thread seems more relevant too. So re-posting here, sorry for my ignorance.
Scenario is below:
I have a got this problem, 'Memory read-only. Cannot write to the device'.
The problem maybe with I have created partitions, but with wrong block size.
I have the 8GB appln install space eMMC. With that, my partition table appeared to be
Device Boot Start End
/dev/mmcblk0p1 2 688258
/dev/mmcblk0p2 688258 950401
/dev/mmcblk0p3 950402 974977
Instead of usual
Device Boot Start End
/dev/mmcblk0p1 2 884865
/dev/mmcblk0p2 884866 950401
/dev/mmcblk0p3 950402 974977.
So I carried out a partitioning like
n
p
1
First cylinder: 2
Last cylinder: 600000
n
e
First cylinder: 600001
Last cylinder: 688258
n
First cylinder: 600001
Last cylinder: 688258
t
Is there a problem due to this? And i now cannot copy any files into the eMMc or even move within. Shows memory read only or input/output error- when done from xterm.
And also when tried to untar the NITDroid archive, it shows bad input. Input/output error. Says the file is not actually of tar.gz type archive when actually it is.
Code:
mounting it back again fails too.
Code:
Anyone has an idea what the problem is?
Scenario is below:
I have a got this problem, 'Memory read-only. Cannot write to the device'.
The problem maybe with I have created partitions, but with wrong block size.
I have the 8GB appln install space eMMC. With that, my partition table appeared to be
Device Boot Start End
/dev/mmcblk0p1 2 688258
/dev/mmcblk0p2 688258 950401
/dev/mmcblk0p3 950402 974977
Instead of usual
Device Boot Start End
/dev/mmcblk0p1 2 884865
/dev/mmcblk0p2 884866 950401
/dev/mmcblk0p3 950402 974977.
So I carried out a partitioning like
n
p
1
First cylinder: 2
Last cylinder: 600000
n
e
First cylinder: 600001
Last cylinder: 688258
n
First cylinder: 600001
Last cylinder: 688258
t
Is there a problem due to this? And i now cannot copy any files into the eMMc or even move within. Shows memory read only or input/output error- when done from xterm.
And also when tried to untar the NITDroid archive, it shows bad input. Input/output error. Says the file is not actually of tar.gz type archive when actually it is.
Code:
Code:
root umount /dev/mmcblk0p1 fsck -a /dev/mmcblk0p1 fsck 1.41.3.maemo0 (12-Oct-2008) dosfsck 2.11, 12 Mar 2005, FAT32, LFN Seek to 22552772096:Invalid argument
Code:
Code:
mount /dev/mmcblk0p1 /home/user/MyDocs/ mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed! Device or resource busy
|
|
2013-07-11
, 21:17
|
|
Posts: 1,424 |
Thanked: 2,623 times |
Joined on Jan 2011
@ Touring
|
#53
|
I am also having what I thought was the regular read only issue but even when I unmount and remount -o rw I still get permission denied. Unless I try as root, then no problems at all. As this is fat32 there shoudnt be any chown issues...
It is not a corruption issuefdisk fsck!!(yipes) comes back clean every time.
Been a long time since I had to deal with unix read/write problems so my magic is weak and google isn't helping.
Last edited by biketool; 2013-07-12 at 06:41.
It is not a corruption issue
Been a long time since I had to deal with unix read/write problems so my magic is weak and google isn't helping.
Last edited by biketool; 2013-07-12 at 06:41.
 |
|
2013-07-12
, 00:54
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#54
|
Originally Posted by biketool
fdisk?
It is not a corruption issue fdisk comes back clean every time.
I don't see how you can still have read-only issues after a correct application of fdisk
Seriously, try checking the partition in Windows. Or use fsck on your phone, but I'd rather recommend the Windows way.
|
|
2013-07-12
, 06:13
|
|
Posts: 1,424 |
Thanked: 2,623 times |
Joined on Jan 2011
@ Touring
|
#55
|
pichlo, it is weirder than that, it is not actually read-only since I can write to the partition as root. I tried sudo chmod -R 777 /home/user/MyDocs but it didn't not fix the prob. Being a fat32 partition chown does nothing and fails.
Last night I ssh'd in to the N900 ran midnight commander as sudo and installed a FTP daemon on my laptop and used this acrobatic method to transfer my wifes music to the phone MyDocs where I normally just mount MyDOcs via wifi/SCP on my laptop.
(edit)Btw, I was tired and realized I had typed fdisk on my post, fortunately I had used fsck on the N900!
I know this is something with permissions but it has been ten years at least since I have had a permissions issue like this.
Last edited by biketool; 2013-07-12 at 08:54.
Last night I ssh'd in to the N900 ran midnight commander as sudo and installed a FTP daemon on my laptop and used this acrobatic method to transfer my wifes music to the phone MyDocs where I normally just mount MyDOcs via wifi/SCP on my laptop.
(edit)Btw, I was tired and realized I had typed fdisk on my post, fortunately I had used fsck on the N900!
I know this is something with permissions but it has been ten years at least since I have had a permissions issue like this.
Last edited by biketool; 2013-07-12 at 08:54.
|
|
2013-07-12
, 11:12
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#56
|
I had the same on my N900, only on my SD card. Read only unless written to as root. Being FAT ruled out permissions, leaving only a file system corruption that root just ignored and burst in with all guns blazing. I had an issue with the USB port preventing me to connect it to a Windows machine so I just reformatted the card on the device. That fixed it.
|
|
2013-07-12
, 11:43
|
|
Posts: 1,424 |
Thanked: 2,623 times |
Joined on Jan 2011
@ Touring
|
#57
|
pichlo, were you getting errors or clean in fsck?
For some reason bootmenu wont work so I am stuck with fsck'ing from a running N900. But again fsck comes out clean.
just an example I made a directory called hats
Last edited by biketool; 2013-07-12 at 12:49.
For some reason bootmenu wont work so I am stuck with fsck'ing from a running N900. But again fsck comes out clean.
Code:
~ $ sudo umount /dev/mmcblk0p1 ~ $ sudo fsck -a /dev/mmcblk0p1 fsck 1.42.5 (29-Jul-2012) dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN /dev/mmcblk0p1: 9120 files, 288375/442377 clusters
Code:
~ $ sudo mount rootfs on / type rootfs (rw) ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /tmp type tmpfs (rw,noatime,size=1024k) tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755) none on /dev type tmpfs (rw,noatime,size=10240k,mode=755) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k) /dev/mmcblk0p2 on /home type ext3 (defaults) /home/opt on /opt type none (bind) nodev on /sys/kernel/debug type debugfs (0) /opt/pymaemo/usr/lib/python2.5 on /usr/lib/python2.5 type bind (bind) /opt/pymaemo/usr/share/pyshared on /usr/share/pyshared type bind (bind) /opt/pymaemo/usr/lib/pyshared on /usr/lib/pyshared type bind (bind) /opt/pymaemo/usr/share/python-support on /usr/share/python-support type bind (bind) /opt/pymaemo/usr/lib/python-support on /usr/lib/python-support type bind (bind) /dev/mmcblk0p1 on /home/user/MyDocs type vfat (0)
Code:
~/MyDocs $ sudo chmod -R 777 /home/user/MyDocs/ ~/MyDocs $ rm -rf hats/ rm: cannot remove 'hats': Permission denied ~/MyDocs $ sudo rm -rf hats ~/MyDocs $
Last edited by biketool; 2013-07-12 at 12:49.
|
|
2013-07-12
, 12:52
|
|
Posts: 1,424 |
Thanked: 2,623 times |
Joined on Jan 2011
@ Touring
|
#58
|
What is the downside on dumping the contents of MyDocs into a directory on my laptop, fdisk'ing /dev/mmcblk0p1, and then pouring the contents back in. I dont think the N900 uses symlinks like the old Zaurus used to.
|
|
2013-07-12
, 13:41
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#59
|
Originally Posted by biketool
Dunno, I didn't bother to check. Just reformatted the blighter.
pichlo, were you getting errors or clean in fsck?
For some reason bootmenu wont work so I am stuck with fsck'ing from a running N900. But again fsck comes out clean.
Originally Posted by biketool
Depending on what program you use for the operation, the files' time stamps may get nuked. Otherwise no downside: just the opposite, it might improve performance a bit by fixing any fragmentation.
What is the downside on dumping the contents of MyDocs into a directory on my laptop, fdisk'ing /dev/mmcblk0p1, and then pouring the contents back in.
Only I would use the stock file manager to do the formatting rather than fsck. It should provide the same results but somehow feels more like the "approved" way.
|
|
2013-07-12
, 14:29
|
|
Posts: 1,424 |
Thanked: 2,623 times |
Joined on Jan 2011
@ Touring
|
#60
|
pichlo, the USB port was broken and I accidently desoldered a SM component fixing it, too small to replace IMHO; I dont know if running windows in a VM would be able to do the fix though the Ubuntu tool seems to work really well when I have used it with the other N900.
I will dump the MyDOcs to disk and format next week.
I will dump the MyDOcs to disk and format next week.
this way solved my problem also