Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Wierd issues that I could use immediate help on if possible

DeathtoToasters
in unRAID Server 3.0 [No new topics]

Featured Replies

I am stuck with this on my server:

 

Capture1-2.jpg

 

I have telnet'd in and rebooted...I have even pulled the plug and did a hard restart.

 

The lights on the machine seem to be all working. I think it is doing a parity check.

 

I have cleared the cache and temp files from my computer (thinking it could be an issue of seeing an old webpage) but still nothing. Even tried other computers on the network...same thing.

 

When I try to browse to the server, it only shows the flash drive, no other drives....I hope it is not clearing all drives.......that would suck!

 

There is no use in stopping it now, because if it started clearing them......it would still be ruined, but I would like to figure this out.

 

The whole situation started with it showing a bad drive 11 which was a segate 500GB drive.  Well I replaced it with an older 200 GB drive to see if that helped, but showed the whole thing with errors again.

 

Any help would be great.

Well, based on the screen shot it's stuck mounting a drive.  The only way to diagnose the issue is to get a copy of the syslog file.  If you post here I can take a look at it, but I would suggest sending it to Tom via mail as well.  It is the holidays so I don't know how quickly he will be able to get to it. 

 

 

Just read your note again.  If you had a bad drive replaced it and still have errors that could be an indication that it wasn't the drive at all and could be the cable, power, or controller, etc. 

 

I had a flaky/loose SATA PORT on one of my non-unRAID systems the other day so even that can be an issue sometimes.

I don't think you can replace a drive with another drive smaller than the one you wish to replace. Your 500 GB cannot be replaced by a 200 GB, maybe that is what is causing Unraid to get stuck.

I don't think you can replace a drive with another drive smaller than the one you wish to replace. Your 500 GB cannot be replaced by a 200 GB, maybe that is what is causing Unraid to get stuck.

 

Gnollo,

 

I thought you could if there was no data on it or at least less data than the total of the new drive.  Tom would probably be able to answer that though.  Looking at the screen shot the guy provided he has a lot of free space so I imagine if there was data on the bad drive he moved it to another drive before replacing.

  • Author

Here you go....very little of the log as it kept going for over 5 min. Hope this little bit helps.

 

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75784, count=120

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75784

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75784/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75792, count=112

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75792

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75792/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75800, count=104

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75800

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75800/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75808, count=96

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75808

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75808/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75816, count=88

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75816

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75816/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75824, count=80

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75824

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75824/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75832, count=72

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75832

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75832/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75840, count=64

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75840

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75840/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75848, count=56

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75848

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75848/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75856, count=48

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75856

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75856/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75864, count=40

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75864

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75864/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75872, count=32

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75872

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75872/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75880, count=24

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75880

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75880/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75888, count=16

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75888

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75888/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75896, count=8

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75896

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75896/11, count: 6, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75904, count=128

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75904

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75904/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75912, count=120

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75912

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75912/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75920, count=112

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75920

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75920/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75928, count=104

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75928

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75928/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75936, count=96

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75936

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75936/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75944, count=88

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75944

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75944/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75952, count=80

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75952

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75952/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75960, count=72

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75960

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75960/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75968, count=64

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75968

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75968/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75976, count=56

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75976

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75976/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75984, count=48

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75984

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75984/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=75992, count=40

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 75992

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 75992/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76000, count=32

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76000

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76000/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76008, count=24

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76008

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76008/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76016, count=16

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76016

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76016/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76024, count=8

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76024

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76024/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76032, count=128

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76032

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76032/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76040, count=120

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76040

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76040/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76048, count=112

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76048

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76048/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76056, count=104

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76056

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76056/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76064, count=96

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76064

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76064/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76072, count=88

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76072

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76072/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76080, count=80

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76080

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76080/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76088, count=72

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76088

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76088/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76096, count=64

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76096

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76096/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76104, count=56

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76104

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76104/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76112, count=48

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76112

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76112/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76120, count=40

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76120

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76120/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76128, count=32

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76128

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76128/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76136, count=24

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76136

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76136/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76144, count=16

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76144

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76144/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76152, count=8

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76152

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76152/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever kernel: hdh1: bad access: block=76160, count=128

Jan  1 15:08:17 ThanosNASSever kernel: end_request: I/O error, dev 22:41 (hdh),

sector 76160

Jan  1 15:08:17 ThanosNASSever kernel: md11: read error!

Jan  1 15:08:17 ThanosNASSever kernel: end_read_request 76160/11, count: 7, upto

date 0.

Jan  1 15:08:17 ThanosNASSever root@ThanosNASSever:~#

 

Well, That pretty much says it all.  There is a read error on the drive that is named hdh.  IF this is during the mounting process that is bad cause it sounds like unraid cannot read the FS at all.  I would recommend getting the entire syslog and mailing it to Tom.  [email protected]

The whole situation started with it showing a bad drive 11 which was a segate 500GB drive.  Well I replaced it with an older 200 GB drive to see if that helped, but showed the whole thing with errors again.

 

Initially, how did you know the original disk11 was 'bad'?

 

From the screenshot, looks like it's doing a parity-sync (building parity).  If this is the case, I suggest you shut it down (just power off if you have to), remove disk11, power up, 'restore' configuration, and the Start.  Data disks1..10 should mount normally, and a parity sync should start & you should see the disks appear on your network.

 

Get your system back to a known good state without disk11 plugged in, and then we can embark on further troubleshooting related to disk11.

  • Author

Ok....doing parity sync without issues.

 

No drive 11 installed.

 

Luckly I didn't send the Seagate 500GB drive back yet!

 

New thoughts, Tom?

  • Author

Initially, how did you know the original disk11 was 'bad'?

 

It showed almost all errors, then when I rebooted the server, it showed it unformatted, then it had the wrong drive serial and type. Then would not format correctly.  All weird things like that.

 

 

 

Initially, how did you know the original disk11 was 'bad'?

 

It showed almost all errors, then when I rebooted the server, it showed it unformatted, then it had the wrong drive serial and type. Then would not format correctly.  All weird things like that.

 

Did it work correctly at one time?  If you had a 12-drive system, with parity generated, then if disk11 started to "die" I would expect that the system would have disabled it at some point (the LED icon next to the disk turning red).

  • Author

To be honest, there was nothing on it, and with the holidays I was not transferring anything, so I don't know if it was STARTING to die or not.

 

I just noticed that one day it showed unformatted.

  • Author

Tom....any thoughts?

Tom....any thoughts?

 

I think your disk11 is bad  ;)

 

 

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.