Disturbing error message in Kernel

RAID, Volume, storage pool, hard drive, USB, SSD cache and iSCSI LUN
Locked
User avatar
Spaniard
Posts: 19
Joined: 26 Dec 2020, 00:28

Disturbing error message in Kernel

Post by Spaniard »

Hello,

I found this message in /var/logs/messages

Code: Select all

Mar 21 00:39:38 nas kernel: [39424.722003] ------------[ cut here ]------------
Mar 21 00:39:38 nas kernel: [39424.724034] WARNING: CPU: 1 PID: 10300 at fs/btrfs/transaction.c:322 record_root_in_trans+0xd1/0xe0
Mar 21 00:39:38 nas kernel: [39424.726116] Modules linked in: flashcache(O) aesni_intel crypto_simd cryptd glue_helper atlantic(O) 8812bu 8812au(O)
Mar 21 00:39:38 nas kernel: [39424.728301] CPU: 1 PID: 10300 Comm: mysqld Tainted: G           O    4.13.16 #446
Mar 21 00:39:38 nas kernel: [39424.730480] Hardware name: retsamarret 000-F5221-FBA002-0001/TM-J3355-2G2L, BIOS MAPL0304V17 07/27/2020
Mar 21 00:39:38 nas kernel: [39424.732717] task: ffff968eaf693500 task.stack: ffff9ba8c1aec000
Mar 21 00:39:38 nas kernel: [39424.735002] RIP: 0010:record_root_in_trans+0xd1/0xe0
Mar 21 00:39:38 nas kernel: [39424.737282] RSP: 0018:ffff9ba8c1aefc00 EFLAGS: 00010297
Mar 21 00:39:38 nas kernel: [39424.739579] RAX: ffff968eafa5a578 RBX: ffff968deb035800 RCX: ffff968eb09fc790
Mar 21 00:39:38 nas kernel: [39424.741927] RDX: 0000000000000000 RSI: ffff968deb035800 RDI: ffff968ead821348
Mar 21 00:39:38 nas kernel: [39424.744277] RBP: ffff9ba8c1aefc20 R08: ffff968ebfc9d4e0 R09: ffff968eb9003080
Mar 21 00:39:38 nas kernel: [39424.746612] R10: ffffffffa8f14da0 R11: ffff9ba8c1aefce8 R12: ffff968ead821348
Mar 21 00:39:38 nas kernel: [39424.748946] R13: ffff968eb09fc770 R14: ffff968eb09fc000 R15: ffff968deb035800
Mar 21 00:39:38 nas kernel: [39424.751317] FS:  00007fe098099b00(0000) GS:ffff968ebfc80000(0000) knlGS:0000000000000000
Mar 21 00:39:38 nas kernel: [39424.753724] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 21 00:39:38 nas kernel: [39424.756141] CR2: 00007fe098093ff8 CR3: 00000001eed4e000 CR4: 00000000003406e0
Mar 21 00:39:38 nas kernel: [39424.758608] Call Trace:
Mar 21 00:39:38 nas kernel: [39424.761023]  btrfs_record_root_in_trans+0x4e/0x70
Mar 21 00:39:38 nas kernel: [39424.763430]  start_transaction+0x94/0x400
Mar 21 00:39:38 nas kernel: [39424.765858]  btrfs_join_transaction+0x18/0x20
Mar 21 00:39:38 nas kernel: [39424.768242]  btrfs_dirty_inode+0x44/0xd0
Mar 21 00:39:38 nas kernel: [39424.770566]  btrfs_update_time+0x7a/0xb0
Mar 21 00:39:38 nas kernel: [39424.772879]  touch_atime+0x88/0xb0
Mar 21 00:39:38 nas kernel: [39424.775202]  generic_file_read_iter+0x8ad/0x9a0
Mar 21 00:39:38 nas kernel: [39424.777554]  ? inet_recvmsg+0x37/0x90
Mar 21 00:39:38 nas kernel: [39424.779905]  ? sock_recvmsg+0x38/0x40
Mar 21 00:39:38 nas kernel: [39424.782206]  __vfs_read+0xc7/0x130
Mar 21 00:39:38 nas kernel: [39424.784462]  vfs_read+0x89/0x130
Mar 21 00:39:38 nas kernel: [39424.786739]  SyS_read+0x41/0xa0
Mar 21 00:39:38 nas kernel: [39424.789011]  ? SyS_lseek+0x43/0xa0
Mar 21 00:39:38 nas kernel: [39424.791211]  entry_SYSCALL_64_fastpath+0x17/0x98
Mar 21 00:39:38 nas kernel: [39424.793359] RIP: 0033:0x7fe0a594b908
Mar 21 00:39:38 nas kernel: [39424.795448] RSP: 002b:00007fe0980964e0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Mar 21 00:39:38 nas kernel: [39424.797576] RAX: ffffffffffffffda RBX: 00007fe044005370 RCX: 00007fe0a594b908
Mar 21 00:39:38 nas kernel: [39424.799750] RDX: 0000000000000014 RSI: 00007fe098096630 RDI: 0000000000000030
Mar 21 00:39:38 nas kernel: [39424.801955] RBP: 00007fe0440054f0 R08: 0000000000000000 R09: 0000000000000000
Mar 21 00:39:38 nas kernel: [39424.804141] R10: 0000000000000039 R11: 0000000000000246 R12: 00007fe044005580
Mar 21 00:39:38 nas kernel: [39424.806363] R13: 00007fe044005588 R14: 00005583b61150e8 R15: 0000000000000000
Mar 21 00:39:38 nas kernel: [39424.808627] Code: 5b 41 5c 41 5d 41 5e 5d c3 85 d2 0f 85 65 ff ff ff 31 c0 c3 41 c6 46 78 00 31 c0 5b 41 5c 41 5d 41 5e 5d c3 0f ff e9 67 ff ff ff <0f> ff e9 6d ff ff ff 0f 1f 84 
00 00 00 00 00 55 48 89 e5 41 56 
Mar 21 00:39:38 nas kernel: [39424.813359] ---[ end trace 635bec230ae903d7 ]---
Looks like a problem wih the filesystem. Should I be worried about the integrity of the btrfs (RAID1)?

Is there any check I can perform safely?

Thanks.
Top
User avatar
TMRyan
TerraMaster Team
Posts: 829
Joined: 01 Dec 2020, 11:50
China

Re: Disturbing error message in Kernel

Post by TMRyan »

Hi,
Your memory and file system report errors, what happens after you log in to tOS? When did you create the file system?
You can check whether the hard disk is healthy after backing up the data.
If it only detects the hard disk, such as detecting bad sectors, it will not affect the data on the hard disk.
But the hard disk repair operation will destroy the data, and it is likely to cause permanent data loss.
Please back up the data before proceeding.
How to know exactly whether your hard drive is healthy?viewtopic.php?f=75&t=1125
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement)
Top
User avatar
Spaniard
Posts: 19
Joined: 26 Dec 2020, 00:28

Re: Disturbing error message in Kernel

Post by Spaniard »

I have no problems logging into TOS.

The hard disks are brand new and were fully scanned for bad sectors before formatting. Iron wolf recommended by you. Everything reported as healthy status.

Haven't seen the error anymore. I'll keep an eye on it, as basically you have no more idea than me about its meaning.

Thanks for the reply, anyway.
Top
Locked

Return to “Storage”