Problems mounting and accessing web gui (FAT-fs (sda1): Volume was not properly)

[espenandre]

Hello,

I'm getting tired of fixing my unRaid server now. Today I noticed that Plex couldn't find my server, so I tried logging in on the web gui, but I got a "connection refused" in the browser.

I captured the syslog, and rebooted using shutdown now.

 

The syslog is attached. I did notice one line there:

FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

 

Any thoughts? After reboot, the web gui is still not working and when I try to access my server from a client computer, I get in on the server, but no shares are visible.

Putty still works, as it also did before the first reboot.

syslog.txt

[espenandre]

Ok, so I tried reiserfsck on the mentioned sda1, and got this (attached is the newest screenshot I have of my configuration):

 

reiserfsck --check /dev/sda1

reiserfsck 3.6.24

 

Will read-only check consistency of the filesystem on /dev/sda1

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

 

reiserfs_open: the reiserfs superblock cannot be found on /dev/sda1.

Failed to open the filesystem.

 

If the partition table has not been changed, and the partition is

valid  and  it really  contains  a reiserfs  partition,  then the

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

[espenandre]

For some reason, I can now suddenly access the web gui again. All drives are unassigned, but luckily I have a screenshot, so it should be easy to fix it again.

 

Still, I wonder what really happened, and how I can, if possible, avoid it in the future.

 

Edit:

When I have selected the parity disk and two additional disk to slots in the gui, the rest of the options in the remaining slots are greyed out. Anyone know why?

[espenandre]

Ok, hopefully this is my last post in this thread!

 

After a reboot via the web gui, everything was back to normal again!!

[espenandre]

This morning, the server was down again. During the night it had been running a parity check, and this is an excerpt from the syslog:

 

Nov 20 04:37:20 Bart kernel: Sense Key : 0xb [current] [descriptor]
Nov 20 04:37:20 Bart kernel: Descriptor sense data with sense descriptors (in hex):
Nov 20 04:37:20 Bart kernel:        72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 d8 d8 
Nov 20 04:37:20 Bart kernel:        d8 d8 d8 d8 
Nov 20 04:37:20 Bart kernel: sd 8:0:0:0: [sdg]  
Nov 20 04:37:20 Bart kernel: ASC=0x0 ASCQ=0x0
Nov 20 04:37:20 Bart kernel: sd 8:0:0:0: [sdg] CDB: 
Nov 20 04:37:20 Bart kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 18 30 7d e0 00 00 00 08 00 00
Nov 20 04:37:20 Bart kernel: end_request: I/O error, dev sdg, sector 405831136
Nov 20 04:37:20 Bart kernel: end_request: I/O error, dev sdg, sector 405831136
Nov 20 04:37:20 Bart kernel: ata9: EH complete
Nov 20 04:37:50 Bart kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Nov 20 04:37:50 Bart kernel: ata9.00: failed command: WRITE DMA EXT
Nov 20 04:37:50 Bart kernel: ata9.00: cmd 35/00:08:d8:7d:30/00:00:18:00:00/e0 tag 0 dma 4096 out
Nov 20 04:37:50 Bart kernel:         res 40/00:d8:d8:d8:d8/d8:d8:d8:d8:d8/d8 Emask 0x4 (timeout)
Nov 20 04:37:50 Bart kernel: ata9.00: status: { DRDY }
Nov 20 04:37:50 Bart kernel: ata9: hard resetting link
Nov 20 04:37:50 Bart kernel: ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 20 04:37:51 Bart kernel: ata9.00: configured for UDMA/33
Nov 20 04:37:51 Bart kernel: ata9: EH complete
Nov 20 04:38:21 Bart kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Nov 20 04:38:21 Bart kernel: ata9.00: failed command: WRITE DMA EXT
Nov 20 04:38:21 Bart kernel: ata9.00: cmd 35/00:08:d8:7d:30/00:00:18:00:00/e0 tag 0 dma 4096 out
Nov 20 04:38:21 Bart kernel:         res 40/00:d8:d8:d8:d8/d8:d8:d8:d8:d8/d8 Emask 0x4 (timeout)

 

There are multiple lines similar to this in the log. Any ideas?

sdg is my cache disk, recently formatted with btrfs. Should I replace it?

[itimpi]

I would first carefully check the cabling in case that is the issue (it is amongst the commonest).

 

You might want to also get a SMART report for the drive and post the results here to see if it shows anything.

[dgaschk]

Run check disk on the flash in a PC or Mac. Do not shutdown using the command line. Only shutdown using the GUI.