second boot == Read-only file system

Moderators: mdrjr, odroid

second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 9:39 am

Hi, 1st post. I've been working w/ the rPi for a couple years and I have about 2 dozen of them working in commercial applications. One hasn't had to be restarted in 3 years, taken 1000's of pictures, and never lost a network connection.

I was attracted to the odroid for it's RTC and ADC. But I'm struggling to just get the thing to boot. I only run headless. I managed to find a wheezy-minimal image on here that would actually boot great the first time. Not doing anything but simply sudo reboot after the initial boot, the odroid takes forever to allow me to ssh into again. Then whenever I try to do anything I get "Read-only file system"

Any help would be greatly appreciated. If I can get this thing to work I can easily replace the rPI w/ this and getting them out in the wild.

I need an image for headless operation that allows me to add packages and boots consistently.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby tobetter » Fri Mar 20, 2015 10:58 am

mulepic wrote:Hi, 1st post. I've been working w/ the rPi for a couple years and I have about 2 dozen of them working in commercial applications. One hasn't had to be restarted in 3 years, taken 1000's of pictures, and never lost a network connection.

I was attracted to the odroid for it's RTC and ADC. But I'm struggling to just get the thing to boot. I only run headless. I managed to find a wheezy-minimal image on here that would actually boot great the first time. Not doing anything but simply sudo reboot after the initial boot, the odroid takes forever to allow me to ssh into again. Then whenever I try to do anything I get "Read-only file system"

Any help would be greatly appreciated. If I can get this thing to work I can easily replace the rPI w/ this and getting them out in the wild.

I need an image for headless operation that allows me to add packages and boots consistently.

I guess you may not use SanDisk MicroSD, please confirm this and let us know what's the vendor and model of your MicroSD. C1 have MicroSD compatible issue, some vendor's MicroSD take over 40 seconds or boot failure on reboot. Cold boot would work anyhow.
tobetter
 
Posts: 2081
Joined: Mon Feb 25, 2013 10:55 am
Location: Kitchener, ON, Canada
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 11:26 am

I am using a SanDisk MicroSD. I can sort of live with the slow boot but it doesn't make any sense why I write the image to the SD and the first boot that follows is very fast. Then I do sudo reboot and it's slow.

The bigger issue is the system become "Read-only file system" after the that first boot. Therefore I cannot add/update any packages.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby tobetter » Fri Mar 20, 2015 11:30 am

mulepic wrote:I am using a SanDisk MicroSD. I can sort of live with the slow boot but it doesn't make any sense why I write the image to the SD and the first boot that follows is very fast. Then I do sudo reboot and it's slow.

The bigger issue is the system become "Read-only file system" after the that first boot. Therefore I cannot add/update any packages.

Could you please specify the model of your MicroSD and show me your boot.ini in BOOT partition.
tobetter
 
Posts: 2081
Joined: Mon Feb 25, 2013 10:55 am
Location: Kitchener, ON, Canada
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 11:39 am

It is a SanDisc MicroSD HC I 8GB Class 4

Here's my boot.ini

ODROIDC-UBOOT-CONFIG

# Possible screen resolutions
# Uncomment only a single Line! The line with setenv written.
# At least one mode must be selected.

# setenv m "vga" # VGA 640x480
# setenv m "480p" # 480p 720x480
# setenv m "576p" # 576p 720x576
# setenv m "800x480p60hz" # WVGA 800x480
# setenv m "720p" # 720p 1280x720
# setenv m "800p" # 800p(WXGA) 1280x800
# setenv m "sxga" # SXGA 1280x1024
setenv m "1080p" # 1080P 1920x1080
# setenv m "1920x1200" # 1920x1200

# HDMI/DVI Mode Configuration
setenv vout_mode "hdmi"
# setenv vout_mode "dvi"

# HDMI BPP Mode
setenv m_bpp "32"
# setenv m_bpp "16"

# UHS Card Configuration
# Uncomment the line below to __DISABLE__ UHS-1 MicroSD support
# This might break boot for some brand/models of cards.
# setenv disableuhs "disableuhs"

# T0 disable serial console, fomment first and uncomment second line
setenv bootargs "console=ttyS0,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304 a09859 rootwait ro no_console_suspend vdaccfg=0xa000 logo=osd1,loaded,0x7900000, 720p,full dmfc=3 cvbsmode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs}"
#setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro no_ console_suspend vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full dmfc=3 cvbsm ode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs}"

ext4load mmc 0:1 0x21000000 boot/uImage
ext4load mmc 0:1 0x22000000 boot/uInitrd
ext4load mmc 0:1 0x21800000 boot/meson8b_odroidc.dtb
fdt addr 21800000

