Jump to content
  • 0

CubieTruck, Jessie(Legacy), Filesystem always cracks..


nemonein
 Share

Question

Hm.. I'll write to you what I have done. Please tell me what's wrong.
 
I have a cubietruck, and I downloaded this one, Legacy Jessie(http://mirror.igorpecovnik.com/Armbian_5.00_Cubietruck_Debian_jessie_3.4.110.zip), and installed it.
 
Install was successful, and worked good. I tried to use nand and SD, and SD only. There were no differences. The result that I want to tell you below, is the same on both cases.

 

.........................

After OS install, I followed this instruction, and I installed several packages.

Instruction : 
  wget -q -O - http://upgrade.armbian.com | bash
Packages : 
  NFS server
  Samba server
  Deluge Daemon(server)

I have a 3TB sata disk with External Sata Interface Case, so I connected it. The external case has it's own power.
By the way, I've been using Volumio 1.5 (https://volumio.org/) for CubieTruck for a long time, and it has worked very good.
 
When I connect the 3TB disk to Cubietruck, it was usually mounted with read only. However I did not mean to do that.
I used this on /etc/fstab,

UUID=xxxx-xxx-xxxx-xxx /mnt/Big_Storage ext4 defaults 0 2

or

/dev/sda1 /mnt/Big_Storage ext4 defaults 0 2

The results are same, sometimes mounted read only, few times mounted ok, and everytime file system cracks.

I have to manully fix the system with fsck.ext4 -y -v -C 0 /dev/sda1.

fsck could fix the problem, but I lost some of my data.

 

The report is like this.

 

3TB_Drive: ***** FILE SYSTEM WAS MODIFIED *****


      234152 inodes used (0.13%, out of 183148544)
       11690 non-contiguous files (5.0%)
          36 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 13/13/14
             Extent depth histogram: 232917/1204
   463810814 blocks used (63.31%, out of 732566272)
           0 bad blocks
         145 large files


      210620 regular files
       23498 directories
           2 character device files
           9 block device files
           3 fifos
       30049 links
           7 symbolic links (3 fast symbolic links)
           4 sockets
------------
      264191 files


I think that Volumio(1.5) is based on Jessie too, but it did not happen everytime. Volumio also sometimes made the file system broken, but not always.

 

I'm trying to install Trusty Legary version....

 

Can you find out what was the problem?

Please help me.

 

Thanks in advance!

 

 

PS.

1. I tried Ubuntu Trusty version, and it works fine, at least for 2 hours, with several reboots and power off/on.

2. I've got this message when it boots. : *** Warning - bad CRC, using default environment.

     But it seems to be working fine. Can I ignore this?

Link to comment
Share on other sites

14 answers to this question

Recommended Posts

  • 0
wget -q -O - http://upgrade.armbian.com | bash

This is not necessary if you have recent images and you have correct kernel. Just use standard commands: apt-get update / apt-get upgrade

 

Try this on your hard drive: (more info on issue)

dd if=/dev/urandom of=testfile bs=1024k count=2048;
md5sum testfile;
md5sum testfile;
md5sum testfile;

Bad CRC on u-boot is normal behavior. Not to worry.

Link to comment
Share on other sites

Help Armbian team helping you!

  • 0

Thank you for your answer.

 

I tried what you asked me to, on Jessie 5.0. But the file system turned to 'Read Only' while writing the testfile.

error writing './testfile': Read-only file system
1103+0 records in
1102+0 records out
1156567040 bytes (1.2GB) copied, 753.8 s, 1.5 MB/s

The file system is corrupted again.

 

I'll try this on Ubuntu Trusty tomorrow.

 

If this is caused by faulty ram, what can I do? And why Jessie has a problem while Ubuntu is ok?

I'll appreciate your help.

Link to comment
Share on other sites

  • 0

I tried, and I've never got into the same situation, like 'error writing './testfile': Read-only file system'.

I succeeded to finish 'dd' and 'md5sum' check several times, and there were no errors.

 

I think file system corrpution occurs not everytime when I reboot or shutdown.

However, sometimes the system could not unmount sata disk, and it may result in the file system crises.

I have this message when I have to check the disk which could not be mounted at the boot time.

--> fsck.ext4: Superblock invalid, trying backup blocks. // 'This Disk' was not cleanly unmounted, check forced.

 

If it happens, it cannot go to the normal booting process, but goes to the 'Emergency mode.'

 

Should I have to manually unmount everytime I want to reboot(or shutdown)?

Link to comment
Share on other sites

  • 0

Could this be a matter to that?

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.
Link to comment
Share on other sites

  • 0

 

Could this be a matter to that?

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

 

That's normal. 

Link to comment
Share on other sites

  • 0

I am running the Cubietruck for long time. My setup is 2 DVB tuners plugged in USB ports and one internal 2,5" 7200 rpm hard drive. I had problems with randomly interrupted tv recording in past. I discovered USB voltage is dropping when system is under load and for second I discovered I need at least 5.5V power adapter to get stable power supply 5V for USB devices. And I am running this board now on 5.7V to reach top allowed voltage value for USB (12V power adapter plus adjustable buck converter designed for 5A current beacuse 3A is not enough when 2.5" hard drive is connected to the board). USB 2.0 specification says voltage must be in range between 4,75 - 5,25V and I think you are running your system on edge of lowest value (Differecies between you and my setup: power adapters 5.5V-5.2V = 0.3V, USB ports 5V-0.3V=4.7V => 4.7 voltage is out of range). 

 

I recommend you to buy USB meter (see links bellow), plug it in separate USB port with your hard drive plugged and try some stress test while watching USB voltage. It is different when system is under load or not or if 2.5" hard drive is attached or it isn't. Therefore you must check USB voltage in your setup.

 

  test examples:

   stress -t 900 -c 1 -m 1 -i 2 -d 2

   hdparm -t /dev/sda

 

USB meters:

1) with low voltage buzzer

2) cheaper but it can do

3) or if you have some experiences you can cut old USB extension cable and attach multimeter for electricians

Link to comment
Share on other sites

  • 0

@technik007_cz Thank you for your concern.

 

I'll try the test you suggested.

My Hdd has been working fine since I last modifed the fstab option.

By the way, I do not use USB port at all. Only SD card is used, and SATA port also. However, because the Sata disk has it's own power source(not coming from the Cubietruck), I don't think it's a matter of power.

 

I'll tell you if there's something suspicious on the disk.

Thanks!

Link to comment
Share on other sites

  • 0

If you have hard drive connected to SATA port it is a different story.

It seems I had some reading problems :-).

 

And whatabout to try btrfs filesystem with file checksumming?

You will need kernel 4.xx but you can set filesystem compression and save some space (it has no sense turn it on media files).

 

It is possible ext4 => btrfs conversion (do that on stable pc).

And after you finish conversion you can do scrub of whole system on you Cubietruck.

Scrubbing of 3TB hard drive is very time consuming process but if someting is wrong with your setup (board,power source,cables...)

this process should end with some errors.

 

What do you thing about it?

Link to comment
Share on other sites

  • 0

Thank you technik007_cz, I really appreciate it.

It's been working with no problem. So I do not want to do anything for now.

However, if there's something wrong on the system again, I'll try what you have suggested.

I've never thought about changing the file system format, which is intriguing, because I never tried btrfs before.

 

Thanks again!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...