hwclock error

hwclock error

Postby taetae » Tue Jan 06, 2015 8:46 am

Happy new year guys!!

Installed the new version at this time,
This alert is normal when I press power led off or on?
  Current System Status: could not update field: __ FILE__, hwclock -w -u, err = 1

but the starting of the engine on or off work
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

hwclock error

Postby Jocko » Tue Jan 06, 2015 9:17 am

Happy new year taetae,

taetae wrote:This alert is normal when I press power led off or on?
Current System Status: could not update field: __ FILE__, hwclock -w -u, err = 1
Absolutely, not !

did you have the same behaviour previously when you set manually the time? (disable the option "Clock from internet time server")
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

hwclock error

Postby taetae » Tue Jan 06, 2015 12:02 pm

is not set

Set Clock from internet time server (NTP)

NTP server 1: 0.it.pool.ntp.org
NTP server 2:


I'm not clear the server inserted
You do not have the required permissions to view the files attached to this post.
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

hwclock error

Postby Jocko » Tue Jan 06, 2015 2:00 pm

Hi taetae,

So keep disable the option "clock from Internet time server" and change manually time.

You should get the same error.
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

hwclock error

Postby Jocko » Tue Jan 06, 2015 2:21 pm

very amazing because in some previous posts, I can read these lines in your dmesg:
Code: Select all
rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
...
rtc-rs5c372 0-0032: setting system clock to 2013-12-31 20:49:53 UTC (1388522993)


So can you check your dmesg?
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

hwclock error

Postby taetae » Tue Jan 06, 2015 2:49 pm