# comment to ENABLE framebuffer
#fdt rm /mesonfb

# !!comment next 3 lines to ENABLE video
fdt rm /mesonstream
fdt rm /vdec
fdt rm /ppmgr

bootm 0x21000000 0x22000000 0x21800000
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby tobetter » Fri Mar 20, 2015 11:54 am

mulepic wrote:It is a SanDisc MicroSD HC I 8GB Class 4

Ah, might be because of Class 4, I have not success with it yet on my end. Do you have any other MicroSD, SanDisk Class 10?
# UHS Card Configuration
# Uncomment the line below to __DISABLE__ UHS-1 MicroSD support
# This might break boot for some brand/models of cards.
setenv disableuhs "disableuhs"

It wouldn't be relative with your issue but please try this in your boot.ini.
tobetter
 
Posts: 2081
Joined: Mon Feb 25, 2013 10:55 am
Location: Kitchener, ON, Canada
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 12:08 pm

I found a Class 6 laying around. I wrote the same image to it and odroid won't even boot. I a red light but no blue light whatsoever.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby tobetter » Fri Mar 20, 2015 12:10 pm

mulepic wrote:I found a Class 6 laying around. I wrote the same image to it and odroid won't even boot. I a red light but no blue light whatsoever.

Please Class 10.
tobetter
 
Posts: 2081
Joined: Mon Feb 25, 2013 10:55 am
Location: Kitchener, ON, Canada
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 12:26 pm

Which brand you recommend I purchase? Please keep in mind I only paid $35 for the whole computer, I'll be very discouraged if I have to pay even more for the SD.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby tobetter » Fri Mar 20, 2015 12:30 pm

mulepic wrote:Which brand you recommend I purchase? Please keep in mind I only paid $35 for the whole computer, I'll be very discouraged if I have to pay even more for the SD.

As I said, SanDisk UHS-I Class 10 would be best what I found. Please refer the link for the problem of MicroSD compatible issue.
http://odroid.com/dokuwiki/doku.php?id= ... _selection
tobetter
 
Posts: 2081
Joined: Mon Feb 25, 2013 10:55 am
Location: Kitchener, ON, Canada
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: second boot == Read-only file system

Unread postby patoberli » Fri Mar 20, 2015 4:10 pm

It should still work with an old slow card, although I also recommend a fast one :)
After you have booted, can you issue the mount command to show us the current mounted partitions? I guess your distribution is missing a remount rw command.
As you run it headless, here some additional command which might work for your image to add into your boot.ini:
Code: Select all
# Disable VPU (Video decoding engine, Saves RAM!!!)
# 0 = disabled
# 1 = enabled
setenv vpu "0" #as you want to run it headless

# Disable HDMI Output (Again, saves ram!)
# 0 = disabled
# 1 = enabled
setenv hdmioutput "0"

if test "${vpu}" = "0"; then fdt rm /mesonstream; fdt rm /vdec; fdt rm /ppmgr; fi

if test "${hdmioutput}" = "0"; then fdt rm /mesonfb; fi

Sample taken from here: viewtopic.php?f=112&t=8740

You need to alter your bootargs command line a tiny bit for the additional parameters.
-
pato
patoberli
 
Posts: 401
Joined: Mon Feb 23, 2015 6:32 pm
Location: Switzerland
languages_spoken: english, german
ODROIDs: C1 with RTC, Bluetooth 4.0, Wireless stick 4.0

Re: second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 10:18 pm

I added the vpu and hdmi output setenv statements. I couldn't find in the link you proved that shows where to add those to the boot args.

Nonetheless, I the result was the same. Still read-only:

odroid@OdroidC1:~$ sudo su
sudo: unable to resolve host OdroidC1
[sudo] password for odroid:
sudo: unable to open /var/lib/sudo/odroid/0: Read-only file system

and still took 30m before I could log in.


