January 26, 20215 yr I'm getting a corrupt flash drive error. I reinstalled unraid on a new flash drive...same error: Corrupt This usually means your flash drive is corrupted or has dropped offline. The rest of the Unraid GUI will also be affected. Post a new thread in the Unraid forums if this error continues. Seeing the following on the dashboard page: Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 466 Log showing the following: Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30627) failed Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30628) failed Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30629) failed Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30630) failed Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30631) failed Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30632) failed Jan 26 07:13:46 Unraid kernel: FAT-fs (sda1): Directory bread(block 30633) failed Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/media.cfg Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/misc.cfg Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/pictures.cfg Jan 26 07:13:47 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/system.cfg Jan 26 07:13:47 Unraid emhttpd: Starting services... Jan 26 07:13:47 Unraid emhttpd: shcmd (41645): /etc/rc.d/rc.samba restart Jan 26 07:13:47 Unraid root: cp: cannot create regular file '/boot/config': Input/output error Jan 26 07:13:47 Unraid kernel: FAT-fs (sda1): FAT read failed (blocknr 148) Jan 26 07:13:49 Unraid root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: No such file or directory Jan 26 07:13:49 Unraid root: cp: cannot stat '/boot/config/machine-id': No such file or directory Jan 26 07:13:49 Unraid root: Starting Samba: /usr/sbin/smbd -D Jan 26 07:13:49 Unraid root: /usr/sbin/nmbd -D Jan 26 07:13:49 Unraid root: /usr/sbin/winbindd -D Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/media.cfg Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/misc.cfg Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/pictures.cfg Jan 26 07:13:51 Unraid emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/system.cfg Jan 26 07:13:51 Unraid emhttpd: Starting services... Jan 26 07:13:51 Unraid emhttpd: shcmd (41655): /etc/rc.d/rc.samba restart Jan 26 07:13:51 Unraid root: cp: cannot create regular file '/boot/config': Input/output error Jan 26 07:13:51 Unraid kernel: FAT-fs (sda1): FAT read failed (blocknr 148) Jan 26 07:13:53 Unraid root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: No such file or directory Jan 26 07:13:53 Unraid root: cp: cannot stat '/boot/config/machine-id': No such file or directory Jan 26 07:13:53 Unraid root: Starting Samba: /usr/sbin/smbd -D Jan 26 07:13:53 Unraid root: /usr/sbin/nmbd -D Jan 26 07:13:53 Unraid root: /usr/sbin/winbindd -D
January 26, 20215 yr Community Expert The ‘bread’ failures definitely indicate a problem at the hardware level either with the flash drive itself (most likely) or with the port it is plugged into.
January 26, 20215 yr Author It is a USB 3.0 Drive plugged into 2.0 Port. Should I get a 2.0 Drive? Edited January 26, 20215 yr by drradkin
January 26, 20215 yr Community Expert 9 minutes ago, drradkin said: It is a USB 3.0 Drive plugged into 2.0 Port. Should I get a 2.0 Drive? No. The problem, is with USB3 ports on very few MB's, BIOS versions, etc. What happens is that the USB3 port seems to 'lose' the flash drive usually during the boot process.
January 26, 20215 yr Author 51 minutes ago, Frank1940 said: No. The problem, is with USB3 ports on very few MB's, BIOS versions, etc. What happens is that the USB3 port seems to 'lose' the flash drive usually during the boot process. Well, my server only has usb 2.0 ports. Could there be something else causing the problem?
January 26, 20215 yr Community Expert 1 hour ago, drradkin said: I'm getting a corrupt flash drive error. I reinstalled unraid on a new flash drive... Am I correct in assuming that this is the second flash drive you have had fail within a short period of time (say, a month or so)? If this is the case, it could just be the luck of the draw where you got two bad drives... or you using inferior no-name drives... or some docker or plugin is setup to use your flash drive for its temp files.
Archived
This topic is now archived and is closed to further replies.