Errors then flash died


9 posts in this topic Last Reply

Recommended Posts

Hi Experts, Need help :)

 

I noticed in my log I was seeing errors (Pasted below).  So I downloaded a diagnostic log and rebooted.  When my system came up, it launched right into a parity check which I thought was odd since I had just done one a few days ago.  Then I noticed a bunch of read only errors showing up, so I stopped the parity check, downloaded a 2nd diagnostic file, then shut down the server.  When I went for 2nd reboot my BIOS complained there was no boot disk.  I pulled the flash drive out and tried it in Windows computer and its now is blank and can't be reformatted.  Corrupt.  So at a minimum I have to fix the flash and maybe other stuff.  

 

I use Community Apps to make weekly backups of my flash drive, but I store it an UInraid share (followin spaceinvader video).  So I have a backup of my flash drive, but its on unraid. 

 

Whats my best course of action?   I do have a recent copy of which disks are Parity/data etc.   Get a trial license, start up unraid, get access to the share, download the flash backup, restore flash backup on different USB stick, reboot server from new restored stick?

 

Thanks!

 

 

Apr  8 07:54:05 NAS4x12 kernel: blk_update_request: critical target error, dev sda, sector 36456 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 0
Apr  8 07:54:05 NAS4x12 kernel: Buffer I/O error on dev sda1, logical block 34408, lost async page write
Apr  8 07:54:05 NAS4x12 kernel: Buffer I/O error on dev sda1, logical block 34409, lost async page write
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] 
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x27 ASCQ=0x0 
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 1e 1c 28 00 00 f0 00
Apr  8 07:54:51 NAS4x12 kernel: blk_update_request: critical target error, dev sda, sector 1973288 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] 
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x27 ASCQ=0x0 
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 1e 1d 18 00 00 f0 00
Apr  8 07:54:51 NAS4x12 kernel: blk_update_request: critical target error, dev sda, sector 1973528 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Apr  8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] 

nas4x12-diagnostics-20210408-0754_Before1st_Reboot.zip nas4x12-diagnostics-20210408-1157_Before2ndReboot.zip

Edited by drjUnraid
Link to post

You can see your disk assignments in those diagnostics you posted.

 

As long as you make the correct disk assigments, you can just start with a new install and access your backup that way. Just be sure you don't assign any data disk to any parity slot and you should be good.

Link to post
  • drjUnraid changed the title to Errors then flash died

I was still on 6.9.1 release, should I try and reinstall that version first?

Were all the errors in my diagnostic related to the flash? Or is something else going on? Thanks in advance.

Link to post

Go ahead and install the version you were using since you know that was working. Then all you need to do is get your disks assigned and the array started so you can access your backup. You only need to copy the config folder from that backup to your new flash to get all your configuration back. After you reboot with that config, which contains the license to your old flash, you can transfer your license to your new flash by going to Tools - Registration.

 

I didn't fully examine the diagnostics since it was clear your flash had failed. That even explains it starting a parity check when you rebooted since the start/stop status of the array is saved on flash, and if it can't write that to flash when you shutdown then it sees that as an unclean shutdown when you reboot.

 

If you still have problems after you get going on a new flash with your previous config from your backup then we can take another look with new diagnostics.

Link to post

Thanks Trurl.  I will probably have to contact lime-tech as its been less than 12 months since I replaced my flash drive.  I pre-emptively replaced it last year, but it didn't last very long....I learned those micro flash drives, while small, are not very robust.

Link to post
13 hours ago, drjUnraid said:

I learned those micro flash drives, while small, are not very robust.

I have been using a USB 2.0 16GB Sandisk Cruzer Fit for 7 years.  They are still available on amazon.  I recommend to do a full (not quick format) FAT32 reformat before using.   The Usb 2.0 seem to be more robust.

Link to post
1 hour ago, Gragorg said:

I have been using a USB 2.0 16GB Sandisk Cruzer Fit for 7 years.

Me too and on 2 servers.

 

1 hour ago, Gragorg said:

The Usb 2.0 seem to be more robust.

And booting from USB2 port is also more trouble-free.

 

There is no advantage to USB3 for this.

Link to post

I had a very similar situation this morning. I pulled the plug today for replacing a "bad" flash disk, 32GB Usb 2.0 SanDisk Cruzer Fit. I replaced an old/cheap drive back in June of last year, that was actually bad. So I had to go through support to get reinstated. So not as hassle free, but they were pretty quick to respond and get me fixed up!

 

Anyway, I was getting read errors:
 image.thumb.png.8c70298e016c8fc375467f7ee9aca9d9.png

 

I thought for sure the flash drive was dead, because when I plugged it into my Windows machine to yank the config file at least, but it hosed it up proper. Windows explorer crashed, I couldn't get into disk management, nothing I tried would allow me to see/access the drive. I called it, and went ahead with replacing it with a backup Cruzer I have still NIB. Then a while later, I got curious, and fiddled with it more. Obviously the flash drive had a chance to cool down and such. But its been solid read/write/verify testing for nearly 5 hours now without a single error. So, looks like I may have prematurely replaced it, but not sure why it hosed up so bad to begin with.

 

image.thumb.png.af77e04920b8a8466a45992ba1a05ceb.png

 

Server is going good now, no more errors. Just thought I'd tell my story as well, just in case someone else has similar errors pop up. It may not be the flash drive.

 

-Ross

Link to post
  • 2 weeks later...

Thanks everyone. I was able to replace the flash drive, get access to my shares via trial license, copy the backups from the share to my desktop using cloud commander.  Then I restored my config folder, fixed my license key with tech support, and now I'm back in business.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.