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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

flash drive is read only

CapnBax
in Hardware

Featured Replies

Hi,

First I want to say what an outsiding job you guys do! I can usually find what I need here. But..

My flash drive seems to be read only. When I try to load apcupsd from unmenu it knocks out my flash!

When I open flash on the network, it says that this file is empty!

Here is my syslog after boot.

Next post will have syslog after flash goes away.

  • Quote

    These messages in your syslog show that your FAT file-system on the flash drive is corrupted.  The third line shows how the file-system has been set to a read-only" state to prevent any further corruption. It says: " File system has been set read-only "

    Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel:     File system has been set read-only
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)
Oct 21 09:54:08 Tower kernel: FAT: Filesystem panic (dev sde1)
Oct 21 09:54:08 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 1808734)

     

    Easiest way to fix this is to stop the unRAID array, move the flash drive to a windows machine and then run either chkdisk or scandisk on it.  (or right click on it and run the repair utility on it that way)

     

    Don't forget to "safely eject" the flash drive from the windows PC before you move it back to the unRAID server, otherwise, it is possible to re-introduce corruption by not having the fixes properly written to the device.

    Joe L.

  • Quote
    • Author

    OK,

    I have 2 Sanddisk micros. This happens with both of them.

    I formated and loaded 4.5-beta 7.

    I then bootup unraid.

    when every I try to write to the flash, wheather manually thru the network or thru unmenu it corrupts the flash and the flash folder says it's empty.

    Here is the last syslog.

    Thanks for the help!

    Bax

  • Quote

    OK,

    I have 2 Sanddisk micros. This happens with both of them.

    I formated and loaded 4.5-beta 7.

    I then bootup unraid.

    when every I try to write to the flash, wheather manually thru the network or thru unmenu it corrupts the flash and the flash folder says it's empty.

    Here is the last syslog.

    Thanks for the help!

    Bax

    Looking closer, I see a usb controller error, followed by the inability to read the flash drive.

     

    I'd try a different port USB first.

    Oct 21 11:55:39 Tower kernel: usb 1-2: reset high speed USB device using ehci_hcd and address 3

    Oct 21 11:55:39 Tower kernel: usb 1-2: device descriptor read/64, error -71

    Oct 21 11:55:39 Tower kernel: usb 1-2: device descriptor read/64, error -71

    Oct 21 11:55:39 Tower kernel: usb 1-2: reset high speed USB device using ehci_hcd and address 3

    Oct 21 11:55:39 Tower kernel: usb 1-2: device descriptor read/64, error -71

    Oct 21 11:55:39 Tower kernel: usb 1-2: device descriptor read/64, error -71

    Oct 21 11:55:40 Tower kernel: usb 1-2: reset high speed USB device using ehci_hcd and address 3

    Oct 21 11:55:40 Tower kernel: usb 1-2: device not accepting address 3, error -71

    Oct 21 11:55:40 Tower kernel: usb 1-2: reset high speed USB device using ehci_hcd and address 3

    Oct 21 11:55:41 Tower kernel: usb 1-2: device not accepting address 3, error -71

    Oct 21 11:55:41 Tower kernel: sd 0:0:0:0: [sde] Unhandled error code

    Oct 21 11:55:41 Tower kernel: sd 0:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00

    Oct 21 11:55:41 Tower kernel: end_request: I/O error, dev sde, sector 113129

    Oct 21 11:55:41 Tower kernel: sd 0:0:0:0: [sde] Unhandled error code

    Oct 21 11:55:41 Tower kernel: sd 0:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00

    Oct 21 11:55:41 Tower kernel: end_request: I/O error, dev sde, sector 64

    Oct 21 11:55:41 Tower kernel: Buffer I/O error on device sde1, logical block 1

    Oct 21 11:55:41 Tower kernel: lost page write due to I/O error on sde1

  • Quote
    • Author

    Thanks Joe L. !

     

    I used another usb port and everything is working now.

     

    Bax

  • Quote

    • Archived

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

    Go to topic listing

    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.