Alexandr Kuznetsov

Good afternoon dear experts. I have a problem on my Orange pi plus 2. My hard drive(WD Red WD10JFCX, 1Тб, HDD, SATA III, 2.5") is periodically switched-off (/dev/sda1). in ravines I have: Sep 28 10:48:37 PM dvr kernel: [1678371.474389] ehci_irq: highspeed device disconnect Sep 28 10:48:37 PM dvr kernel: [1678371.474593] usb 3-1: USB disconnect, device number 2 Sep 28 10:48:37 PM dvr kernel: [1678371.479539] Buffer I/O error on device sda1, logical block 76682192 Sep 28 10:48:37 PM dvr kernel: [1678371.479581] Buffer I/O error on device sda1, logical block 76682193 Sep 28 10:48:37 PM dvr kernel: [1678371.479609] Buffer I/O error on device sda1, logical block 76682194 Sep 28 10:48:37 PM dvr kernel: [1678371.479636] Buffer I/O error on device sda1, logical block 76682195 Sep 28 10:48:37 PM dvr kernel: [1678371.479663] Buffer I/O error on device sda1, logical block 76682196 Sep 28 10:48:37 PM dvr kernel: [1678371.479690] Buffer I/O error on device sda1, logical block 76682197 Sep 28 10:48:37 PM dvr kernel: [1678371.479716] Buffer I/O error on device sda1, logical block 76682198 and Sep 28 22:48:37 dvr kernel: [1678371.474593] usb 3-1: USB disconnect, device number 2 Sep 28 22:48:37 dvr kernel: [1678371.480406] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 1900544 size 126976 starting block 76682478) Sep 28 22:48:37 dvr kernel: [1678371.481086] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2023424 size 73728 starting block 76682496) Sep 28 22:48:37 dvr kernel: [1678371.482205] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2097152 size 126976 starting block 76683038) Sep 28 22:48:37 dvr kernel: [1678371.483168] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2220032 size 126976 starting block 76683068) Sep 28 22:48:37 dvr kernel: [1678371.484271] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2342912 size 126976 starting block 76683098) Sep 28 22:48:37 dvr kernel: [1678371.485228] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2465792 size 126976 starting block 76683128) Sep 28 22:48:37 dvr kernel: [1678371.485968] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2588672 size 126976 starting block 76683158) Sep 28 22:48:37 dvr kernel: [1678371.485968] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2711552 size 126976 starting block 76683188) Sep 28 22:48:37 dvr kernel: [1678371.485968] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2834432 size 126976 starting block 76683218) Sep 28 22:48:37 dvr kernel: [1678371.485968] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368747 (offset 2957312 size 61440 starting block 76683233) Sep 28 22:48:37 dvr kernel: [1678371.492144] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 860160 size 110592 starting block 76681453) Sep 28 22:48:37 dvr kernel: [1678371.493059] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 737280 size 126976 starting block 76681426) Sep 28 22:48:37 dvr kernel: [1678371.493944] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 614400 size 126976 starting block 76681396) Sep 28 22:48:37 dvr kernel: [1678371.494826] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 491520 size 126976 starting block 76681366) Sep 28 22:48:37 dvr kernel: [1678371.495733] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 368640 size 126976 starting block 76681336) Sep 28 22:48:37 dvr kernel: [1678371.496700] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 245760 size 126976 starting block 76681306) Sep 28 22:48:37 dvr kernel: [1678371.497596] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 122880 size 126976 starting block 76681276) Sep 28 22:48:37 dvr kernel: [1678371.498622] EXT4-fs warning (device sda1): ext4_end_bio:249: I/O error writing to inode 55368748 (offset 0 size 126976 starting block 76681246) Sep 28 22:48:37 dvr kernel: [1678371.499036] JBD2: Detected IO errors while flushing file data on sda1-8 Sep 28 22:48:40 dvr kernel: [1678373.960205] usb 3-1: new high-speed USB device number 3 using sunxi-ehci Sep 28 22:48:40 dvr kernel: [1678374.114545] scsi1 : usb-storage 3-1:1.0 Sep 28 22:48:40 dvr mtp-probe: checking bus 3, device 3: "/sys/devices/platform/sunxi-ehci.4/usb3/3-1" Sep 28 22:48:40 dvr mtp-probe: bus: 3, device: 3 was not an MTP device Sep 28 22:48:41 dvr kernel: [1678375.112846] scsi 1:0:0:0: Direct-Access WDC WD10 JFCX-68N6GN0 0009 PQ: 0 ANSI: 0 Sep 28 22:48:41 dvr kernel: [1678375.115159] sd 1:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/931 GiB) Sep 28 22:48:41 dvr kernel: [1678375.116283] sd 1:0:0:0: [sdb] Write Protect is off Sep 28 22:48:41 dvr kernel: [1678375.155871] sdb: sdb1 Sep 28 22:48:41 dvr kernel: [1678375.160752] sd 1:0:0:0: [sdb] Attached SCSI disk Sep 29 06:42:28 dvr rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="1415" x-info="http://www.rsyslog.com"] rsyslogd was HUPed Sep 29 06:42:29 dvr rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="1415" x-info="http://www.rsyslog.com"] rsyslogd was HUPed Sep 29 22:50:02 dvr kernel: [1764856.800097] EXT4-fs (sda1): error count since last fsck: 5 Sep 29 22:50:02 dvr kernel: [1764856.800132] EXT4-fs (sda1): initial error at time 1475092117: ext4_journal_start_sb:328 Sep 29 22:50:02 dvr kernel: [1764856.800164] EXT4-fs (sda1): last error at time 1475125069: ext4_find_entry:941: inode 55312385 Orange pi plus 2 works 24 hours a day, 7 days a week, on the hard drive constant record of small videos of files has to be made. Help to solve a problem please.

Thanks a lot, everything has turned out. I had only one question: whether this method of cloning is correct whether something will break? Also I apologize that not on a subject, but I am tormented by a question why after performance of nand-sata-install the root section is in the fstab file on / dev/mmcblk1p1 /dev/mmcblk1p1/ext4 defaults, noatime, nodiratime, commit=600, errors=remount-ro 0 1 , judging by fdisk - l the root section has to be / dev/mmcblk0p1 / dev/mmcblk0p1 2048 30469567 30467520 14.5G 83 Linux

Also doesn't want to open. sdcard after record of an image doesn't open, I see the section, but gives an error message of reading the section.

I haven't absolutely understood what next to do? how to me to transfer an image?

My new sdcard is a little less than old therefore at record of an image on the new card which has been created so: dd if=/dev/sdd of=/home/user/imagename.img, the message is given: dd: write error "/dev/sdd": On the device there is no empty seat left 7563265+0 records are received 7563264+0 records are sent 15489564672 bytes (15 GB), 4249,41 c, 3,6 MB/c are copied

Dear gurus good afternoon. I ask for help because itself I don't understand any more what not so I do. I should make a clone of my sdcard, but nothing leaves. I tried so: I find the sdcard fdisk - l I create the empty file of an image dd if=/dev/zero of=armbian.img bs=2048 count=1402144 also I add him to loop losetup/dev/loop0 armbian.img now I clone the sdcard in loop the device dd if=/dev/sdd of=/dev/loop0 now I write down a half-scientific image on new sdcard dd bs=2048 if=armbian.img of=/dev/sdd As a result my sdcard doesn't seem on linux and I can't mount sections and loading doesn't happen to sdcard. Prompt please in what a mistake and as to me to make a clone of the sdcard. I am very grateful.

Thanks a lot

if now the system is installed on sdcard, then having chosen option boot from SD, system on SATA/USB, the same sdcard for storage of the loader will be used? I will be able to transfer then the loader to sdcard of the smaller size? if I am able, then how then to transfer the loader?

how to make full transfer, to leave loading only from sata without emmc/nand or sdcard?

Good afternoon dear gurus. help to transfer please system with sdcard to sata hdd in OrangePI +2. Debian jessy and additional software is established. what needs to be made? if it is possible, then on steps. the point is that I want to refuse completely loading with sdcard and emmc. To be loaded only with sata hdd. Thanks in advance.