Here's the output of dmesg:
[ 12.180495@0] ***********SDHC_REGS***********
[ 12.184804@0] SDHC_ARGU: 0x00000000
[ 12.188278@0] SDHC_SEND: 0x003404d9
[ 12.191790@0] SDHC_CTRL: 0xe7ffe001
[ 12.195233@0] SDHC_STAT: 0x0008003e
[ 12.198695@0] SDHC_CLKC: 0x0002f010
[ 12.202190@0] SDHC_ADDR: 0x3fc84a00
[ 12.205643@0] SDHC_PDMA: 0x2c43bcf0
[ 12.209121@0] SDHC_MISC: 0xe0000150
[ 12.212608@0] SDHC_DATA: 0x00000000
[ 12.216063@0] SDHC_ICTL: 0x00003866
[ 12.219539@0] SDHC_ISTA: 0x00000239
[ 12.223022@0] SDHC_SRST: 0x00000000
[ 12.226487@0] SDHC_ESTA: 0x00000000
[ 12.229970@0] SDHC_ENHC: 0x00fe0cff
[ 12.233430@0] SDHC_CLK2: 0x0000100f
[ 12.237025@0] mmcblk0: timed out sending r/w cmd command, card status 0xd00
[ 12.243973@0] mmcblk0: not retrying timeout
[ 12.248123@0] end_request: I/O error, dev mmcblk0, sector 527368
[ 12.255299@0] end_request: I/O error, dev mmcblk0, sector 527376
[ 12.261378@0] end_request: I/O error, dev mmcblk0, sector 527384
[ 12.267410@0] end_request: I/O error, dev mmcblk0, sector 527392
[ 12.273500@0] end_request: I/O error, dev mmcblk0, sector 527400
[ 12.279560@0] end_request: I/O error, dev mmcblk0, sector 527408
[ 12.285649@0] end_request: I/O error, dev mmcblk0, sector 527416
[ 12.291731@0] end_request: I/O error, dev mmcblk0, sector 527424
[ 12.297785@0] end_request: I/O error, dev mmcblk0, sector 527432
[ 12.303883@0] end_request: I/O error, dev mmcblk0, sector 527440
[ 12.310019@1] Aborting journal on device mmcblk0p1-8.
[ 17.740853@3] EXT4-fs error (device mmcblk0p1): __ext4_journal_start_sb:62: D etected aborted journal
[ 17.749879@3] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
[ 380.964919@0] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[ 1110.287184@2] config uart_ao_ttyS0:: Character length 8bits/char
[ 1110.306161@2] config uart_ao_ttyS0:: Character length 8bits/char
[ 1110.326146@2] config uart_ao_ttyS0:: Character length 8bits/char
[ 1110.346941@3] config uart_ao_ttyS0:: Character length 8bits/char
[ 1110.907027@3] config uart_ao_ttyS0:: Character length 8bits/char
[ 1110.919102@2] config uart_ao_ttyS0:: Character length 8bits/char


Here's my fdisk output

fdisk -l

Disk /dev/mmcblk0: 7861 MB, 7861174272 bytes
236 heads, 57 sectors/track, 1141 cylinders, total 15353856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x06b7de21

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 3072 1846271 921600 83 Linux
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby rprakash » Fri Mar 20, 2015 10:56 pm

Might need to fsck.ext4 that card.
rprakash
 
Posts: 6
Joined: Tue Dec 23, 2014 10:07 am
languages_spoken: english
ODROIDs: ODROID-C1

Re: second boot == Read-only file system

Unread postby mulepic » Fri Mar 20, 2015 11:10 pm

i tried
fsck -A
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
wheezy: clean, 21395/57600 files, 102567/230400 blocks

I haven't rebooted but it's still read-only.

why would the file system get corrupted only on the 2nd boot every time?
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby rprakash » Fri Mar 20, 2015 11:31 pm

I'm curious, are you getting second boot corruption issues only with the wheezy-minimal image? Or are you also getting second boot corruption with the v1.3 (or brand spankin' new v1.4) Ubuntu image?
rprakash
 
Posts: 6
Joined: Tue Dec 23, 2014 10:07 am
languages_spoken: english
ODROIDs: ODROID-C1

Re: second boot == Read-only file system

Unread postby patoberli » Fri Mar 20, 2015 11:45 pm

This line doesn't look nice:
Code: Select all
[ 12.237025@0] mmcblk0: timed out sending r/w cmd command, card status 0xd00

So either there is some bug/configuration issue or the card is broken/incompatible.

I also recommend to try with the Lubuntu image.
-
pato
patoberli
 
Posts: 401
Joined: Mon Feb 23, 2015 6:32 pm
Location: Switzerland
languages_spoken: english, german
ODROIDs: C1 with RTC, Bluetooth 4.0, Wireless stick 4.0

Re: second boot == Read-only file system

Unread postby tobetter » Sat Mar 21, 2015 12:38 am

@mulepic, are you trying with SanDisk Class 10 or still other media?
tobetter
 
Posts: 2081
Joined: Mon Feb 25, 2013 10:55 am
Location: Kitchener, ON, Canada
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: second boot == Read-only file system

