Page 1 of 7

Feature request - cloudshell XU4

Posted: Tue Oct 25, 2016 6:21 am
by johnvick
Hi Fourdee,

Would it be possible to extend the cloudshell display to include the stats from more than two drives? I have a 32 GB eMMC, a 16GB USB flash for backup and a 120 GB SSD but only the former two appear on the display. My coding skills are not up to the job :)

John

Re: Feature request - cloudshell XU4

Posted: Tue Oct 25, 2016 9:28 pm
by Fourdee
johnvick wrote:Hi Fourdee,

Would it be possible to extend the cloudshell display to include the stats from more than two drives? I have a 32 GB eMMC, a 16GB USB flash for backup and a 120 GB SSD but only the former two appear on the display. My coding skills are not up to the job :)

John
Hi John,

Yep, no worries, i'll take a look. Will have to wait until after v135 is released (stacked up), but heres the ticket for tracking: https://github.com/Fourdee/DietPi/issues/582

Re: Feature request - cloudshell XU4

Posted: Wed Oct 26, 2016 12:02 am
by johnvick
Thanks Fourdee look forward to it - the reason for the request is the SSD somehow became disconnected/unmounted and it took a while for me to realise that was the reason for some errors.

Re: Feature request - cloudshell XU4

Posted: Wed Oct 26, 2016 7:23 pm
by Fourdee
johnvick wrote:SSD somehow became disconnected/unmounted
Hi John,

Bizzare, did this occur when the device was powered on, or, after reboot? Might be worth checking dmesg after this occurs again, last entries should give some info, or paste here and i'll take a look.

Re: Feature request - cloudshell XU4

Posted: Thu Oct 27, 2016 11:04 am
by johnvick
Hi Fourdee,

Not really sure when it happened but the three devices I have running DietPi are on 24/7 (Banana M1, Raspberry 3, XU4) and are are only rebooted if necessary. I'll watch for it happening again and check the logs.

John

Re: Feature request - cloudshell XU4

Posted: Tue Nov 01, 2016 7:07 am
by johnvick
Hi Fourdee,

It happened again - the SSD failed. I suspect overheating - the XU4 was simultaneously updating Emby databases on several devices but the files are on the eMMC not the SSD. Anyhow the SSD felt very warm. A software reboot went into emergency mode. Rather than attach a monitor I powered down and left to cool and started again and all is well.

This is from dmesg - it goes on like this so just a selection

[74747.214943] ASC=0x3a ASCQ=0x0
[74747.216052] [c0] sd 1:0:0:0: [sdb] CDB:
[74747.217154] cdb[0]=0x2a: 2a 00 00 00 00 00 00 00 08 00
[74747.219081] [c0] Buffer I/O error on device sdb, logical block 0
[74747.220726] [c0] lost page write due to I/O error on sdb
[74747.251678] [c4] sd 1:0:0:0: [sdb] Device not ready
[74747.252321] [c4] sd 1:0:0:0: [sdb]
[74747.252802] Result: hostbyte=0x00 driverbyte=0x08
[74747.253239] [c4] sd 1:0:0:0: [sdb]
[74747.253646] Sense Key : 0x2 [current]
[74747.254082] [c4] sd 1:0:0:0: [sdb]
[74747.254491] ASC=0x3a ASCQ=0x0
[74747.254911] [c4] sd 1:0:0:0: [sdb] CDB:
[74747.255330] cdb[0]=0x28: 28 00 05 00 00 80 00 00 08 00
[74747.256120] [c5] EXT4-fs error (device sdb): ext4_read_inode_bitmap:175: comm syncthing: Cannot read inode bitmap - block_group = 320, inode_bitmap = 10485776
[74747.257711] [c5] EXT4-fs (sdb): previous I/O error to superblock detected
[74747.259505] [c5] sd 1:0:0:0: [sdb] Device not ready
[74747.260127] [c5] sd 1:0:0:0: [sdb]
[74747.260590] Result: hostbyte=0x00 driverbyte=0x08
[74747.261022] [c5] sd 1:0:0:0: [sdb]
[74747.261447] Sense Key : 0x2 [current]
[74747.261899] [c5] sd 1:0:0:0: [sdb]
[74747.262326] ASC=0x3a ASCQ=0x0
[74747.262795] [c5] sd 1:0:0:0: [sdb] CDB:
[74747.263235] cdb[0]=0x2a: 2a 00 00 00 00 00 00 00 08 00
[74747.263966] [c5] Buffer I/O error on device sdb, logical block 0
[74747.264574] [c5] lost page write due to I/O error on sdb
[74747.266811] [c5] sd 1:0:0:0: [sdb] Device not ready
[74747.267493] [c5] sd 1:0:0:0: [sdb]
[74747.267911] Result: hostbyte=0x00 driverbyte=0x08
[74747.268346] [c5] sd 1:0:0:0: [sdb]
[74747.268759] Sense Key : 0x2 [current]
[74747.269202] [c5] sd 1:0:0:0: [sdb]
[74747.269613] ASC=0x3a ASCQ=0x0
[74747.270041] [c5] sd 1:0:0:0: [sdb] CDB:
[74747.270453] cdb[0]=0x28: 28 00 05 00 00 80 00 00 08 00
[74747.271230] [c6] EXT4-fs error (device sdb): ext4_read_inode_bitmap:175: comm syncthing: Cannot read inode bitmap - block_group = 320, inode_bitmap = 10485776
[74747.272815] [c6] EXT4-fs (sdb): previous I/O error to superblock detected
[74747.274672] [c6] sd 1:0:0:0: [sdb] Device not ready
[74747.275309] [c6] sd 1:0:0:0: [sdb]
[74747.275739] Result: hostbyte=0x00 driverbyte=0x08

Re: Feature request - cloudshell XU4

Posted: Tue Nov 01, 2016 8:41 pm
by Fourdee
Hi John,

Had to reserve v136 for some bug fixes. So nudged your request to v137 and will take a look in the next few days.

HDD temps:
You might be able to read the HDD temps by running:

Code: Select all

apt-get install hddtemp
hddtemp /dev/sdb
It reads from SMART info directly on the drive, so if its not available, possibly the cloudshell USB <> SATA converter doesnt support it. In which case, have to go by touch, or IR temp gun.

Usually, operating temps for SSD's are 0-70'c, is it possible yours is running hotter than this?

Re: Feature request - cloudshell XU4

Posted: Tue Nov 01, 2016 8:44 pm
by Fourdee
Also John,

At the end of:

Code: Select all

/etc/hdparm.conf
You'll find:

Code: Select all

#DietPi external USB drive. Power management settings.
/dev/sda {
        #10 mins
        spindown_time = 120

        #
        apm = 254
}
This is to enable drive spin down (powersaving) after 10 minutes. As your using SSD, try removing that code, reboot then see if the issue reoccurs.

Re: Feature request - cloudshell XU4

Posted: Tue Nov 01, 2016 9:55 pm
by johnvick
Hi Fourdee,

Thanks - the temp sensor does not work. I've removed the section you suggest and will see how it goes.

John

Re: Feature request - cloudshell XU4

Posted: Wed Nov 02, 2016 4:55 pm
by Fourdee
John,

Update: https://github.com/Fourdee/DietPi/issue ... -257908068. Nearly done, i'll let you know how to update your version so you can test.