Skip to content

Commit

Permalink
Another FAT fix
Browse files Browse the repository at this point in the history
  • Loading branch information
@dkulp
dkulp committed Nov 12, 2018
1 parent 737b81e commit dc06c5a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion scripts/copy_settings_to_storage.sh
View file
Expand Up @@ -11,7 +11,7 @@ elif [[ "$FSTYPE" =~ "ext4" ]]; then
mount -t ext4 -o noatime,nodiratime,nofail /dev/$DEVICE /tmp/smnt
elif [[ "$FSTYPE" =~ "FAT" ]]; then
EXTRA_ARGS="--no-perms"
mount -t ext4 -o noatime,nodiratime,exec,nofail,flush,uid=500,gid=500 /dev/$DEVICE /tmp/smnt
mount -t auto -o noatime,nodiratime,exec,nofail,flush,uid=500,gid=500 /dev/$DEVICE /tmp/smnt
elif [[ "$FSTYPE" =~ "DOS" ]]; then
EXTRA_ARGS="--no-perms"
mount -t auto -o noatime,nodiratime,exec,nofail,flush,uid=500,gid=500 /dev/$DEVICE /tmp/smnt
Expand Down

3 comments on commit dc06c5a

@JonB256
Copy link

@JonB256 JonB256 commented on dc06c5a Nov 12, 2018 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trying now with 2.4-master - FAT32
still copying but no error messages at the top. good sign

Well, it did give me a successful transfer of important settings needed for boot.
But, only one FSEQ file was transferred intact. The second was partial, then it aborted.

But it is booting perfectly with sda1 as the Settings location.

@JonB256
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, lets back that up.
I tried to manually add the 4 files that didn't transfer.
That didn't go well. They started to transfer (green bars moving nicely) then stopped and stayed stopped.
I cancelled the transfer.
Then rebooted. On reboot, it did not load any settings (DNS name or IP data)
But, cycle the power and it came back normally.
Tried loading files again (just one this time) and it got 1/2 way and just quit.
Same behavior on reboot.
The FAT format is not behaving.

@JonB256
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And the above failure may be just due to a bad Flash Drive. (8gb SanDisk)
Put in another drive (PNY 32gb) and it went perfectly and much faster.
Uploaded a new fseq file to sda1, no problem, normal transfer speed.

I may trash that drive or try a "long format" instead of quick.

Please sign in to comment.