Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Is my UnRaid flash drive failing?

Featured Replies

  • Community Expert

Hello - just got his error on my boot USB drive - I would appreciate some help in understanding what the 2 errors below mean. Thanks in advance.

May 20 21:53:19 Tower kernel: print_req_error: I/O error, dev sda, sector 3943936
May 21 21:08:58 Tower kernel: FAT-fs (sda): error, fat_free_clusters: deleting FAT entry beyond EOF

Full log below:

May 20 21:52:52 Tower kernel: sd 0:0:0:0: [sda] 3944448 512-byte logical blocks: (2.02 GB/1.88 GiB)
May 20 21:52:52 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off
May 20 21:52:52 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
May 20 21:52:52 Tower kernel: sd 0:0:0:0: [sda] No Caching mode page found
May 20 21:52:52 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
May 20 21:52:52 Tower kernel: sda:
May 20 21:52:52 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
May 20 21:52:52 Tower kernel: sda:
May 20 21:53:18 Tower emhttpd: JetFlash_Transcend_2GB_H6UH5G0U-0:0 (sda) 512 3944448
May 20 21:53:18 Tower emhttpd: import flash device: sda
May 20 21:53:19 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:19 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
May 20 21:53:19 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x6 [current]
May 20 21:53:19 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x28 ASCQ=0x0
May 20 21:53:19 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 3c 2e 00 00 00 70 00
May 20 21:53:19 Tower kernel: print_req_error: I/O error, dev sda, sector 3943936
May 20 21:53:19 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:25 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:25 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:31 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:32 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:38 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:38 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:44 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:53:44 Tower kernel: VFS: busy inodes on changed media or resized disk sda
May 20 21:55:52 Tower emhttpd: JetFlash_Transcend_2GB_H6UH5G0U-0:0 (sda) 512 3944448
May 20 21:55:52 Tower emhttpd: import flash device: sda
May 20 21:56:06 Tower emhttpd: JetFlash_Transcend_2GB_H6UH5G0U-0:0 (sda) 512 3944448
May 20 21:56:06 Tower emhttpd: import flash device: sda
May 20 21:56:27 Tower emhttpd: JetFlash_Transcend_2GB_H6UH5G0U-0:0 (sda) 512 3944448
May 20 21:56:27 Tower emhttpd: import flash device: sda
May 20 21:57:41 Tower emhttpd: JetFlash_Transcend_2GB_H6UH5G0U-0:0 (sda) 512 3944448
May 20 21:57:42 Tower emhttpd: import flash device: sda
May 21 21:08:58 Tower kernel: FAT-fs (sda): error, fat_free_clusters: deleting FAT entry beyond EOF
May 21 21:08:58 Tower kernel: FAT-fs (sda): Filesystem has been set read-only

 

Edited by abhi.ko

  • Community Expert

The messages certainly mean that the system is having troubles reading the USB stick :(   Do you have a backup backup of the USB stick?   Are you using a USB2 port (prefered over US3 as they seem to be more reliable)?

 

You might want to plug the USB stick into a PC/Mac to check it can be read.    If you do not have a backup then try and make one at this point.    The ‘config’ folder and its contents are the important information as it contains your license key file and all your settings.    It might be a good idea to run the USB Creator tool to rewrite the USB stick contents and then copy the saved ‘config’ folder replacing the contente of the one the USB Creator tool puts on the USB stick.

  • Author
  • Community Expert
13 hours ago, itimpi said:

The messages certainly mean that the system is having troubles reading the USB stick :(   Do you have a backup backup of the USB stick?   Are you using a USB2 port (prefered over US3 as they seem to be more reliable)?

 

You might want to plug the USB stick into a PC/Mac to check it can be read.    If you do not have a backup then try and make one at this point.    The ‘config’ folder and its contents are the important information as it contains your license key file and all your settings.    It might be a good idea to run the USB Creator tool to rewrite the USB stick contents and then copy the saved ‘config’ folder replacing the contente of the one the USB Creator tool puts on the USB stick.

Thanks.

 

Yes I created a backup now. The drive is working and showing green - 

2a4poxc.jpg

 

Should I replace it or continue using it?

 

  • Community Expert
16 minutes ago, abhi.ko said:

Thanks.

 

Yes I created a backup now. The drive is working and showing green - 

2a4poxc.jpg

 

Should I replace it or continue using it?

 

It is really up to you.    During normal use there is very little writing to the USB stick so it is probably fine, but keep an eye on it.    It is only when doing upgrades To Unraid that any significant number of writes occur.

 

There seem to be a significant number of people who have experienced a similar set of issues when doing the 6.7 upgrade.    It make me wonder whether there was subtle change at the Linux kernel level that have increased the chance of large writes not always succeeding.   However that is just some supposition as many (including myself) upgraded without any such problems.

  • Author
  • Community Expert
4 hours ago, itimpi said:

It is really up to you.    During normal use there is very little writing to the USB stick so it is probably fine, but keep an eye on it.    It is only when doing upgrades To Unraid that any significant number of writes occur.

 

There seem to be a significant number of people who have experienced a similar set of issues when doing the 6.7 upgrade.    It make me wonder whether there was subtle change at the Linux kernel level that have increased the chance of large writes not always succeeding.   However that is just some supposition as many (including myself) upgraded without any such problems.

Interesting. My error popped up a few weeks after the upgrade finished successfully, so not sure if its related to the upgrade. It actually popped up when I was trying to upgrade a plugin, not sure why none of the plugins or anything else are on the flash drive. so not sure if that was a coincidence.

 

I guess I will get/find a new one and get ready to replace.

  • Community Expert
5 hours ago, abhi.ko said:

 

I guess I will get/find a new one and get ready to replace.

If you decide to buy a new one as a replacement go for a USB2 drive rather than a USB3 ones.    As well as being cheaper a USB2 drive tends to be more reliable and Unraid gains no performance advantage from USB3 as it runs from RAM after initial boot.

  • Author
  • Community Expert
10 hours ago, itimpi said:

If you decide to buy a new one as a replacement go for a USB2 drive rather than a USB3 ones.    As well as being cheaper a USB2 drive tends to be more reliable and Unraid gains no performance advantage from USB3 as it runs from RAM after initial boot.

Thanks - will do! 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.