Hello I have recently upgraded a disk in my array (well 2 actually) the first one I upgraded went smooth with no issue. However the second disk I upgraded is having an issue. I upgraded it, let unraid rebuild and make a valid config of the array (everything fine and dandy) After everything was valid. I spun down the disks, and stopped the array, and then did a clean power down, as I like to make sure everything is good when it is powered up.

 

When I powered on the array, it again thought the disk was new (upgraded) and did the whole process over again. So I let it. After the process (which takes 1200 minutes) finished I then again stopped and did a clean power down. And again it thinks it is a new disk. It is frustrating.

 

So I turn to anyone that may have a solution to this issue. Thank you

It sounds like your flash drive was mounted read-only because of detected file-system-corruption.  However, since you did not attach a syslog for analysis, that is just my best guess.

 

Since it is not writable, the new status cannot be saved, thus you are in a loop.

 

Joe L.

It was not exported, I dont know about READ ONLY though . I was just changing that via GUI to access the flash, but I can not see any files on it ... I see the flash in my network shares, when I access it it is just blank... I could shutdown the server and access it local on the PC... what do you suggest I do ? How can I pull a syslog to post on here for you?

It was not exported, I dont know about READ ONLY though . I was just changing that via GUI to access the flash, but I can not see any files on it ... I see the flash in my network shares, when I access it it is just blank... I could shutdown the server and access it local on the PC... what do you suggest I do ? How can I pull a syslog to post on here for you?

see here:

http://lime-technology.com/forum/index.php?topic=9880.0

 

You will likely need to run checkdisk/scandisk on your PC on the flash drive to fix it.

here is syslog

 

 

would i maybe have to rename my current .cfg to (.old) and allow the server to make a new fresh .cfg ? perhaps once you look at the log you can tell what is going on... I am skimming through it but don't know exactly what is going on... Thanks

 

SYSLOG.txt

as I said, the flash drive is either corrupted, or disconnected (it is not readable or writable):

Dec 30 10:47:06 Tower kernel: usb 2-1: device not accepting address 2, error -110

Dec 30 10:47:06 Tower kernel: usb 2-1: USB disconnect, address 2

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: Device offlined - not ready after error recovery

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: [sdj] Unhandled error code

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: [sdj] Result: hostbyte=0x01 driverbyte=0x00

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: [sdj] CDB: cdb[0]=0x2a: 2a 00 00 00 04 2f 00 00 01 00

Dec 30 10:47:06 Tower kernel: end_request: I/O error, dev sdj, sector 1071

Dec 30 10:47:06 Tower kernel: Buffer I/O error on device sdj1, logical block 1008

Dec 30 10:47:06 Tower kernel: lost page write due to I/O error on sdj1

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: [sdj] Unhandled error code

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: [sdj] Result: hostbyte=0x01 driverbyte=0x00

Dec 30 10:47:06 Tower kernel: sd 0:0:0:0: [sdj] CDB: cdb[0]=0x2a: 2a 00 00 00 00 45 00 00 02 00

Dec 30 10:47:06 Tower kernel: end_request: I/O error, dev sdj, sector 69

Dec 30 10:47:06 Tower kernel: Buffer I/O error on device sdj1, logical block 6

Dec 30 10:47:06 Tower kernel: lost page write due to I/O error on sdj1

Dec 30 10:47:06 Tower kernel: Buffer I/O error on device sdj1, logical block 7

Dec 30 10:47:06 Tower kernel: lost page write due to I/O error on sdj1

Dec 30 10:47:06 Tower kernel: write_file: write error 5

Dec 30 10:47:06 Tower kernel: md: could not write superblock from /boot/config/super.dat

Dec 30 10:47:06 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.

Dec 30 10:47:06 Tower kernel: usb 2-1: new high speed USB device using ehci_hcd and address 3

Dec 30 10:47:22 Tower kernel: usb 2-1: device descriptor read/64, error -110

Dec 30 10:47:37 Tower kernel: usb 2-1: device descriptor read/64, error -110

Dec 30 10:47:37 Tower kernel: usb 2-1: new high speed USB device using ehci_hcd and address 4

Dec 30 10:47:49 Tower kernel: FAT: Directory bread(block 496) failed

Dec 30 10:47:49 Tower kernel: FAT: Directory bread(block 497) failed

Dec 30 10:47:49 Tower kernel: FAT: Directory bread(block 498) failed

Dec 30 10:47:49 Tower kernel: FAT: Directory bread(block 499) failed

Dec 30 10:47:49 Tower kernel: FAT: Directory bread(block 500) failed

I did move the ports the USB was always connected to.... I always had it connected in front USB and moved it to the rear USB is that the issue....

 

So shut down my server ? attach my USB to my local PC here (windows) and run chkdisk on it ? then attach it back to the server, boot up and let the rebuild continue ?

 

here is the new syslog after shutdown / chkdisk / reboot ---> does everything look ok now ??

 

 

I am letting the rebuild process go for the 1300 minutes (I tried to attached screenshot but I guess it is too big) So after the process finishes .... and the config is valid, what should I do to verify that this does not happen again and it keeps my config saved and doesn't think it is a new disk ??

SYSLOG-2.txt

Another syslog, just to update make sure things are looking right (ie, read and write access)

SYSLOG-3.txt

SOLVED , THANK YOU