Unread postby mulepic » Sat Mar 21, 2015 12:39 am

rprakash wrote:I'm curious, are you getting second boot corruption issues only with the wheezy-minimal image? Or are you also getting second boot corruption with the v1.3 (or brand spankin' new v1.4) Ubuntu image?



Please send me a link to the image you'd like me to try. There are so many out here and nearly none of them work. This wheezy image is the only one that has worked consistently at least the first boot.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby mulepic » Sat Mar 21, 2015 12:42 am

tobetter wrote:@mulepic, are you trying with SanDisk Class 10 or still other media?


I'm still using Class 4 b/c that is what I have available and I've read others having success w/ a 'slow' card. And I'm having a hard time believing the card has anything to do w/ it b/c it works great every time I write the image to the card and boot it up the first time. Doing a simple reboot cannot possibly have much to do w/ the card.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby mulepic » Sat Mar 21, 2015 12:43 am

patoberli wrote:This line doesn't look nice:
Code: Select all
[ 12.237025@0] mmcblk0: timed out sending r/w cmd command, card status 0xd00

So either there is some bug/configuration issue or the card is broken/incompatible.

I also recommend to try with the Lubuntu image.



Please send me a link to the Lubuntu image that is known to work. I've tried a ton of images and very few even boot up. It's only the minimal wheezy one that has been consistent.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby patoberli » Sat Mar 21, 2015 1:22 am

Here you go: http://odroid.com/dokuwiki/doku.php?id= ... _note_v1.4
Take the "Ubuntu 14.04.2 Image".
-
pato
patoberli
 
Posts: 401
Joined: Mon Feb 23, 2015 6:32 pm
Location: Switzerland
languages_spoken: english, german
ODROIDs: C1 with RTC, Bluetooth 4.0, Wireless stick 4.0

Re: second boot == Read-only file system

Unread postby mulepic » Sat Mar 21, 2015 5:28 am

patoberli wrote:Here you go: http://odroid.com/dokuwiki/doku.php?id= ... _note_v1.4
Take the "Ubuntu 14.04.2 Image".



I installed this image. It boots consistently fast now so that is a welcome relief. But it's still jumping into read-only after the first reboot.

Here is the fsck result:

fsck
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
trusty: recovering journal
trusty contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
trusty: 201606/294912 files (0.5% non-contiguous), 1057265/1167104 blocks

here are some dmesg errors:

[ 196.995738@2] mmcblk0: timed out sending r/w cmd command, card status 0xd00
[ 197.002166@2] mmcblk0: not retrying timeout
[ 197.006318@2] mmc_blk_reset 938 reset error md->reset_done:2 and type:2
[ 197.012932@2] end_request: I/O error, dev mmcblk0, sector 266240
[ 197.018910@2] Buffer I/O error on device mmcblk0p2, logical block 0
[ 197.025182@2] lost page write due to I/O error on mmcblk0p2


I also noticed the MAC addressed changed.

I wish this thing worked.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby mulepic » Sat Mar 21, 2015 6:26 am

I made a discovery. If I do a reboot the system comes back up in read-only mode. If I do a shutdown now then it comes up in r/w.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby patoberli » Sat Mar 21, 2015 8:31 pm

