Forum Discussion

Aspirant

Jan 10, 2022

Boot up gets stuck on same file, tried booting into read only and stuck on different file.

Hello. There was an update, then I had a drive fail. I hot swapped it and everything seemed to work fine. Later when the nas shut down it would not boot up again. Raid X Netgear RAIDar shows my...

StephenB

Guru - Experienced User

Jan 15, 2022

michaelsammler wrote:

Are you suggesting a seagate test?

Sounds like he is suggesting Seatools.

michaelsammler wrote:
I have used the built in TEST DISK boot menu option and all the disks have shown no issues.

Netgear's threshold for bad sectors is higher than mine - I suggest also downloading the log zip file, and looking in disk-info.log.

rn_enthusiast

Virtuoso

Jan 15, 2022

Yes the disk-info.log log is good to look at.

You can get it by downloading the logs from the NAS via RAIDar here and then open the zip file and find the disk-info.log

michaelsammler
Aspirant
Jan 18, 2022
Here is the DISK INFO LOG from the RAIDar downloaded logs. I made it a pdf file so I could attach. Hope that works.

Thanks for the clarification.
- StephenB
  Guru - Experienced User
  Jan 18, 2022
  sda (serial S301EEYH) doesn't look healthy.
  
  Try powering down the NAS, and removing that drive. Then try booting read-only and see if anything changes.
  
  It looks like it's in bay 4, though the numbering is a bit unusual (normally sda is bay 0). So make sure you check the serial number when you pull the drive.
  - michaelsammler
    Aspirant
    Jan 18, 2022
    Thank you for your reply. The serial number did match up with bay 4's drive. I pulled it and booted as Volume Read Only. Still got stuck on upnphttp.service.
    
    I have tried pulling each drive one at a time to see if it would boot (regular, not read only) and it always got stuck on that same file.
    
    Good to know that drive in bay 4 is not looking good. Thanks.
    
    Michael