December 6, 201015 yr Hi, and again, another problem with my unraid server. Yesterday i copied data to it and it stopped repsonding at some point. I ran a parity check after reboot which succeeded with around 300 sync errors. I didn't check any further this morning and shut the server down. Now i powered on again and find the same situation, server is running a paritycheck. The Syslog shows some strange entries, maybe someone can elaborate? Dec 6 18:14:44 SPACEHOG kernel: FAT: Filesystem error (dev sda1) Dec 6 18:14:44 SPACEHOG kernel: fat_get_cluster: invalid cluster chain (i_pos 245528) Dec 6 18:14:44 SPACEHOG kernel: File system has been set read-only Dec 6 18:14:48 SPACEHOG kernel: write_file: error 30 opening /boot/config/super.dat Dec 6 18:14:48 SPACEHOG kernel: md: could not write superblock from /boot/config/super.dat Could this be a defective USB Drive? Syslog Cheers...
December 6, 201015 yr Author After googleing around a little, i tried a quick chkdsk on windows and found some inconsistencies which where fixed, up and running again. Seems the fs of the usb stick got damaged due to the 'hardreset' Now im on for the next 10hrs parity sync NARF...
Archived
This topic is now archived and is closed to further replies.