Always shutdown or reboot, newer just unplug it. It is like a PC :)
Not sure if this still works (haven't got my odroid at home) but you could try this:
fsck -f -y -C -V -c -c /dev/mmcblk0p2
You might need to change the /dev/.... to the correct partition.
This should do this:
-f "force" the complete operation to occur even if the flag says the disk is "clean"
-y automatically answer "yes" whenever an error is discovered which asks the user what to do
(needed for unattended automatic fix operation)
-C (note upper case)
present a progress bar showing how much of the operation has been completed
-V (note upper case)
enable "verbose" mode to keep the user apprised of what's happening by printing informative messages
-c -c (no that's not a stutter, it really does need to be entered twice for this particular piece of software - only once would specify the "shortcut" of only reading the existing data from every sector and relying completely on the disk itself to detect any problems, thus missing many flaws)
do a comprehensive surface scan operation by saving the existing contents of each area, writing a test pattern to the area, reading the area and making sure the data read is exactly the same as the pattern that was written, then finally restoring the initial contents of the area

Source: http://www.ckollars.org/disk-surface-scan.html

This will do a surface check of the card (takes a long time!) and also write test patterns and verify those.

Oh and one more thing, open your /media/boot/boot.ini and make sure that the disable-uhs option is set to disable it (your class 4 can't do UHS).
-
pato
patoberli
 
Posts: 401
Joined: Mon Feb 23, 2015 6:32 pm
Location: Switzerland
languages_spoken: english, german
ODROIDs: C1 with RTC, Bluetooth 4.0, Wireless stick 4.0

Re: second boot == Read-only file system

Unread postby mulepic » Sun Mar 22, 2015 12:26 am

I've figured out you CANNOT reboot this thing without it going into read-only mode. The safest way is to do a shutdown -h now and wait till the blue light goes out before unplugging it. Also the long boot times are random so I put: echo $(date) >> /home/odroid/startTime.txt in /etc/rc.local sometimes it would boot in a couple minutes sometimes 10 minutes and this last time it was 1.5hrs! Here's the output:

shutdown -h now @ Sat Mar 21 12:35:49 UTC 2015
rc.local executed @ Sat Mar 21 12:44:29 UTC 2015

shutdown -h now @Sat Mar 21 12:49:22 UTC 2015
rc.local executed @ Sat Mar 21 12:52:04 UTC 2015

shutdown -h now @ Sat Mar 21 12:55:53 UTC 2015
rc.local executed @ Sat Mar 21 12:57:18 UTC 2015

shutdown -h now @ Sat Mar 21 12:59:19 UTC 2015
rc.local executed @ Sat Mar 21 14:35:19 UTC 2015

I'm starting to get the feeling this Odroid C1 just isn't ready for prime time. Maybe as toy/hobby this thing is ok to show cool benchmarks against other micro computers. But it doesn't seem like it's even a minimally viable product.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby robroy » Sun Mar 22, 2015 2:27 am

I've tried a ton of images and very few even boot up.

That isn't typical. It really just seems like you have a bad SD card (class 4?), which is strongly indicated by the I/O errors in your dmesg log. Your card is having trouble holding data.

The Ubuntu 14.04.2 image is so stable for me that I can unplug the C1 without shutting down, and it will repair itself back to normal on the next boot. I own around 100 Wintec brand microSD cards and never have a problem with them. Quality varies quite a bit with the cheaper cards.

Do yourself a favor and borrow a better microSD card from a friend, or better yet, get the eMMC module which is astonishingly fast.

I'm starting to get the feeling this Odroid C1 just isn't ready for prime time. Maybe as toy/hobby this thing is ok to show cool benchmarks against other micro computers. But it doesn't seem like it's even a minimally viable product.

Lol even a Tesla won't run well on flat tires.
Rob Roy, Editor-in-Chief of ODROID Magazine (submit an article | make a donation)
User avatar
robroy
 
Posts: 3349
Joined: Mon Feb 25, 2013 2:29 am
Location: San Francisco, California
languages_spoken: English
ODROIDs: Q2, X, X2, U2, U3, XU-E, XU3, XU4, C1, C1+, C2

Re: second boot == Read-only file system

Unread postby patoberli » Sun Mar 22, 2015 3:52 am

I never had such an issue with my C1. I'm pretty sure your card might have a problem or have some compatibility issues. You use the Windows tool to write the image to the card?
If so, what is the image writing speed? (You see that in the lower left when writing the image)
And after you have written it, can you once verify it? It shouldn't find any error. I'm not sure if it will show you the read speed, but if it does, how fast is it?
-
pato
patoberli
 
Posts: 401
Joined: Mon Feb 23, 2015 6:32 pm
Location: Switzerland
languages_spoken: english, german
ODROIDs: C1 with RTC, Bluetooth 4.0, Wireless stick 4.0

Re: second boot == Read-only file system

Unread postby mulepic » Mon Mar 23, 2015 11:36 am

Honestly this exact card works just fine in my rPi and many others. This variability you guys speak of with cheaper cards has never been an issue for me w/ the rPi. I think the issue w/ the c1 and slower cards has more to do w/ some assumptions being made in the code to read them. But whatever.... I'm not here to defend the rPi, I want the c1 to work.

robroy wrote: I own around 100 Wintec brand microSD cards and never have a problem with them. Quality varies quite a bit with the cheaper cards.


Will a wintec class 10 card work?

robroy wrote:Do yourself a favor and borrow a better microSD card from a friend, or better yet, get the eMMC module which is astonishingly fast.


Spending that much on the eMMC for a $35 computer would solidify this thing as a hobby. I need a reliable viable product I can provide customers. I have enough hobbies.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby robroy » Mon Mar 23, 2015 12:59 pm

Will a wintec class 10 card work?

That's what I use :)
Rob Roy, Editor-in-Chief of ODROID Magazine (submit an article | make a donation)
User avatar
robroy
 
Posts: 3349
Joined: Mon Feb 25, 2013 2:29 am
Location: San Francisco, California
languages_spoken: English
ODROIDs: Q2, X, X2, U2, U3, XU-E, XU3, XU4, C1, C1+, C2

Re: second boot == Read-only file system

Unread postby crashoverride » Mon Mar 23, 2015 1:01 pm

mulepic wrote:Honestly this exact card works just fine in my rPi and many others. This variability you guys speak of with cheaper cards has never been an issue for me w/ the rPi. I think the issue w/ the c1 and slower cards has more to do w/ some assumptions being made in the code to read them. But whatever.... I'm not here to defend the rPi, I want the c1 to work.

The initial revision of Odroid-C1 has known, documented compatibility issues with certain SD cards. This is more likely due to the electrical characteristics of the card than whether its a "cheap card' or a "slow (class 4)" card. Using a recommended SD card such as the Sandisk mentioned does indeed result in reliable operation of the C1. You will also find that connecting a USB serial console cable to the board and a PC alters the electrical characteristics and allows problematic SD cards to be used. A recommended SD cards is not difficult to source (I found them at my local Wal-mart) nor are they prohibitively expensive ($9.00 USD).

Issues such as these are not unique to the Odroid-C1 as the initial revision of RPi also has its own errata and the RPi2 continues that tradition.
http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=99042
http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=101845
http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=103847
http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=102680
crashoverride
 
Posts: 3104
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby mulepic » Wed Mar 25, 2015 1:58 am

I purchased a class 10 card and have the latest ubuntu on it. It seems more stable. reboots don't work so well but 'shutdown -h now' does if you wait till the blue light goes out to unplug the power supply. I'm taking it real slow w/ this thing. Right now I'm battling the RTC. hwclock doesn't find it but if I do: udevadm info -a --name /dev/rtc0

looking at device '/devices/platform/rtc.1/rtc/rtc0':
KERNEL=="rtc0"
SUBSYSTEM=="rtc"
DRIVER==""
ATTR{date}=="2015-03-24"
ATTR{name}=="aml_rtc"
ATTR{time}=="13:21:33"
ATTR{since_epoch}=="1427203293"
ATTR{hctosys}=="1"
ATTR{max_user_freq}=="64"

looking at parent device '/devices/platform/rtc.1':
KERNELS=="rtc.1"
SUBSYSTEMS=="platform"
DRIVERS=="aml_rtc"

looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""


So I know it's working but the OS isn't finding it. But that's another thread. I'll keep this one updated w/ a longer term report.
mulepic
 
Posts: 38
Joined: Fri Mar 13, 2015 3:03 am
languages_spoken: english
ODROIDs: C1

Re: second boot == Read-only file system

Unread postby robroy » Wed Mar 25, 2015 3:22 am

Glad to hear it! As you mentioned, it is important to wait until the blue light is off before unplugging it, since the blue light signals kernel activity.
Rob Roy, Editor-in-Chief of ODROID Magazine (submit an article | make a donation)
User avatar
robroy
 
Posts: 3349
Joined: Mon Feb 25, 2013 2:29 am
Location: San Francisco, California
languages_spoken: English
ODROIDs: Q2, X, X2, U2, U3, XU-E, XU3, XU4, C1, C1+, C2

Re: second boot == Read-only file system

Unread postby presentmind » Tue Apr 21, 2015 3:13 pm

Replace /etc/fstab entry for / with the following format:
UUID=e139ce78-9841-40fe-8823-96a304a09859 / ext4 defaults 0 1

Disables the read only error stuff that makes it impossible to do anything.
presentmind
 
Posts: 4
Joined: Sun Mar 29, 2015 5:12 pm
languages_spoken: english
ODROIDs: ODROID-C1

Re: second boot == Read-only file system

Unread postby dchang0 » Tue Dec 22, 2015 1:50 pm

This is not a thread hijack because I have a nearly-identical situation to the original poster.

I too have been tasked with creating a commercially-viable product using an SBC. I chose the ODROID C1+ due to its onboard RTC and excellent performance.

I have also found that it goes into read-only filesystem mode surprisingly often, although not just on reboots. It can go into read-only filesystem mode just about any time, in my experience. Each time ended in some small catastrophe--in one case I lost the dpkg binary in the middle of an apt-get upgrade--dpkg just totally disappeared. There was no power outage nor any botched shutdown attempt--it was in the middle of a large apt-get upgrade. I could not recover even after copying the dpkg binary back and had to do a wipe and reinstall. Second boots almost always lead to a read-only filesystem.

Now, I have confirmed that it has not happened yet with a Sandisk Extreme microSDXC card while it happens frequently with a Samsung EVO microSDXC card.

Strangely, the Samsung is one of the cards that HardKernel recommended here: http://odroid.com/dokuwiki/doku.php?id= ... _selection

They provided a link to it here: http://www.samsung.com/us/computer/memo ... -MP64DA/AM

I bought it on ODROID's recommendation (since it is much cheaper than the equivalent-size Sandisk Ultra). I'm not saying that this is enough data to recommend pulling the Samsung EVO microSDXC from the recommended list, just noting one data point in the failure column. Note also that this is the C1+ board, which is supposed to have better compatibility with various brands and models of microSD, although the point of selecting a model out of the recommendation list is to avoid any of that.

The surprisingly ungraceful way it fails coupled with my microSD's surprisingly high failure rate has put me on guard against choosing the C1+ for the product design. It's just not resilient enough for our needs. I'm not bashing ODROID, and some ODROID fanbois that may slam me for my observations, but I am here to back up the OP's experience, not to advance any brand favoritism or disfavoritism.

---

To riff on the joke, "not even a Tesla will run well on flat tires," this is more like a car running with only a certain brand and rating of tire, like say a Continental Z-rated tire and not running at all with anything else... Step down to an H-rated tire or switch to anything from Goodyear, and BAM, the car stalls and only kinda runs. Kinda absurd, huh? We're not talking about running optimally in high-performance situations (like picking Z-rated tires for a car going 200mph on a racetrack), we're talking about not running at all, which is a very different problem. I consider a read-only filesystem to be "not running at all," as being able to write sensor data to the filesystem for later processing is a must in our situation.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby odroid » Tue Dec 22, 2015 2:55 pm

Sorry about the Samsung SD card.
I heard most SD card manufacturers changes their SD controller from time to time.
So even the same vendor/model number can show different result.

BTW, did you try the UHS mode via editing the boot.ini file with your EVO card?
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby dchang0 » Tue Dec 22, 2015 3:00 pm

odroid wrote:Sorry about the Samsung SD card.
I heard most SD card manufacturers changes their SD controller from time to time.
So even the same vendor/model number can show different result.

BTW, did you try the UHS mode via editing the boot.ini file with your EVO card?


Hmm. I saw the prior messages about disabling the UHS mode but did not try it. Doesn't doing so dramatically slow down the performance? Just curious--I will give the tip a try anyway, even if it does slow down the C1+. Better to have a usable card than a non-usable one.

Thanks!

Right now I am testing the Samsung card on a laptop to make sure it is not defective and am testing the Sandisk card on the C1+ to see if I can break it. The Sandisk card is holding up well, but I only have about an hour of testing time so far. I fully expect it to work perfectly, though.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby dchang0 » Tue Dec 22, 2015 4:26 pm

Samsung EVO microSDXC card tested fine on the laptop. I wiped it with zeroes and re-imaged it with the factory Ubuntu image. I added the setenv disableuhs "disableuhs" to the /boot/boot.txt file and rebooted, and it hung outright (instead of booting successfully but with read-only filesystem).

The errors are:

EXT4-fs error (device mmcblk0p2): ext4_lookup:1437: inode #823: comm init: deleted inode referenced: 2662403

There are similar errors preceding that one with different inode numbers.

I guess this Samsung card is not going to work, no matter what.

The SanDisk Ultra microSDXC card survived about 2 hours of repeated writes and deletes without errors (a very simplistic test--I wasn't checking for perfect read-backs).

Chalk this one up to an incompatibility with this particular Samsung EVO card.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby odroid » Tue Dec 22, 2015 6:03 pm

I've updated the WiKi page. Sorry for the incomplete information. :(
http://odroid.com/dokuwiki/doku.php?id= ... d_for_boot

BTW, we've used this card over 3~4 months without problem yet.
s_20151222_175631.jpg
(307.86 KiB) Downloaded 3216 times

But it seems to be a SDHC not the SDXC.

We will buy some EVO SDXC cards and try it soon.
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby odroid » Tue Dec 22, 2015 6:12 pm

BTW, can you try this option in the boot.ini file?
It is worth to try to reduce the SD clock frequency to redue the stability/compatibility issue.
Add this to the end of boot.ini, just before the bootm command:

Code: Select all
fdt set /sdhc/sd f_max   <40000000>
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby dchang0 » Tue Dec 22, 2015 6:29 pm

I'll try it and get back to you. Let me wipe and reimage the card.... I'll post back tomorrow at the earliest. Hopefully we can figure this out and put the card back on the recommended list...
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby dchang0 » Tue Dec 22, 2015 7:27 pm

No luck with the fdt set /sdhc/sd f_max <40000000> command just before the bootm.

I got the same type of EXT4-fs errors as before, just with different inode numbers. As a reminder, this is worse than the typical second boot response of "read-only filesystem." In that case, the system usually gets all the way to the graphical desktop.

Did I do this correctly, though?

I edited /boot/boot.txt on Ubuntu (not Android).

One of the lines (not the last one) had the bootm command as part of a setenv string. I inserted the fdt command just before that with a semicolon to terminate that line.

I did not do a reboot--I did a shutdown -h now followed by a power cycle.

Anyway, hope that helps. I will pull the card and wipe and reimage it one more time.

Next time I'll take a screenshot of the boot.txt file edits.

Also, should I be editing the boot.txt file before the very first boot-up (the one where it has the white factory setup screen with the green lettering)? Or is it okay to modify it on the first boot-up after the factory setup?

Finally, one more question--does the fdt command have to be used in conjunction with the disableuhs setting? I did not put the setenv disableuhs "disableuhs" command back in there--I only did the fdt command.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby odroid » Wed Dec 23, 2015 9:58 am

I thought your card issue seemed to be related this thread and I recommended the "fdt set" command.
viewtopic.php?f=115&t=8642#p80607
But my assumption could be wrong.

I'll order 16GB and 32GB of EVO SDXC cards today.
I hope we can test it from early next year.
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby dchang0 » Wed Dec 23, 2015 12:56 pm

Hmm. That other thread seems to have different error messages than in my situation...

I think you'll figure it out quickly enough when you receive some Samsung EVO microSDXC cards soon. The settings for the 32GB model will probably work for my 64GB model.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby odroid » Wed Dec 23, 2015 2:05 pm

Oh.. I will buy a 64GB SDXC card.
16GB and 32GB are SDHC.
Is you card the EVO+ or just the EVO?
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby dchang0 » Wed Dec 23, 2015 2:42 pm

Regular EVO. Thanks for trying out the 64GB SDXC.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby odroid » Tue Dec 29, 2015 2:19 pm

We've received an EVO 64GB SDXC and tested with C1+.
We could observed a similar symptom you met.

After comment out "disableuhs" option line in the boot.ini file, it works well now.
Code: Select all
#setenv disableuhs "disableuhs"


Note that the adding "#" on the disableuhs option line means the system will use the UHS mode.
It will increase the access speed of SD card.
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby dchang0 » Wed Dec 30, 2015 7:53 am

I tried the commenting-out of setenv disableuhs "disableuhs" and it doesn't seem to work for me. The filesystem went read-only again during the first large apt-get upgrade after the initial imaging.

Then, on the next reboot, it produces the same "EXT4-fs errors" I referenced before.

Oh well, guess it doesn't like my Samsung card. I have tested the card on my Macbook and it appears to work fine there. If you have any other ideas that you would like me to test, please let me know.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby odroid » Wed Dec 30, 2015 12:27 pm

Did you also try to add this line just before bootm command with commenting-out the disableuhs option?
Code: Select all
fdt set /sdhc/sd f_max   <40000000>


We ran a tons of dd commands to reproduce the issue. But the file system is still okay.
User avatar
odroid
Site Admin
 
Posts: 25040
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: second boot == Read-only file system

Unread postby dchang0 » Wed Dec 30, 2015 1:23 pm

No, not yet. I am currently testing the Samsung card on my Macbook (copying ~60GB of files onto it, running checksums, etc.)

I'll get back to you in a few days when I get to re-image the card with ODROID Ubuntu and add the fdt line you suggested.
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Re: second boot == Read-only file system

Unread postby dchang0 » Fri Jan 01, 2016 7:19 am

Half-luck.

Trying:

#setenv disableuhs "disableuhs"

AND

fdt set /sdhc/sd f_max <40000000>

makes the system really, really slow, but at least it survives the second reboot without going into read-only filesystem mode.

I did test the Samsung card extensively on my Macbook by filling it up to 55GB and checking the contents. It worked fine, so I am very sure the card is okay.

Oh well, I guess I'll just buy Sandisk cards. Maybe as you say, Samsung changed their controller chip between batches...
dchang0
 
Posts: 100
Joined: Tue Dec 22, 2015 1:29 pm
languages_spoken: english
ODROIDs: C1+, XU4Q

Next

Return to General Chat

Who is online

Users browsing this forum: No registered users and 2 guests