Code: Select all
......
netconsole: network logging started
rtc-rs5c372 0-0032: setting system clock to 2015-01-06 08:41:35 UTC (1420533695)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 0
device-name= sata_mv
fvdw2 disk index after get_sd_name = 4
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sde
sd 0:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sde] 4096-byte physical blocks
sd 0:0:0:0: [sde] Write Protect is off
sd 0:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sde: sde4 < sde5 sde6 sde7 sde8 >
sd 0:0:0:0: [sde] Attached SCSI disk
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata9: failed to resume link (SControl 0)
ata9: SATA link down (SStatus 0 SControl 0)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 1
device-name= sata_mv
fvdw2 disk index after get_sd_name = 3
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sdd
sd 1:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdd] 4096-byte physical blocks
sd 1:0:0:0: [sdd] Write Protect is off
sd 1:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd4 < sdd5 sdd6 sdd7 sdd8 >
sd 1:0:0:0: [sdd] Attached SCSI disk
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 2
device-name= sata_mv
fvdw2 disk index after get_sd_name = 2
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sdc
sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 2:0:0:0: [sdc] 4096-byte physical blocks
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc4 < sdc5 sdc6 sdc7 sdc8 >
sd 2:0:0:0: [sdc] Attached SCSI disk
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 3
device-name= sata_mv
fvdw2 disk index after get_sd_name = 1
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sdb
sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 3:0:0:0: [sdb] 4096-byte physical blocks
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb4 < sdb5 sdb6 sdb7 sdb8 >
sd 3:0:0:0: [sdb] Attached SCSI disk
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
ata5.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access     ATA      WDC WD5000AADS-0 01.0 PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 4
device-name= sata_mv
fvdw2 disk index after get_sd_name = 0
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sda
sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 4:0:0:0: [sda] Attached SCSI disk
ata6: SATA link down (SStatus 0 SControl 300)
ata7: SATA link down (SStatus 0 SControl 300)
ata8: SATA link down (SStatus 0 SControl 300)
ata10: failed to resume link (SControl 0)
ata10: SATA link down (SStatus 0 SControl 0)
ata11: failed to resume link (SControl 0)
ata11: SATA link down (SStatus 0 SControl 0)
ata12: failed to resume link (SControl 0)
ata12: SATA link down (SStatus 0 SControl 0)
ata13: failed to resume link (SControl 0)
ata13: SATA link down (SStatus 0 SControl 0)
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda7): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:71.
Freeing init memory: 120K
EXT3-fs (sda7): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sda7): using internal journal
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda2): warning: checktime reached, running e2fsck is recommended
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): mounted filesystem with ordered data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda5): using internal journal
EXT3-fs (sda5): recovery complete
EXT3-fs (sda5): mounted filesystem with ordered data mode
Adding 514076k swap on /dev/sda3.  Priority:-1 extents:1 across:514076k
NTFS driver 2.1.30 [Flags: R/W MODULE].
fuse init (API version 7.21)
Register Driver 'usblp'
usbcore: registered new interface driver usblp
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
iSCSI Enterprise Target Software - version trunk
iscsi_trgt: Registered io type fileio
iscsi_trgt: Registered io type blockio
iscsi_trgt: Registered io type nullio
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
Linux video capture interface: v2.00
uvcvideo: Unable to create debugfs directory
Register Driver 'uvcvideo'
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
EXT3-fs (sda8): (no)user_xattr options not supported
EXT3-fs (sda8): (no)acl options not supported
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda8): using internal journal
EXT3-fs (sda8): recovery complete
EXT3-fs (sda8): mounted filesystem with ordered data mode
EXT3-fs (sdb8): (no)user_xattr options not supported
EXT3-fs (sdb8): (no)acl options not supported
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb8): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdb8): using internal journal
EXT3-fs (sdb8): recovery complete
EXT3-fs (sdb8): mounted filesystem with ordered data mode
EXT3-fs (sdc8): (no)user_xattr options not supported
EXT3-fs (sdc8): (no)acl options not supported
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdc8): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdc8): using internal journal
EXT3-fs (sdc8): recovery complete
EXT3-fs (sdc8): mounted filesystem with ordered data mode
EXT3-fs (sdd8): (no)user_xattr options not supported
EXT3-fs (sdd8): (no)acl options not supported
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdd8): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sdd8): using internal journal
EXT3-fs (sdd8): recovery complete
EXT3-fs (sdd8): mounted filesystem with ordered data mode
EXT3-fs (sde8): (no)user_xattr options not supported
EXT3-fs (sde8): (no)acl options not supported
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sde8): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sde8): using internal journal
EXT3-fs (sde8): recovery complete
EXT3-fs (sde8): mounted filesystem with ordered data mode
udevd (1038): /proc/1038/oom_adj is deprecated, please use /proc/1038/oom_score_adj instead.
udev: starting version 130
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
warning: `proftpd' uses 32-bit capabilities (legacy support in use)
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: rs5c372_set_datetime: write error
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
rtc-rs5c372 0-0032: can't read registers
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

hwclock error

Postby Jocko » Tue Jan 06, 2015 2:58 pm

So the hardware time seems to be rightly set at booting :scratch

In putty what is the ouput of these commands
Code: Select all
hwclock
hwclock -w -u
echo $?
hwclock
date
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

hwclock error

Postby taetae » Tue Jan 06, 2015 3:55 pm

Code: Select all
/usr/bin$ hwclock
hwclock: RTC_RD_TIME: Input/output error
/usr/bin$ hwclock -w -u
hwclock: RTC_SET_TIME: Input/output error
/usr/bin$ echo $?
0
/usr/bin$ hwclock
hwclock: RTC_RD_TIME: Input/output error
/usr/bin$ data
-sh: data: not found
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

hwclock error

Postby Jocko » Tue Jan 06, 2015 4:11 pm

As you did not post enough lines of the dmesg output, I could not check what rtc device is set.

So post the output of
Code: Select all
ls -Rl /dev/rtc*
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

hwclock error

Postby taetae » Tue Jan 06, 2015 4:18 pm

Code: Select all
/usr/bin$ ls -Rl /dev/rtc*
lrwxrwxrwx  1 root root        9 2014-12-30 21:22 /dev/rtc -> /dev/rtc0
crw-rw----  1 root root 254,   0 2015-01-06 09:42 /dev/rtc0
crw-rw----  1 root root  10, 135 2008-01-03 21:06 /dev/rtc-old

taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Next

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 2 guests