Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by nemonein

  1. Thank you for your reply. I use the Cubietruck as, an Mpd Server (using SPDIF) a File Server (both NFS and Samba) a Torrent Server (using deluged) with a Sata HDD(3TB) and Gigabit ethernet cable attached. It's on 24/7. It's acting normal. As far as I remember, it never went down(even during the last summer), unless there was a Sata disk issue, but I think it's fine right now. I'm using a platic case for CubieTruck, and also using a heat sink for A20 chip. Because I use a heat sink, I could only guess that how hot the CPU is. When the sensor says it's 77~79 degrees, I touched the heat sink, and it was, well, touchable? I mean not that hot. But without a heat sink, I'm sure it's very hot. Actually, I used a power adapter with 5.2V(I checked it with a voltage tester, it was 5.4~5.5v), 2A. Under this adapter, the temperature of the CPU was up to 79 degrees. I changed it to 5V(The tester's result was the same. 4.9~5.0V) adapter, the temperature went down around 60~73. With 5V adapter, and barely in 'nude' mode(no case/enclosure), the temperature was 57~62. What should I do? Any suggestions are welcome. Thanks!
  2. Hi. I'm using Armbian Jessie(Legacy) on Cubietruck. My cubietruck's cpu temp. is aruond 77~79. Is it too hot? If it is, how can I lower the temperature? One more thing to ask. How can I see the temperature? I could see it when I log in to Armbian, but how can I do it manually? Could this be one of the method? cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/temp1_input Thank you for reading.
  3. My board's power is 5.2V, 2A. External HDD has it's own power source. Since I changed the fstab option, there have been no problems at all just for now.
  4. I've change the fstab option to "rw,data=journal,commit=1,errors=remount-ro", also replace the cable with a new one. I'll test with this circumstances for a while, and post the result.
  5. I upgraded from Wheezy to Jessie by editing the source.list file. (# sed -i 's/wheezy/jessie/g' /etc/apt/sources.list) The upgrade was successful, and the system works fine. Mpd volume is also quite good. (Not quiet.) I did not modify anything but /etc/mpd.conf. There must be miss settings on Jessie, regarding Cubietruck's spdif output.
  6. I tried with the Wheezy Version(Armbian_5.00_Cubietruck_Debian_wheezy_3.4.110.zip), and there was no volume issue. I hope you find out what causes this in Jessie.
  7. 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.
  8. Hello. I'm using CubieTruck, Armbian 5.00 (Armbian_5.00_Cubietruck_Debian_jessie_3.4.110.zip). I installed and setup mpd, using spdif port and Tos-Link cable. Everything went well except the volume. The volume is too low to listen to the music. I can hear that, if I turn up the external amp's volume, but even I do that to the maxium, it still is very quiet. What can I do? Please give me clue. Thanks in advance~!
  9. 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)?
  10. Thank you for your concern. I did try with 2 drives. The results are the same. I will try with various circumstances, and ask you again.
  11. 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.
  12. 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?
  13. Thank you guys, it worked. But.. I found other serious problem, and I'd like to talk to you in other topic. See you in a bit.
  14. Hello. Thank you for your great effort. I'm using CubieTruck, and I installed Debian Jessie(Armbian, of course), and make it boot from Nand. It was successful. However, if I insert sd card into the slot, CubieTruck won't boot. Isn't it possible to boot from nand while sd card is inserted? I want mount the SD card to /home directory. (Using USB slot works.) Thanks in advance!
  • Create New...